|
Products affected:
EtherExpress™ PRO/10 and PRO/10+ adapters
Windows* 95 error message: "Unable to browse the network. The network is not accessible."
There are many possible causes for this error message. First, make sure you are using the latest drivers for the Intel® adapter. If you are running third party client software, such as Novell's* IntranetWare* Client, update to the latest version.
If you are running the latest versions of all your network software, determine if your adapter's driver software is loaded and functioning normally. To do this;
- Select Start, Settings, Control Panel, and then double click on the System icon.
- Click on the tab labeled Device Manager.
- Look for an icon labeled Network adapters on the Device Manager list. If there is a plus symbol (+) next to the icon, click on it to expand the entry.
- The Intel® adapter should be listed, and there should not be a yellow exclamation point or red X next to the name. If Novell's* IntranetWare* Client is installed and you are using the 32 bit ODI driver for the Intel® adapter, then another adapter, "Novell ODINSUP", must also be listed and working.
- Double click on the Intel adapter's name. You should be presented with a dialog box for the Intel® adapter. On the general tab, the device status should read "This device is working properly."
If the Device Manager list does not include Network Adapters, or the Network Adapters list does not include your Intel adapter, or if the adapter status is NOT "This device is working properly", then consult the Windows* 95 Troubleshooting Methods document on our website for your adapter as listed below.
If the adapter status is "This device is working properly", then check the following in Control Panel/ Network properties;
- If logging into a workgroup, the workgroup name is identical to other stations in the workgroup and at least one station with that workgroup name on the network has file and printer sharing enabled.
- If logging into a domain, the domain name is correct and the domain server is up and running. Your workgroup name must equal the domain name to see other stations in the domain, or it must equal an existing workgroup within the domain.
- Your computer name is unique on the network (not equal to any other computer or domain name).
- Your Primary Network Logon is set to the network type you are trying to log into.
- The proper client is configured and the same protocols are configured on all machines.
- You are in fact logging in, not canceling the logon.
- When the system is booted to a DOS command prompt and the "Test Adapter" function from the adapter's configuration/test program is run, all tests pass, including the network test.
If all of the above are correct, try running Microsoft* Net Diag (see document, Using Microsoft* Net Diag to Test Network Connections) between this computer and another Windows 95 or Windows for Workgroups computer to check the connection. If your connection does not appear to be functioning, on the adapter's advanced properties settings, try forcing the adapter's duplex mode to match the hub or switch it is attached to. If your adapter has more than one type of network connector, force it to the type of transceiver you are using (TPE for twisted pair, BNC for thin coax, AUI for the 15 pin DIX connector).
If you are logging into a NetWare* network, select the IPX/SPX-compatible Protocol and click on properties. Click on the Advanced tab, then select Frame Type. Change Frame Type from auto to the actual frame type your NetWare server is using.
This applies to:
| 
