Discussion Locked

Network adapter card in server

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,
I have a H.P. Lh4 Server connected to a windows nt4.0 network. It's a stand alone Server. I recently installed a second network adapter card. Configured it W/ a static ip address. Creating a private network keeping it off the main network.
When I rebooted the system it no was no longer on the network. When I would delete the driver for the new card it was back on the network. I tried switching the pci slots that the new card was installed on w/the same results...Why would the installation of the new card take the computer off the network when the original card was never touched...Any help would be appreciated..

7 replies

by curlergirl

Check your binding order - usually a new NIC will be put first in the binding order in NT. If that's the case, and it's IP address is not on the same subnet as the rest of your network, it would certainly take your server off the network. You needto make sure that the NIC that communicates with the rest of your network is first in the binding order for all protocols/services. Hope this helps!

by vh_s

Check the IP address.

I think you used the same network address as the first one. NT wouldn't accept this.

So, if the first is: 192.168.0.1 / 255.255.255.0, the second should be: 192.168.1.1 / 255.255.255.0.

vh_s

by curious_george

Answer #2 is 1 of 2 places to start. You certainly must make sure that you are using discrete subnets and masks.

Binding order as suggested in Answer #1 does not matter, incoming requests would still reach the server and be responded to based upon the connection they came in through.

You need to insure that you do not have a hardware i/o conflict firstmost. Make sure both network cards use different IRQ and I/O address settings, LH4 servers do not automatically manage this well, especially when running NT4 which is not Plug and Play. It is VERY unlikely that the probllem is a driver conflict. A hardware conflict it the MOST LIKELY cause of your problem.

This discussion is closed to new replies.