NC3163 NIC imbedded NIC card

[Austin Hatcher]

I have a Compaq Proliant ML350 running W2K service pack 2. At present it is connecting to the network via token ring. I need to convert it to Ethernet.

I remove the Token Ring card,
and verify that the imbedded ethernet card is activated in the BIOS.

When W2K starts, it finds the 3163 NIC card and installs the driver.

There are no error messages in any of the log files. The status of the NIC is enabled and connected. However, no packets are being sent or recieved.

It's configured for DHCP, but it's IP address reads 0.0.0.0.

I know the cabling is good as I have tried plugging in the CAT5e cable from a known good working computer.

Any suggestions would be appreciated.

[Paul Slee]

Are you getting a link light on your switch?

[Ernest Ford]

Couple of questions - primarily because you mention converting from token ring to ethernet. It looks like your ML350 is not talking to your DHCP server so -

What's the other end of the CAT5e cable connected to - token ring concentrator or ethernet hub/switch?

What's the DHCP server connected to - token ring concentrator or ethernet hub/switch?

Also - the known good working computer - is that token ring or ethernet?

Has the Cat5e cabling plant been certified as Cat5 compliant? Which pairs have been tested? Ethernet uses the 1-2 & 3-6 pairs, whilst token ring uses the 3-6 & 4-5 pairs, so cabling that is known to work with token ing will not necessarily work for ethernet

[Roger Faucher]

Hi:

Once you get running, you may want to retrieve the latest driver from here:
http://h18023.www1.hp.com/support/files/server/us/locate/20_1120.html#14
assuming you have a vanilla ML350, not a G2 or G3.

Roger

[Neal Bowman]

When you changed from Token Ring to Ethernet, did you also change the jack the cable was plugged into from Token Ring to Ethernet. There is a difference in the wiring in the cross-connects that each system uses. You may have enough of a signal on one pair to indicate you have a link, but the other pair that Ethernet needs is not connected to any port at all. Make sure your Ethernet jack is cross-connected on connections 1,2,3 and 6.

[Austin Hatcher]

Thanks for all the replies.

The other end of the Cat5e cable is
connected to a Cisco 6500 Ethernet
switch. The DHCP server is also connected
to an Ethernet switch.

The known good working ML350(s) have both
been sucessfully converted from Token Ring to Ethernet. Except for the operating system,
all three of these machines are exact
duplicates. (the working machines are running
Windows NT 4.0).

I have already tried the latest NIC card driver.

The CAT5e cable is good.
I have switched cables with a working
ML350. The working ML350 continues
to work fine, while the problem ML350
continues to be a problem.

[Terri Harris]

To isolate if this is a Windows 2000 DHCP issue or the NIC itself (hardware or software), assign a static IP address to the NIC card. Can you now ping to and from the server? If so, the issue is with DHCP...

[Neal Bowman]

Have you verified the NIC port speed? If there is a mismatch in the NIC settings and the switch port settings, you will not be able to communicate. I have also seen issues where there is a timing mismatch when both NIC and switch are set for AUTO/AUTO. Make sure that at least one of the devices is set for 10/100 and Half/Full Duplex (depending on the capacity of the switch).

What does the Compaq/HP NIC Teaming Utility show? If it is installed, you can view statistics about the NIC, errors, over/under-runs.