• Configuration Process
• File Sharing

Configuring your network settings

Before beginning the setup you should have already obtained an IP address and other information from Computing and Information Services by filling out an IP request or sending email to ip-request@hmc.edu. Freshmen receive their IP address information when they receive their new accounts from CIS.

1. Double-click on My Computer and then on the Control Panel icon.

2. Go into System and ensure that your network card is listed under the Device Manager in the Network adapters section. You should also highlight it and click on Properties to ensure that it is working properly. If it is not listed, or is not working, you will have to use the Add Hardware wizard or adjust the Resources until it is working.

   

3. Return to the Control Panel and double-click on the Network option. You may or may not see some items listed in the Network Components box. Regardless of what is currently there, you will minimally need to Add the following items to the list:
   • Client for Microsoft Networks
   • Your ethernet adapter (varies depending upon brand name)
   • TCP/IP -> Your ethernet adapter
   Note TCP/IP is listed under "Microsoft" protocols.

4. Once you have added the above items to your Network Components list, it is likely that Windows may have automatically added others to the list (such as NetBEUI). You can safely Remove all of the other things that may be listed. Your screen should now look something like this screen.

   

5. At the top of the Network configuration window, you should see several tabs, as shown below.
   
   
   1. Click on Identification and set it as you feel appropriate, but you should ensure that you set the Computer Name so that matches what you reported to Computing and Information Services when you obtained your IP address.
      

   2. Click on Access Control and ensure that it is set to Share-level access control, since User-level access control is not supported on this campus.

      

   3. Click back on Configuration.

6. Highlight the "Client for Microsoft Networks" and click on Properties and ensure that you are not logging into any Windows NT domains. Click OK when done.

7. Highlight the driver for your ethernet adapter and click on Properties. You should ensure that the Driver Type is set to "Enhanced mode" (if possible) and that Bindings are enabled for TCP/IP. Click OK when done.

8. Highlight the "TCP/IP" Protocol and click on Properties. You should see the following tabs at the top of the TCP/IP Properties window:
   
   
   1. Click on IP Address and ensure that Specify an IP address is selected and that the IP Address and Subnet Mask are set to the values given to you by CIS (note that the IP address is typically in the form of 134.173.??.?? for HMC and that the Subnet Mask is 255.255.248.0 if you are in the dorm.)
   2. Click on WINS Configuration and verify that it is disabled. Its usage is not necessary on this campus.
   3. Click on Gateway and enter the value given to you by Computing and Information Services. For HMC, this is usually identical to your IP Address, except that the number after the last decimal point is "200". If you are in the dorm it should be 134.173.63.200. Once you have entered the gateway, click on the Add button.
   4. Click on DNS Configuration.
      • Ensure that Enable DNS is selected.
      • Ensure that Host is set to your machine's name plus any subnet identifiers (such as "mycomputer.st" or "handel.ac") and that Domain is set to "hmc.edu". Note that combining Host.Domain should be the full DNS name of your computer.
      • Enter the address of the DNS Server that was given to you by Computing and Information Services (should be 134.173.53.8) and click on Add.
      • Enter "hmc.edu" into the Domain Suffix Search Order box and click on Add.
      • When you're done, things should look something like this.
        
   5. Don't adjust the Advanced settings.
   6. Click on Bindings and ensure that it is enabled for "Microsoft Networks."
   7. Click on OK to close the TCP/IP Properties window.

9. Ensure that Primary Network Logon is set to Windows.

10. Click on OK to close this window and save the settings. You may be prompted to insert some Windows Installation Disks at this point, after which you will be prompted to restart.

After your computer restarts and Windows reloads, you should be completely operational. You can access CHARLIE by opening Windows Explorer and in the prompt typing //charlie.ac.hmc.edu. You will then be prompted for your CHARLIE username and password.

NOTE: You will not be able to run any applications available on CHARLIE if your machine is running Windows 95, 98, or NT.

Once you've verified that your connection to CHARLIE is operational, you should verify that your connection to the Internet (via TCP/IP) is working. This is most easily done by clicking on Start and selecting Run... and then typing "telnet odin" in the box and clicking on OK.

A Note About Peer-to-Peer File Sharing and Windows

Microsoft Windows permits users to share files from your personal hard disk and allows other users of Windows to access them. Although this type of filesharing is not discouraged, it is not supported by CIS. If you do decide to share files, you should be aware of the content of the files that you are making available. If you have any questions, you should see the Policy Guide to Offering Dorm Resources.

Furthermore, if you decide to enable Windows' file sharing, you should ensure that you use the File and printer sharing for Microsoft Networks service, and not the File and printer sharing for NetWare Networks service. Not only will the peer-to-peer NetWare filesharing not work, but because of a Microsoft bug, if "SAP Advertising" is enabled, it can block all other users from accessing other campus NetWare computers and can crash them if it is left enabled. Such intentional disruption of network services is not an authorized use and may be deemed to be an Honor Code Violation. Note that this particular bug was later fixed by Microsoft in its Service Pack 1, but the use of NetWare peer-to-peer file sharing should still not be used.