Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have an HP server (Windows Server 2003) with 2 external NICs (couldn't get the builtin NIC to work).

One is for an internal network of 4 PCs and the other is for part of an Internet-facing network. Many times a day, we have to disable the internal NIC in order to get the other NIC to see the network.

I know this is happening on a server, but the issue is more related to the conflicts on the NICs. Any suggestions from the community on where to look for a solution?

share|improve this question

Realised that Windows did not like to play with 2 NICs. Workaround was to create a persistent static routes for the internal network with a "route -p add ...."

share|improve this answer
    
Hmmm. I have multi-homed several Windows servers over the years and never had to do that. Windows works just fine with multiple NICs. Just remember that only the Internet facing one should have a gateway applied in this configuration. – Brian Knoblauch Mar 9 '10 at 18:56
    
You may well have a point about the Internet facing one having a gateway applied. Point noted. We also have 4 other Window servers multi-homed which did not have a problem, but the difference being that these four units connect to a Layer3 switch, whereas this particular unit only connects to a HP ProCurve switch. – funbi_grace Apr 8 '10 at 1:22

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .