ITEC 350 Lab Exercise

 

 

 

Note:

 

Total points = (Basic Requirements (40 points) + Advanced Topics (50 points) + Report (10 points) + [Optional: Linux Exercises (10 points)])*(peer evaluation)

0         ≤     peer evaluation      ≤     1

 

 

Basic Requirements:  40 points

 

I.                     Read this description and divide the duties among your pod-mates.  Your pod must submit a list of assignments among the members.  You may copy this document and submit it with your names beside each of the core items, and your chosen electives.   Each pod-mate should submit a copy to his/her student dropbox.

 

II.                   Connect the computers with your switch using patch panels at the pod and at the switch.  Please treat all cabling gently.  If you break a connector in a patch panel or breakout box, it may delay your lab.  You must have your PCs connected into the Ethernet switch, and the switch power on to be able to install Active Directory and a DNS server.

 

III.                  Install operating systems on the three computers in your pod.  (Note:  You have a single copy of the CD from our MSDN agreement that has Win2003 Server on it. 

1.                   Install Windows 2003 Server (W2K3S) on one machine to be your domain controller.  You may want to configure the server as a stand-alone server first – this means saying “configure the server later” in the Server Config dialogue that automatically starts when you first login to W2K3S as administrator. Then use the application named “Manage Your Server” to promote the server to a domain controller later on.   Use any domain name you want but try to avoid a name you know is registered such as radford.edu, Toyota.com, etc.

2.                   Install Windows XP Professional (WXPP) on another machine.  Make sure your Domain controller is set up so that your WXPP workstation can join your pod’s domain. Add user accounts to the workstation.

3.                   Install Linux on the third machine. See separate instructions on options for the Linux setup.

 

IV.                Make sure your network card is detected correctly, load alternate drivers if necessary.

 

V.                  Configure TCP/IP on the server and workstations using static IP addresses  (you do not need Appletalk, NetBeui or IPX).  The DNS entry for the Ethernet NIC on the W2K3 Server machine should be left blank – this will result in the loopback address being used. (A small complaint from W2K3S will pop up; just say OK.) Be sure to configure the DNS settings on the other workstations to the actual IP address of your W2K3 Server.

 

VI.                Confirm basic network communications by pinging ip addresses and then machine names. If pings do not work, check your wiring. Configure the workstations to join the domain if you have not already done so.

 

VII.               Confirm that name resolution (DNS) is working on your server.  Check to make sure that the zone ‘.’ has not been automatically added by W2K3S – if so, delete that zone.  Set up DNS on your server to use the lab server (190.111.50.100) as a forwarder.  Check the DNS tables and use nslookup. 

 

VIII.             Establish a shared directory on the domain controller and confirm access by group members logged on to workstations.

 

IX.                 Learn how to add users to the active directory database remotely, from the workstations, by installing the ADMINPAK plug-in on a workstation.  Learn how to use the computer management plug-in to manage remote computers.

 

X.                   Cable your router per the lab diagram.   Configure and activate the two Ethernet interfaces on your router. (NOTE: configure interfaces for full duplex)  Configure your pod’s computers to use the router as a gateway.  Confirm basic connectivity by pinging the lab server (190.111.50.100).

 

 

(At this point you should have me check your project)