ComTech: IT Support Stirling | Page 2
TwitterFacebookGoogle

How to connect FreeNAS to Active Directory


Today I will show you how to connect your FreeNAS server to Active Directory.  For the basis of this tutorial I will use Small Business Server 2011 as my primary DNS server on the network and a NAS box running FreeNAS 8.

First thing we need to do is configure the appropriate DNS record in Active Directory so on your primary DNS server (SBS2011 in my case) open up the DNS Management Console.  To do this go to:

Start – Administrative Tools – DNS (shown below)

Now we need to expand the dns zone (shown below) and then right click to add A New Host (A or AAAA) record.

Enter the hostname and ip address of your FreeNAS server (as shown below)

Then click add host and your FreeNAS server should now have an A record in DNS.

Now we need to access your FreeNAS server via the web interface so open up a browser and type the ip address of your FreeNAS server (as shown below).

We now have to add the ip address of the primary DNS server to the FreeNAS network configuration.  To do this go to:

Network – Global Configuration (shown below)

Enter the ip address of the primary DNS server (in my case 10.0.0.199) into the Nameserver 1 row and then click ok.

Next we need to configure the Active Directory settings so go to:

Services – Active Directory Settings (as shown below)

This should bring up the next box.

You need to enter your specific details which are relevant to your domain.  When you have finished click ok.  This will take you back to the Services screen where you need to turn the Active Directory Service ON.  Now restart the system.

Once restarted your FreeNAS server will be connected to your Active Directory domain and a computer account will be set up in Active Directory Users and Computers.

About the Author

P1020114

Hi I’m Chris Wakefield the owner of ComTech IT Support. I provide Windows, Mac and Linux based IT Support to small businesses in Stirling, Alloa and Falkirk.

Follow @Comtech247 on Twitter

 

How to transfer DNS Zones in Windows Server 2008 R2


Today we will having a look at Windows Server 2008 R2 and in particular how you go about transfering DNS zones between two or more DNS servers.

On the DNS server hosting the primary DNS zone open up DNS Manager.  Expand the menus until you locate your domain and right click.  Go to properties.  You should get the screenshot below.

On the general tab it is good practice to change Dynamic updates to Secure Only.  Doing this only allows updates from trusted sources.  Once completed click on the Zone Transfers tab.  You should get the screenshot below.

 

 

 

 

 

 

 

 

 

 

 

Click on Allow Zone Transfers and then it is a good idea to click on “Only to the following servers”.  This allows DNS data to only be replicated to trusted servers.  Enter the ip address of the trusted server and wait until the FQDN appears.  Once the data is entered and verified click Apply.  The DNS data will now be replicated between your servers.

About the Author

P1020114

Hi I am Chris Wakefield the owner of ComTech IT Support. I provide Windows and Linux based IT Support, laptop repairs and computer repairs to both business and personal clients throughout Stirling, Falkirk and Clackmannanshire.

For a list of what I can offer you why not visit my website www.comtech247.net where you will find a list of my services, testimonials, blog and much more!!

 

 

How to set up a DHCP server on Linux Mint 12


Recently I did a tutorial on setting up a Linux dhcp server using the dhcp3-server package.  With the arrival of Linux Mint 12 the configuration is slightly different so I shall revise the tutorial to show this.

First thing to do is to give your server a static ip address. For details on how to do this read this.

Now we need to install the dhcp package.  Open up a terminal and type:

sudo apt-get install isc-dhcp-server

There are two main files /etc/default/isc-dhcp-server and /etc/dhcp/dhcpd.conf which we will need to configure so lets take the first.  Open up a terminal and using your favourite text editor type:

sudo gedit /etc/default/isc-dhcp-server

You should get the following:

———————————————————————————————–

# Defaults for dhcp initscript
# sourced by /etc/init.d/dhcp
# installed at /etc/default/isc-dhcp-server by the maintainer scripts

#
# This is a POSIX shell fragment
#

# On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
# Separate multiple interfaces with spaces, e.g. “eth0 eth1”.
INTERFACES=”eth0″

————————————————————————————————–

Replace eth0 above with the name of your network interface that you want the server to lease addresses on.  Onto the next file.  Open up a terminal and type:

sudo gedit /etc/dhcp/dhcpd.conf

which should give you the output below.

————————————————————————————————-

#
# Sample configuration file for ISC dhcpd for Debian
#
# Attention: If /etc/ltsp/dhcpd.conf exists, that will be used as
# configuration file instead of this file.
#
#

# The ddns-updates-style parameter controls whether or not the server will
# attempt to do a DNS update when a lease is confirmed. We default to the
# behavior of the version 2 packages (‘none’, since DHCP v2 didn’t
# have support for DDNS.)
ddns-update-style none;

# option definitions common to all supported networks…
option domain-name “example.org”;
option domain-name-servers ns1.example.org, ns2.example.org;

option domain-name “comtech.com”;
default-lease-time 600;
max-lease-time 7200;

# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
#authoritative;

# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
log-facility local7;

# No service will be given on this subnet, but declaring it helps the
# DHCP server to understand the network topology.

#subnet 10.152.187.0 netmask 255.255.255.0 {
#}

# This is a very basic subnet declaration.

subnet 10.0.0.0 netmask 255.255.255.0 {
range 10.0.0.150 10.0.0.253;
option routers 10.0.0.2;
option subnet-mask 255.255.255.0;

option broadcast-address 10.0.0.254;
option domain-name-servers 10.0.0.1, 10.0.0.2;

option ntp-servers 10.0.0.1;
option netbios-name-servers 10.0.0.1;
option netbios-node-type 8;
}

# option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;

#}

# This declaration allows BOOTP clients to get dynamic addresses,
# which we don’t really recommend.

#subnet 10.254.239.32 netmask 255.255.255.224 {
# range dynamic-bootp 10.254.239.40 10.254.239.60;
# option broadcast-address 10.254.239.31;
# option routers rtr-239-32-1.example.org;
#}

# A slightly different configuration for an internal subnet.
#subnet 10.5.5.0 netmask 255.255.255.224 {
# range 10.5.5.26 10.5.5.30;
# option domain-name-servers ns1.internal.example.org;
# option domain-name “internal.example.org”;
# option routers 10.5.5.1;
# option broadcast-address 10.5.5.31;
# default-lease-time 600;
# max-lease-time 7200;
#}

# Hosts which require special configuration options can be listed in
# host statements. If no address is specified, the address will be
# allocated dynamically (if possible), but the host-specific information
# will still come from the host declaration.

#host passacaglia {
# hardware ethernet 0:0:c0:5d:bd:95;
# filename “vmunix.passacaglia”;
# server-name “toccata.fugue.com”;
#}

# Fixed IP addresses can also be specified for hosts. These addresses
# should not also be listed as being available for dynamic assignment.
# Hosts for which fixed IP addresses have been specified can boot using
# BOOTP or DHCP. Hosts for which no fixed address is specified can only
# be booted with DHCP, unless there is an address range on the subnet
# to which a BOOTP client is connected which has the dynamic-bootp flag
# set.
#host fantasia {
# hardware ethernet 08:00:07:26:c0:a5;
# fixed-address fantasia.fugue.com;
#}

# You can declare a class of clients and then do address allocation
# based on that. The example below shows a case where all clients
# in a certain class get addresses on the 10.17.224/24 subnet, and all
# other clients get addresses on the 10.0.29/24 subnet.

#class “foo” {
# match if substring (option vendor-class-identifier, 0, 4) = “SUNW”;
#}

#shared-network 224-29 {
# subnet 10.17.224.0 netmask 255.255.255.0 {
# option routers rtr-224.example.org;
# }
# subnet 10.0.29.0 netmask 255.255.255.0 {
# option routers rtr-29.example.org;
# }
# pool {
# allow members of “foo”;
# range 10.17.224.10 10.17.224.250;
# }
# pool {
# deny members of “foo”;
# range 10.0.29.10 10.0.29.230;
# }
#}

————————————————————————————————

This needs a little bit of explaining.

1. Everything in bold needs adding to the file.  Adjust your settings according to your network requirements.

2. The option domain name is your dns zone name.  For example mine is set to comtech.com.

3. Range should be the range of ip addresses that you want the server to give out to clients.

Now restart the dhcp service by typing:

sudo service isc-dhcp-server restart

Thats it!! Your dhcp server should be running, however it is best to check.  Open up a terminal and type:

sudo netstat -uap

which will show you the following information:

————————————————————————————————

Active Internet connections (servers and established)

Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name

udp 0 0 *:55827 *:* 916/avahi-daemon: r
udp 0 0 chris-desktop.lo:domain *:* 1273/named
udp 0 0 chris-desktop:domain *:* 1273/named
udp 0 0 *:bootps *:* 4525/dhcpd
udp 0 0 *:17500 *:* 1768/dropbox
udp 0 0 *:54407 *:* 4539/VirtualBox
udp 0 0 10.0.0.255:netbios-ns *:* 1016/nmbd
udp 0 0 chris-deskto:netbios-ns *:* 1016/nmbd
udp 0 0 *:netbios-ns *:* 1016/nmbd
udp 0 0 10.0.0.255:netbios-dgm *:* 1016/nmbd
udp 0 0 chris-deskt:netbios-dgm *:* 1016/nmbd
udp 0 0 *:netbios-dgm *:* 1016/nmbd
udp 0 0 *:mdns *:* 916/avahi-daemon: r
udp6 0 0 [::]:domain [::]:* 1273/named
udp6 0 0 [::]:51853 [::]:* 916/avahi-daemon: r
udp6 0 0 [::]:mdns [::]:* 916/avahi-daemon: r

————————————————————————————————

This shows that the dhcp daemon is working.

About the Author

Hi I am Chris the owner of ComTech. I provide IT Support, Laptop repairs and Computer repairs to both personal and business clients in and around Stirling. For a list of what I can offer you why not visit my website www.comtech247.net where you will find my blog, testimonials, services and much more.  Start supporting a local business today so I can start supporting you.

If you found this blog useful then why not sign up to my RSS Feed for news, tutorials, views and general techie stuff!!

 

Setting up a Linux DHCP server


Today we are going  install and set up a Linux DHCP server.  Linux Mint 9 was used in this tutorial but the steps are identical for the majority of recent distributions.

First thing to do is to give your server a static ip address. For details on how to do this read this.

Now we need to install the dhcp package.  Open up a terminal and type:

sudo apt-get install dhcp3-server

There are two main files /etc/default/dhcp3-server and /etc/dhcp3/dhcpd.conf which we will need to configure so lets take the first.  Open up a terminal and using your favourite text editor type:

sudo gedit /etc/default/dhcp3-server

You should get the following:

———————————————————————————————–

# Defaults for dhcp initscript
# sourced by /etc/init.d/dhcp
# installed at /etc/default/dhcp3-server by the maintainer scripts

#
# This is a POSIX shell fragment
#

# On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
#    Separate multiple interfaces with spaces, e.g. “eth0 eth1”.
INTERFACES=”eth0″

————————————————————————————————–

Replace eth0 above with the name of your network interface that you want the server to lease addresses on.  Onto the next file.  Open up a terminal and type:

sudo gedit /etc/dhcp3/dhcdp.conf

which should give you the output below.

————————————————————————————————-

#
#   DHCP Server Config File
#
ddns-update-style none;
ignore client-updates;

lease-file-name “/var/lib/dhcp3/dhcp.leases”;
authoritative;

option domain-name                      “comtech.com”;
default-lease-time                     600;
max-lease-time                         7200;

subnet 192.168.1.0 netmask 255.255.255.0 {
option routers                  192.168.1.1;
option subnet-mask              255.255.255.0;

option broadcast-address        192.168.1.255;
option domain-name-servers      192.168.1.4, 192.168.1.1;

option ntp-servers              192.168.1.4;
option netbios-name-servers     192.168.1.4;
option netbios-node-type        8;
range   192.168.1.10   192.168.1.200;
}

————————————————————————————————-

This needs a little bit of explaining.

1. The dhcp.lease file is where all the leases given out by the server will be stored.  Make sure this is /var/lib/dhcp3/dhcp.leases.

2. The option domain name is your dns zone name.  For example mine is set to comtech.com.

3. Range should be the range of ip addresses that you want the server to give out to clients.

Using the above output as a guide modify your file accordingly.  Next thing to do is actually create the dhcp.lease file.  In your terminal type:

sudo touch /var/lib/dhcp3/dhcp.leases

Now restart the dhcp service by typing:

sudo service dhcp3-server restart

Thats it!! Your dhcp server should be running, however it is best to check.  Open up a terminal and type:

sudo netstat -uap

which will show you the following information:

————————————————————————————————

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
udp        0      0 chris-server.loc:domain *:*                                 1072/named
udp        0      0 localhost:domain        *:*                                 1072/named
udp        0      0 *:bootps                *:*                                 1829/dhcpd3
udp        0      0 *:mdns                  *:*                                 625/avahi-daemon: r
udp        0      0 *:35246                 *:*                                 625/avahi-daemon: r
udp6       0      0 [::]:domain             [::]:*                              1072/named

————————————————————————————————

This shows that the dhcp daemon is working.

About the Author

Hi I am Chris the owner of ComTech. I provide IT Support, Laptop repairs and Computer repairs to both personal and business clients in and around Stirling. For a list of what I can offer you why not visit my website www.comtech247.net where you will find my blog, testimonials, services and much more.  Start supporting a local business today so I can start supporting you.

If you found this blog useful then why not sign up to my RSS Feed for news, tutorials, views and general techie stuff!!

 

 

Setting up a windows 7 vpn server

Today we are going to set up a Windows 7 vpn server which will allow you to securely access your PC from anywhere using the internet.

Click on Start – Control Panel – Network and Sharing Centre – Change adapter settings.

Once you see the connections press the ALT key which will bring up a line of menus at the top of the screen.  Go to File – New Incoming Connection.

The first thing we need to do is chose who can access your computer.  Chose the required user (or users) and tick the box next to them.  Then click next.


Next we need to chose how users will connect to your computer.  Tick the box next to Through the Internet and then click next.

On the next page leave the defaults and click Allow Access.

On the final screen you will see the name of your computer.  Write this down as you will need this later.

Now we need to allow vpn traffic through your router and any firewalls.  On your router you will need to port forward vpn traffic to your computers ip address on port 1723.  On any firewalls check that port 1723 is open.

Now we just need to check if the connection is active.  Go to Control Panel -Network Connections – Change Adapter Settings.  You should see an icon stating Incoming Connections with no clients connected.  This means that your vpn server is now active and waiting for connections.

Next time I will show you how to connect to your vpn server.

About the Author

Hi I am Chris Wakefield the owner of ComTech IT Support. I provide Windows and Linux based IT Support, laptop repairs and computer repairs to both business and personal clients in and around Stirling.

For a list of what I can offer you why not visit my website www.comtech247.net where you will find a list of my services, testimonials, blog and much more.

How to set up a Linux Web Server


This tutorial will show you how to set up a basic web server. For this tutorial I have used Linux Mint 9 but the steps work the same on any Linux distribution

Ok first thing to do is give your server a static ip address (refer to earlier blog here for details).  Once done it is time to download the software you will need.  Open up a terminal and install the following packages:

apache2 php5-mysql libapache2-mod-php5 mysql-server

During the install process MySQL will ask you for a root password.  Make this something complex but do not forget it!!!

Once installed open up a web browser and type http://your-server-address (e.g http://192.168.1.3) and you will see the message IT WORKS! This means that you have a working web server.

Now it is time to add some content to your server.  All apache servers store their web data at /var/www but as default you can not write to this folder.  Open up a terminal and type:

sudo nautilus

Enter your password when prompted.  Navigate to /var and right click on www.  Then go to properties.  Add yourself as either the owner or group and give yourself “create and delete files folder access”.

Next thing to do is to download some ftp software.  Personally I recommend Filezilla. Open up a terminal and type:

sudo apt-get install filezilla

Once installed connect to your existing web server and transfer your files into /var/www.

Congratulations!! Your website is now hosted on your new server but it will not yet be visible from the internet.  Most networks sit behind a router which acts as a firewall, so to make your website visible you will need to forward http packets from your router to your server by opening up port 80 and redirecting it to your servers new ip address.Portforward.com is a good starting point to understand port forwarding.

You will also need to speak to your ISP about getting a static ip address for your router. Without this you will not be able to access your site everytime your ip address changes.

And that is it!! You now have a basic web server from which to host your own website.

About the Author

Hi I am Chris the owner of ComTech. I provide IT Support, Laptop repairs and Computer repairs to both personal and business clients in and around Stirling. For a list of what I can offer you why not visit my website www.comtech247.net where you will find my blog, testimonials, services and much more.  Start supporting a local business today so I can start supporting you.

If you found this blog useful then why not sign up to my RSS Feed for news, tutorials, views and general techie stuff!!

 

 

 

 

How to set up a Linux DNS server


Today we will have a look at setting up a DNS server on Linux.  This tutorial was configured using Linux Mint 9 but the steps are the same for any Linux distribution.

First thing to do is to install the software we need. Open up a terminal and type:

sudo apt-get install bind9

Once installed it is time for some configuring.  The first file we need to configure is named.conf.local.  So in the terminal type:

sudo nano /etc/bind/named.conf.local

I have used nano to open up the file but use whichever text editor you are happy with.  Insert the following code into the file:

# This is the zone definition. replace example.com with your domain name
zone “comtech.com” {
type master;
file “/etc/bind/zones/comtech.com.db”;
};

# This is the zone definition for reverse DNS. replace 0.168.192 with your network address in reverse notation – e.g my network address is 192.168.0
zone “1.168.192.in-addr.arpa” {
type master;
file “/etc/bind/zones/rev.0.168.192.in-addr.arpa”;
};

Replace comtech.com with the name of your DNS domain (this is not the same as an active directory domain but rather a name for your DNS zone).

Next up is the options file.  In the terminal type:

sudo nano /etc/bind/named.conf.options

Within this file we need to modify the forwarder with the address of your ISP’s DNS servers.  So modify the file adding the following:

forwarders {

194.72.0.114;
194.74.65.69;
};

Replace the addresses above with the addresses of your ISP’s DNS servers.

Now we need to add the zones file:

sudo mkdir /etc/bind/zones

And then configure it:

sudo nano /etc/bind/zones/comtech.com.db (replace comtech.com with your DNS domain).

Add the following code to the file:

// replace example.com with your domain name. do not forget the . after the domain name!
// Also, replace ns1 with the name of your DNS server
comtech.com.      IN      SOA     chris-server.comtech.com. 
// Do not modify the following lines!
2006081401
28800
3600
604800
38400
)

// Replace the following line as necessary:
// ns1 = DNS Server name
// mta = mail server name
// example.com = domain name
comtech.com.      IN      NS              chris-server.comtech.com.
comtech.com.      IN      MX     10       mta.example.com.

// Replace the IP address with the right IP addresses.
www              IN      A       192.168.1.4
mta              IN      A       192.168.0.3
chris-server              IN      A       192.168.1.4

In the above code replace the following:

comtech.com with your DNS domain name,

192.168.1.4 with your static DNS server address,

chris-server.comtech.com with your computers hostname.dns-domain,

mta is your mail server (if you have one).  If you do modify the IP address to show this.

Next we have to create the reverse DNS zone file:

sudo nano /etc/bind/zones/rev.1.168.192.in-addr.arpa

Add the following code:

//replace example.com with yoour domain name, ns1 with your DNS server name.
// The number before IN PTR example.com is the machine address of the DNS server
@ IN SOA chris-server.comtech.com admin.comtech.com. (
2006081401;
28800;
604800;
604800;
86400
)

IN    NS     chris-server.comtech.com.
1                    IN    PTR    comtech.com

All that is left to do is restart bind:

sudo service bind9 restart (using upstart) or sudo /etc/init.d/bind9 restart (init scripts)

Don’t forget to test the new configuration:

dig comtech.com

About the Author

Hi I am Chris the owner of ComTech. I provide IT Support, Laptop repairs and Computer repairs to both personal and business clients in and around Stirling. For a list of what I can offer you why not visit my website www.comtech247.net where you will find my blog, testimonials, services and much more.  Start supporting a local business today so I can start supporting you.

If you found this blog useful then why not sign up to my RSS Feed for news, tutorials, views and general techie stuff!!

 

 

 

 

 

CyberChimps
Follow

Get every new post delivered to your Inbox

Join other followers

WordPress SEO fine-tune by Meta SEO Pack from Poradnik Webmastera
WP Like Button Plugin by Free WordPress Templates