This section assumes that your EtherExpress™ 16 adapter passes all diagnostics in the computer you are trying to use it in. If you have not run diagnostics on the adapter, please return to the "Basic Troubleshooting section" and complete the diagnostic tests before continuing to this section.
This section requires some familiarity with Device Manager.
From the list below, pick the sentence that best describes the problem that you are having, and go to that heading to start.
- Windows* displays an error message about the EtherExpress™ 16 when it is booting. (A1)
- I don't get any error messages when Windows starts and Device Manager shows that the card is working, but I can not browse the network. (A2)
- My computer works with the EtherExpress™ 16 and I can browse the network fine, but I have other problems. (A3)
(A1) Windows displays an error message about the EtherExpress™ 16 when it is booting.
Click on the description below that best matches the error message you are having..
- "Your network adapter Intel® EtherExpress 16 or 16TP (0000) is not working properly. You may need to set it up again. For more information, see the Network Troubleshooter in Windows Help." (B1)
- "This DHCP client was unable to obtain an IP network address from a DHCP server. Do you want to see future DHCP messages?" (B2)
- "No domain server was available to validate your password. You may not be able to gain access to some network resources." (B3)
- I am getting an error message, but could not find it listed here. (B4)
B1. "Your network adapter Intel EtherExpress™ 16 or 16TP (0000) is not working properly. You may need to set it up again. For more information, see the Network Troubleshooter in Windows Help."
This message will be displayed if the network adapter driver software could not find the adapter when it loads. This is usually caused by one of two things;
- A: The resources (interrupt or I/O address) assigned to the adapter conflict with another device
- B: The resources the adapter is actually set to do not match the resources the driver is configured for in Windows.
B2. "This DHCP client was unable to obtain an IP network address from a DHCP server. Do you want to see future DHCP messages?"
This message will appear in Windows 95 if the following conditions apply:
- Your network configuration has the TCP/IP protocol added
- The TCP/IP protocol is configured to obtain its TCP/IP addressing information from a DHCP server
- No DHCP server can be found to supply an address.
The TCP/IP protocol depends on a set of numbers (called a TCP/IP address) that uniquely identify each device on the network. This number must be assigned to each device. There are two ways your computer can obtain a TCP/IP address; it can be manually assigned (this is called a "static" address) or it can be assigned automatically from a DHCP server when the computer is booting.
A DHCP (Dynamic Host Configuration Protocol) server is a special server on a network that has a "pool" of addresses that it can dispense to workstations as needed.
This error can be caused by the network adapter not communicating with the network. Run SoftSet and execute the "Run Diagnostics on network" test to insure that the card can communicate over the network cable. If the test fails, see "Guide to EtherExpress 16 Basic Troubleshooting" for information on how to troubleshoot this condition.
If the adapter passes the "run diagnostics on network" test, then how you deal with this error depends on your network configuration.
- Your network requires the TCP/IP protocol and has a DHCP server.
Either the DHCP server is out of TCP/IP addresses, or the adapter cannot communicate with the DHCP server. Contact your network administrator for assistance.
- Your network requires the TCP/IP protocol, but does NOT have a DHCP server.
You will need to assign a static TCP/IP address to the adapter. There are a variety of parameters that must be specified, so this task is best left to a network administrator.
- Your network does not require the TCP/IP protocol, but your dial-up adapter requires it for your Internet connection.
It is typical for a dial-up adapter installed for connecting to the Internet to have the TCP/IP protocol bound to it. Do not remove this protocol if this is the case. Instead, open the network properties by clicking Start, Settings, Control Panel and then double clicking Network. Find the following 2 lines in the list of installed network components on the configuration tab;
TCP/IP -> Dial-Up Adapter
TCP/IP -> Intel EtherExpress™ 16 or 16 TP
Highlight the "TCP/IP -> Intel EtherExpress 16 or 16 TP" line and click remove. Click OK, then restart the computer.
- Your network does not require the TCP/IP protocol, and the EtherExpress 16 is your only network connection.
You do not need the TCP/IP protocol, and can remove it. Open Network Properties by clicking on Start, Settings, Control Panel and double clicking Network. Highlight the TCP/IP protocol and click remove. Click OK and restart the system.
You will need at least one protocol to be able to communicate on the network. The most common choices other than TCP/IP are NETBeui (typically used on Microsoft peer-to-peer networks) and IPX/SPX compatible transport ( typically used on NetWare* networks, but also used on many Microsoft Windows NT networks).
B3. "No domain server was available to validate your password. You may not be able to gain access to some network resources."
See "Troubleshooting "Unable to browse the network" errors" for information on how to troubleshoot this problem.
B4. I am getting an error message, but could not find it listed here.
Write down the exact error message, then go to Search for assistance. Enter the error message there.
(A2) I don't get any error messages when Windows starts and Device Manager shows that the card is working properly, but I can not browse the network.
Go to "Troubleshooting "Unable to browse the network" errors".
(A3) My computer works with the EtherExpress™ 16 and I can browse the network fine, but I have other problems.
Go to Search for assistance.
This applies to: