Thursday, July 7, 2011

DNS, DHCP and Other Members of the Alphabet

Image found at http://abstrusegoose.com/strips/ping.png

The morning started where we left off the previous day. More server work!

Our tireless leader worked hard to make sure we had internet connection through our switches. So we started the morning by contacting the other switches by sending a ping request from our workstations. There was much rejoicing as we were able to make contact!

Then we began downloading updates for the server. 

 The next step was to make sure we were able to use telnet to manage our switch. Macs apparently have an easier time with that, but my ol' Dell needed some tweaking. *sigh* The good thing is that it is as simple as checking a box!

We then discovered various ways to manage the switches in our networks. Telnet is one way to access, Webview is another as is Cool Term. You can use any of these to manage work stations in your network through accessing the switch. Through your switch you can manage The good thing is that most of the commands are the same, but there are benefits to using some over others, such as batch processing through telnet and mobile access through Webview.

Through Webview, Ethernet network interface status is visible. You are able to see connection status of other switches, servers and workstations on your network.

One way of managing your network is to direct network traffic by completing routing tables. In this way you can route traffic around content filters or limit what others network users can see. In order to increase functionality, all of our switch addresses were manually typed into the routing table of the main switch. Each of our switches should have four entries in their routing tables. Using telnet, we verified that this was true for our network.

The next task for us was to set up a DHCP servers on our routing table.  We used this resource for this: http://www.windowsreference.com/windows-server-2008/how-to-setup-dhcp-server-in-windows-server-2008-step-by-step-guide/

Then we set up the DNS server! Don't tell anyone, but I think I am getting the hang of this!

Another task for the day was to create a folder on the server that could be shared with other users on the network. After making sure that we allowed all network users to have full control and the ability to change instead of only being able to read the folder contents, we added a document on another server in the network. This kind of access came in handy later in the day when one group managed to get all of the downloads we needed. They kindly stored them in a shared folder!

Another part of the day's work was to make sure our server had all the necessary drivers for full functioning.  At first, we tried to update through the automatic update settings found by clicking on the drivers with an error message. That did not work.

So we downloaded a driver detective on the server and ran a diagnostic. We were unable to locate the drivers without paying for the service, so we scrapped that. We located the driver downloads, but the server did not recognize them. We assumed that meant they were the wrong drivers. That was a mistake.

Although I am not sure, I believe the error was simply that the server had not completed the updates we started getting at the beginning of the day. This seems to have interfered with our progress significantly!

While trying to access the internet from the server, many security warnings popped up. This was all too annoying, so we went to this site and changed the setting: http://www.404techsupport.com/2009/01/08/remove-internet-explorer-enhanced-security-configuration/

Finally to test internet connectivity, we booted a work station with Knopix operating system to make sure the DCHP server would assign a dynamic IP address when requested. At first we loaded the system on our server – WHOOPS! Not to worry - it is just another reboot!

We had a little difficult getting the work station connected, so we tried to reboot, change out towers, check connections ... check both ends of the connection and viola! The ethernet cord was a little loose. All it took was a little wiggle to get things done!

Not sure how techy that is! SHEESH!

No comments:

Post a Comment