The purpose of this document is to give step-by-step instructions on how to install a network, both peer-to-peer and client-server connections.
1. Peer-to-peer networking with Windows XP
2. Client-Server Networking with Windows Server 2003
3. Peer-to-Peer Networking With Window 98
1. Peer-to-peer networking
with Windows XP
Setting the IP and subnet mask
If you would like to see what the different screens look like, refer to the screenshots here,
1. Open the Start Menu on one of the two computers running Windows XP, and select Settings --> Control Panel.
2. Double click on Network Connections.
3.
If one exists, right click on the Local Area Connection icon, and go
to "Properties".
**The Network Interface Card (NIC) should already be recognized and ready
to be configured, assuming that the version of Windows you're using includes
drivers for it. If it doesn't, installing the drivers included with the card
should automatically set it up to this point.**
4. Select the "Internet Protocol" icon, and click on the "Properties" button.
5.
Click on "Use the following IP address", and set the IP addresses to
each of the three machines to an IP such as 192.168.1.x, where there x is a
number between 1 and 254.
**x=0 and x=255 are reserved. x=1 is the traditional place for gateways and
routers in networks with multiple subnets, and for the server in smaller
networks such as this example. Each machine should have a different IP, if they
are connected to the same network.**
6.
Set the Subnet Mask address to a Subnet Mask that matches the IPs
used in Step 6 and press OK.
**For example, 255.255.255.0 would be a valid Subnet Mask for a 192.168.1.x
network.**
7. Make sure that "File and Printer Sharing for Microsoft Networks" and "Client for Microsoft Networks" are installed. If not, see appendix.
8.
Press OK and close until you are back to the Network Connections
window. No rebooting should be necessary at this point, but do so if prompted.
Windows enjoys being rebooted.
**Those interested might consult
RFC 1918, to see a list of IPv4 subnets that are not routeable on the
Internet. Using IPs like 10.x.x.x and 192.168.x.x allows network administrators
to set up TCP/IP networks without risking collisions with other IPs on the
Internet-proper, and are extremely useful in situations like this one.**
1. Right-click on My Computer.
2. Go to the "Computer Name" tab.
3. Click "Change", next to the text "To rename this computer or join a domain,
click Change".
4. Record the original Computer and Domain Names.
5. Set a computer name.
6. Change the Domain name to CIS367.
7. Click on "More" and set the Primary DNS Suffix to "local"
8. Press Okay, and give it your new user name and password. You will get an
error message if the domain name or DNS suffix is typed in incorrectly, the
username on the server is not yet created, or if the client is unable to find
the server.
1. Reboot one or both clients and
attempt to login to the domain CIS367 from the login screen, using your new
username and password.
**Don't worry about the slow login speed. It is most likely triggered by a
miss configured DNS server on the server side, but doesn't concern us here.**
2. Go to "Network places" and verify that the two clients can see each other.
3. Connect to the server by going to Start-->Run, and entering "\\192.168.1.1"
or "\\your-hostname-here", to see a list of shared directories and devices from
that machine.
**You may be prompted again for a username and password for the domain
server**
4. Try connecting to the other two machines as well. You can test it by sharing
new folders and devices, and then writing to and reading from them from the
other machines.
5. The above would not likely work without a functional TCP/IP network, but if
you wish to experiment with less operating system specific tools, you might try
going to Start-->Run, and running "cmd". In the command prompt that runs
afterwards, running "ping /t", followed by an IP address on your network. That
will test the ability of the computers to send TCP/IP packets back and forth,
and is installed by default on nearly every major operating system (including
all derivatives of Unix, such as Mac OS X and Linux). You might also try running
"ipconfig", which will show you your current IP, subnet mask, etc, and is a
useful tool for making such changes remotely.
Cleaning Up:
1. Follow the steps under Changing the
client Hostname to restore the hostname and domain to their original settings.
2. Go back to the TCP/IP properties window, and select the "Obtain an IP address
automatically" bullet.
3. Delete the username that you created
Installing "File and Printer Sharing for
Microsoft Networks" and "Client for Microsoft Networks" drivers
1. Go to the Local Area Connection Properties via the steps listed above.
2. Click on Install.
3. Select either the Client and Service tabs to install the required drivers.
This step will have to be repeated, if both drivers are absent.
3. Peer-to-Peer Networking With Window
If you would like to see what the different screens look like, refer to the screenshots here,
1. turn on the computer and uninstall the 'network neighborhood.” Then, restart the computer, and you will be ready to begin from scratch and install the different configurations.
2. Click Start and go to Settings, then click Control Panel.
3. Double click the Network icon.
3. Click 'Add", click Adapter.
4. Choose the 30om EtherLink III ISA [3C509/3C509b) in ISA mode.
5. By choosing this, the following will be installed automatically:
· Client for Microsoft Networks
· Client for Netware Networks
· 3Com EtherLink III ISA (3C509/3C509b) in ISA
· IPX/SPX-compatible protocol
· NetBUI
6. Next step is to click Client for Netware networks and click remove.
7. Then, click 'Add" click protocol, click Microsoft, select TCP/IP.
S. Now you should be at the main network screen showing all the added items; click Client for Microsoft Networks and select properties; uncheck the box to log on to Windows NT domain, then click OK.
9. Click 3Com EtherLink and select properties, click on the resources tab and set the VO address range: 350-35F
10. Click file and print sharing and check file sharing.
11. Click the 'Identification' tab and give the computer a name [if it does not already have one).
12. Click the 'Access Control' tab and be sure that share-level control is checked.
13. Then click OK and Restart the computer, repeat the steps for the remaining computers and they will be set up on a peer-to-peer connection.
1 First step in client-server is to add your user name through the server. It is done through admin. tools.
2. The following steps assume that the network settings are set for a peer-to-peer connection; if they are not, then go back and reinstall the settings for peer-to-peer (above).
3. Next, right-click the "Network Neighborhood' icon on the server and click the protocols tab and select TCP/IP and then properties.
4. Now find out the IP address and Subnet mask address.
5. Then go to a client and right-click the 'Network Neighborhood" icon and click TCP/P and properties, then click the IP address tab and check the box to specify an IP address.
6. Enter an IP address with the same first three numbers as the server and change the last number by one (for each client) e.g. server IP. 192,168.1.4 client IR 192.168.1.3.
7. Next enter in the subnet mask as it is on the server e.g. 255.255.255.0.
8. Then click OK.
9. Click the Client for Microsoft Networks and select properties, then check the box to log on to Windows NT domain and enter the domain: 'CIS367' Click OK.
10. Now, go back to server to add client to the domain by clicking Start, Programs, Admin Tools.
11. Click Server Mngr, then click computer and add to domain, then enter the client's computer name and click OK.
12. Go back to Admin Tools and select user manager for domains and assign an account for each user.
13. Go back to the client and click OK and restart the computer.
14. You are now connected through a client-server connection.
15. Network asks you to login. You should now be able to login with the user name you have created.
16. If you can log in successfully, you have completed this exercise.
These two different types of connections need to be tested once they are installed. It is important to remember that sometimes it may take a few minutes after installing and rebooting the computer before it actually shows up in the "Network Neighborhood'. Creating test files on each computer and accessing them from another computer and accessing files off of the server can test the connections. There are test files already created. If you wish to use them, they are in the CIS 367 folders on each machine. After installing and testing the network, you are finished, and the network should be fully operational.