This chapter covers the nuances and changes in connecting a Windows 95 system to the FAS Network. On the hardware side, the instructions are identical to those of DOS and Windows 3.x. The software side, however, resembles the Macintosh OS setup process more than anything else, and that is by design!


This fall, Windows 95 Installation should be simpler than ever. Plug and Play is a more stable and accepted technology, and FAS Computer Services has a new Installer that makes the old manual configuration described in the Windows 95 Tip Sheet unnecessary - but be sure to read and know it so you can catch any problems!

Table of Contents:

Section I: The Ethernet Device and Device Drivers

1. Finding the Ethernet Address
2. Understanding Ethernet Cards for PC Desktops
3. Recognizing New Hardware: Plug and Play
4. Recognizing New Hardware: The Add New Hardware Wizard
5. Installing Ethernet Cards for PC Desktops
6. Installing PCMCIA Ethernet Cards for PC Notebooks
7. Installing Parallel Port Adapters for PC Notebooks
8. Resolving Problems in the System Control Panel

Section II: LAN Protocols

1. IPX/SPX on Windows 95
2. The Perils of NetBEUI

Section III: TCP/IP

1. DHCP on Windows 95
2. The WINIPCFG Utility

Section IV: Miscellaneous Troubleshooting

1. A Standard Checklist for PC Networking
2. Other Tips and Tricks
   

Section I: The Ethernet Device and Device Drivers

In previous chapters, we have differentiated between the actual installation of the Ethernet device into the user's computer and the installation of device driver software so the card can be recognized.


Windows 95 works a little differently; much of the grunt work of device drivers is made transparent by "Plug and Play," which in many cases will automatically recognize and install the software for new peripherals. Notice the words "many cases," not all cases - for this reason, Plug and Play has been dubbed "Plug and Pray" by many industry pundits.


If Plug and Play is not working for a particular card, it is often necessary to try adding the device driver before installing the hardware; for this reason, device driver information and hardware installation have been merged into this single section.



WARNING: The adapter boards will be installed in computers which operate with voltages that can be lethal. Before you remove the computer covers,
observe the following steps to protect yourself and prevent damage to the system's components:


1. Turn off the computer and unplug the unit from its power source.
2. Disconnect all cables that are connected to the main system unit.
3. Remove any loose jewelry from your hands and wrists.
4. Use only nonconductive tools.
5. Put on your wrist ground strap (required!)

On 3Com cards, it is quite painless to find the device's hardware Ethernet address. For their PCI, ISA, and EISA cards, there is a white sticker on the top of the card itself -- this sticker has the Ethernet address written on it. The Ethernet address can also be found on the underside of their PCMCIA cards. Be careful when reading off the address, however -- it is easy to mistake the zero, the number eight, and the letter "B!"


For unsupported Ethernet cards, it is more difficult to find their hardware address. Look for a configuration or setup program on the diskette that came with their card; this will often contain the Ethernet address as well. In many cases, the card's packet driver will return an Ethernet address when it recognizes the card.


Another option is to get the Ethernet address from Win95's WINIPCFG utility once the card is installed and recognized in the unit. Clicking on Start, then Run…, then typing WINIPCFG and pressing the ENTER key will bring up a window, showing the machine's IP address and the Ethernet address of the card.



If all else fails, open an MS-DOS prompt, go to the C:\WINDOWS\SYSTEM directory, and type NET DIAG /STATUS to find the Ethernet address. Its interface is archaic, but it's a good "last resort." It's useful if Win95 is recognizing the Ethernet device but TCP/IP (and thus WINIPCFG) aren't working.

There are four main types of PC Ethernet cards; however, they all are installed basically the same way! The only difference is the bus type (essentially the connector circuitry) on the card--ISA, EISA, MCA, or PCI.


ISA, by far the most popular type, is designed for 8-bit or 16-bit buses; most 386, 486, and Pentium machines have ISA slots. PCI cards, available mostly for Pentium machines, use an industry standard 32-bit local bus for incredibly high throughput, and also support hardware "Plug and Play" for easy configuration.


Older machines, such as high-end 386 desktops and the notorious IBM PS/2, in some cases have EISA and MCA slots instead of ISA. These Ethernet cards use a proprietary 32-bit bus and offer higher throughput at a higher price. You probably won't run into any of these machines this fall.


ISA expansion slots will take only ISA cards. EISA slots can take either an EISA card or an ISA one. MCA and PCI slots are only compatible with their respective card types.


It is possible to get unsupported cards working on the Harvard network; however, it is often much harder to do so than with the high-quality 3Com Ethernet cards. Unsupported cards must at the very least support Novell's Open Data-Link Interface (ODI). We are only offering minimal installation and troubleshooting assistance to users with unsupported cards. If you run into major problems with an unsupported card, go ahead and page the Advanced Support Team for guidance and assistance.



Section I.3: Recognizing New Hardware: Plug and Play

One major benefit of Windows 95 is its support of Plug and Play (PnP) technology. In short, this allows a computer to automatically recognize new hardware in a machine, install the device drivers, and assign it an IRQ and other settings - all without user or UA intervention!


All 3Com ISA cards that have shipped in the past 12 months or so are PnP compatible; all PCI and PCMCIA cards support PnP by design. For users who have purchased a new 3Com card from the TPC, then, the best solution is to power down their system, follow the instructions listed below in Sections I.6 to I.8 to install the card, and hope that Windows 95 recognizes the device on startup!


When Win95 does recognize the card, it will usually prompt you for the user's original Win95 disks or CD-ROM so the drivers can be installed. Be sure this is handy before beginning an installation.



Section I.4: Recognizing New Hardware: The Add New Hardware Wizard

In some cases, however, Plug and Play will not recognize the new device automatically, especially on older computers or Ethernet cards that do not fully meet PnP requirements.


On these systems, you need to tell Win95 that you are adding new hardware to the computer before doing so. The way of doing this, appropriately enough, is the Add New Hardware wizard:

1. Click on Start, then Settings, then Control Panel.
2. Double-click on the Add New Hardware icon.
3. Follow the prompts. If the card has not yet been put into the system, choose "No" when asked if you want Win95 to search for the hardware. If it has been installed and wasn't recognized, try the "Yes" option, but it may be faster to just say "No" and select the appropriate device yourself.
4. For all the Ethernet devices on our supported list, the default device drivers that came with Win95 work just fine. If it is a relatively new or unsupported device (like the pesky Xircom or Megahertz Ethernet+Modem devices), use the Have Disk option and insert the disk that came with the user's hardware.
5. Once Win95 installs the drivers, it will tell you what resources it has assigned the device to. Write these numbers down. If you are using a non-PnP device, you need to assign the card to these resources. For the 3Com devices, this means running 3C5X9CFG - but not from a DOS Prompt window! Doing so may damage the Ethernet card! Instead, either select Shut Down... from the Start Menu and use the "Restart Computer in MS-DOS Mode" option, or press F8 when the "Starting Windows 95..." prompt appears at system startup, and choose the "Command Prompt Only" boot option.
6. When prompted by Win95, shut down the computer and physically install the Ethernet device.

Section I.5: Installing Ethernet Cards for PC Desktops

As a reminder, turn off the computer and unplug the unit from its power source before proceeding. Remove the computer's cover. If the computer is a tower, lay it on its side with the motherboard chips facing up. Choose an expansion slot. Remove the expansion slot's backplate by taking out the screw with a screwdriver. Keep the screw in a safe place nearby and give the backplate to the user to keep.

1. Get ready to insert the adapter into the expansion slot. You should first line up the gold contacts on the bottom edge of the Ethernet card with the grooves in the expansion slot connector. Make sure they line up exactly and that the card is an exact fit, otherwise you may have chosen the wrong type of slot. Many new computers come with two types of slots, mixing ISA and PCI slots, for example.
2. Once the card is lined up, insert it into the slot by pressing firmly straight down on the card using both hands for balance. Expect a lot of resistance at first. You may want to try pushing down on one end of the card and getting it in first and then pushing in the other end. Keep in mind that EISA slots are deeper than ISA slots and require firmer pressure to seat them correctly.
3. Make sure the card is firmly seated. When the card is finally in, you should feel it "click"into place and the gold contacts on the bottom edge of the Ethernet card should be just barely visible and all of the same length going across the entire length of the connector. For EISA cards, the gold contacts should not show at all.
4. Now secure the card into the slot with the screw that originally held the backplate.
5. Connect the Ethernet card to the wall datajack via 10-Base-T cable.
6. Replace the computer's cover and reconnect all devices and cables.

Section I.6: Installing PCMCIA Ethernet Cards for PC Notebooks

PCMCIA cards are marvels of miniaturization; they are close to a credit card in size yet rival the speed and reliability of full desktop Ethernet cards. There are three types of PCMCIA slots, in order of development: Type I, Type II, and Type III. All are essentially similar except each newer slot provides a little more functionality than its predecessor. Most new notebooks come with one Type III PCMCIA slot, which can also hold two Type II PCMCIA cards. The 3Com Etherlink III PCMCIA card is Type II; the Xircom CreditCard Ethernet device is Type I.

1. As a reminder, turn off the computer and unplug the unit from its power source before proceeding.
2. Grasp the PCMCIA Ethernet Adapter by the edges. Hold the card so that the 68-pin connector is facing toward the adapter slot of the computer.
3. Insert the adapter into the adapter slot in the computer and slide it in until firmly seated. You should feel a bit of resistance after sliding it in 3/4 of the way--keep pushing until you hear a muffled click.
4. Plug in the proprietary PCMCIA Ethernet adapter cable into the card and the other end of the cable into the wall datajack. Use the 10-Base-T (RJ45) coupler provided with the card if you need to attach the adapter cable to a longer, standard Ethernet cable in order to reach the wall datajack.
5. Turn on the computer.
   

Section I.7: Installing Parallel Port Adapters for PC Notebooks

1. As a reminder, turn off the computer and unplug the unit from its power source before proceeding.
2. Connect the Parallel adapter to the parallel port on the machine. If a printer cable is attached to the parallel port, you will have to detach it.
3. If there is a pass-through parallel port on the Ethernet adapter, you can attach the printer cable to the adapter. This will allow the user to print even while connected to the network. Users of the supported Xircom Pocket Ethernet III Adapter can purchase a port multiplexor from Xircom that allows them to do this. If there is no pass-through port or printer, skip this step.
4. Plug in 10-Base-T Ethernet cable into both the adapter and the datajack.
5. Turn on the computer.




Section I.8: Resolving Problems in the System Control Panel

Whether you use PnP or the Add New Hardware wizard, there are times when Win95 just won't recognize the Ethernet device, or will return errors on startup about it. The best place to start is the System Control Panel, located in Start, Settings, Control Panels. Open the Control Panel and select the Device Manager tab to get started.

If you look under the Network Adapters section, there will often be an exclamation point or red "X" through the name of the device if there is something wrong with it. Double-click on the name of the device and see what error message Win95 is reporting.

One common problem, especially with non-PnP devices, is that another device will be trying to use the same resources as the user's Ethernet device. Always click on the Resource tab and check the Conflicting Device List. If another device is conflicting with the Ethernet card, change the IRQ or I/O Range on the Ethernet card to resolve the conflict. For the 3Com devices, this means running 3C5X9CFG - but not from a DOS Prompt window! Doing so may damage the Ethernet card! Instead, either use the "Restart Computer in MS-DOS Mode" option or the F8/Command Prompt boot option, and run the card's configuration utility to resolve the conflict.

In other cases, one or more of the device drivers may not have been installed correctly. Use the Remove option in the Device Manager to remove the Ethernet adapter listing, restart the system, and try adding the hardware again - Win95 will reload the device drivers from diskette or CD-ROM.



---

Section II: LAN Protocols


In the dim dark past, a long, long time ago - last year, to be exact - users and UAs alike had to manually configure Windows 95 machines to enable support for IPX/SPX and access to LAN servers on the FAS Network.


This fall, a new Windows 95 Installer diskette solves the problem by automatically placing the proper settings in the Windows 95 registry. Just install the Ethernet card and get it working, and the Installer takes care of the rest.


Still, the following section is useful for understanding how IPX/SPX is implemented on Windows 95 and what features it offers users.


Section II.1: IPX/SPX on Windows 95

IPX/SPX is the protocol that allows PCs to communicate with the Novell server over the local area network. For Windows 95 users, this server is known as FAS_ACCESS1. It contains DOS and Win3.1 software for use on Windows95 machines for coursework and other purposes.


IPX/SPX is implemented on Win95 as an option in the Network Control Panel, and is installed and configured properly by the FAS Computer Services Win95 installer. In short, the Installer adds the Client for NetWare Networks login shell and the IPX/SPX protocol for communicating with the FAS_ACCESS1 server. For the specific settings needed for IPX/SPX support, see the Windows 95 tip sheet.


Once installed and functional, the user will be able to see network volumes in the My Computer shortcut on their desktop, providing access to publically-available software.


To access this, the user will need to make sure that "Client for NetWare Networks" is set as their Primary Network Login option on the Network Control Panel. They will need to provide their fas username and password when Win95 starts; if they do not, they will have no access to IPX/SPX and FAS_ACCESS1, but TCP/IP should work fine if properly installed.


Logging into FAS_ACCESS1 brings the user to a DOS box that mimics the Blue Menu from HUSC1 days. Users should be careful to select option 6, "Exit to DOS," rather than the Logout option below it; otherwise, their connection to FAS_ACCESS1 will be closed. For the user's convenience, offer to make the Blue Menu go away by adding the line SET _NOMENU=TRUE to their AUTOEXEC.BAT file.


Section II.2: The Perils of NetBEUI

Microsoft created the NetBEUI protocol, originally in Windows for Workgroups, as their answer to the AppleTalk/Appleshare system. It allows users to specify their Workgroup and computer name, a la the ubiquitous zones and machine names on Macs. NetBEUI packets are designed to cross hubs but stay within a LAN, just like AppleTalk/EtherTalk does.


FAS Network Support, however, has shut off NetBEUI support at the router level because it is not routable; the packets it sends out go all over the network, not just to their destination, thereby eating up bandwidth and network efficiency. Users can still see other machines on the same hub as them, but no further; don't bother to install the protocol.


In addition, users should under no circumstances enable SAP Advertising if the option is present. Doing so will attract unwanted and undesired attention from FAS Network Support, and a warning to turn it off.

A solution for peer-to-peer networking is in the pipeline.


---

Section III: TCP/IP


TCP/IP support, like the IPX/SPX protocol, is installed automatically by the Windows 95 Installer. Microsoft's TCP/IP stack is remarkably seamless and quick, providing trouble-free access to the Internet built into the operating system. Win95 uses DHCP, an alternative to Bootp, to dynamically assign IP addresses.


More specific information about TCP/IP on Windows 95, and the appropriate settings, can be found in the Windows 95 Tip Sheet.


Section III.1: DHCP on Windows 95

Windows 95 computers on the FAS Network find out what their IP address is without user or UA intervention from the network through dynamic addressing using Microsoft's DHCP, or Dynamic Host Configuration Protocol. Users should never "hard-wire" their current IP address into their computer; for more information, please see the discussion of this in Chapter 1, Section II.4.


DHCP alleviates this potential hazard by having a central database that matches Ethernet addresses to IP Addresses. So, when your machine starts up, it sends out its Ethernet address (which never changes) onto the network, and the DHCP server returns the assigned IP address. This way, FAS Network Support personnel must only make sure their IP tables are up-to-date, and do not need to worry about notifying thousands of users individually if IP addresses change.


The Windows 95 Installer should set up DHCP as the Default; if it is not, especially on Win95 machines connected to the FAS Network between February 1995 and August 1996, select the TCP/IP option in the Network Control Panel, click Properties, and then select the IP Address tab. Make sure it is set to "Obtain an IP Address Automatically." Users who have previously "hard-coded" their IP addresses in should switch to DHCP. This is a common source of frustration for users who used Win95 in beta form or before the DHCP server was active, and who have now switched rooms.



Section III.2: The WINIPCFG Utility

Happily, Microsoft has included a handy utility with Win95: the WINIPCFG program. This program will show you the Ethernet address and IP address of a system, as well as providing other network information and confirming that the machine has gotten the proper IP lease from DHCP.


Clicking on Start, then Run…, then typing WINIPCFG and pressing the ENTER key will bring up the program's window, showing the machine's IP address and the Ethernet address of the card. Press More Info to find out more technical details. You should not play with the DHCP lease release and renew controls, however!


This program is very useful for diagnosing problems. If it reports "Fatal IP Configuration" at runtime, there is often either a hardware problem with the card (i.e., not installed correctly), or the device drivers are incorrectly installed. If you see the correct Ethernet address, but no IP address - or an IP address of 0.0.0.0 - you know the card is working right, but that there is something wrong with the TCP/IP stack or the jack/patch (i.e. partition, bad wiring, incorrect Ethernet address entered into netconnect database, etc.). WINIPCFG is of no help in diagnosing IPX/SPX problems or issues, of course, other than to hint at hardware problems.



---

Section IV: Miscellaneous Troubleshooting


This section contains both a checklist for common problems as well as a Question & Answer section. Unfortunately, not every problem can be included so only selected "common problems" and the corresponding solutions will be listed.


Much of the information in this Section is listed earlier in this Chapter, but is repeated here for your convenience.


Section IV.1: A Standard Checklist for PC Networking

If something doesn't work properly, this is the standard checklist of steps you should follow. Often a problem occurs because a simple thing is overlooked. Here is the standard checklist:

1. Check to see if the link light on the Ethernet device is on and/or if the receive/trasmit lights are flashing. NOTE: the link, receive, and transmit lights may not be on every PC Ethernet device. If you see no link light even after testing the user's Ethernet cable, their may be something wrong with the datajack or patch.
2. Check all 10-Base-T connections, including card/cable and cable/wall. As part of this, make sure the cable is plugged into the data portion of the jack and not the voice portion. This step is especially important if there is no link light on the Ethernet device.
3. If the Ethernet device is a card, are you sure you seated it properly in its slot? Double-check if at all possible. If the Ethernet device is an external adapter, make sure the connection between the between the computer and the device is solid.
4. Swap the user's Ethernet cable with yours. This step is especially important if there is no link light on the Ethernet device. If this works, make sure the user's cable is not phone cabling (RJ-11), but 10-Base-T unshielded twisted-pair Ethernet cabling ( RJ-45), before declaring the user's cable defective. Never leave your cable in the user's room; make them buy their own.
5. "Rat-Hair Check:" physically blow hard into the datajack (seriously) in order to clear any dust or debris that may have collected there. You may want to also blow into the RJ-45 connector (where the 10-Base-T Ethernet cable connects) on the Ethernet device just in case.
6. Make sure the number of the jack that the user is plugging into is also the number that is specified on the user's task report. Get the Ethernet address of the user's Ethernet device and make sure your results match up with the Ethernet address that is on the task report.
7. If you get absolutely no link indication and have tried different cables, try plugging into the Voice part of the jack. There are a few rare occasions where the datajacks were installed with the jacks reversed. If this is indeed the case, make sure to let the user and Advanced Support know about it.

Before ever paging Advanced Support, you should complete all the steps in this checklist and be ready to report all the results from the steps.



Section IV.2: Other Tips and Tricks

Windows 95 networking is remarkably straightforward; the hints contained throughout this document should be sufficient for most problems.


If you are stuck, be sure to read the messages Windows 95 is telling you! If it says there is a hardware device conflict, there is! If it says it can't find a DHCP server, it can't! The point is, you need to try and digest the messages Win95 is returning and trace them to their cause.