Mulithomed system

  • Thread starter Thread starter william r. riley
  • Start date Start date
W

william r. riley

We have a multihomed W2K Pro system that interfaces between our network and
the state. If we need to reboot the system it will almost always bring up
the state connection first causing it to not interface with our network
correctly (i.e. cannot ping, browse, etc...). If we disable the state
connection and wait for the system to realize that our network is there, it
will then interface with our network normally and then we can bring up the
state connection and have it work. When we do this we are not able to
connect to the state resource for 5-to-15 minutes, which is somewhat of a
pain since we have to stay at the site until we confirm that the service
starts and connects correctly. When we had the system on a NT workstation
it worked just fine. Any ideas on how to remedy the problem or if you can
set the default order for the NICs to load?

Thanks.
 
In Network Connections, Advanced, advanced you should be able to set the
order of the nics.

Marina
 
Right click on My Network Places, choose Properties. In this new window,
click the Advanced menu option, then choose Advanced Settings. Here you can
change the order your NIC's load.

Good Luck. . .
 
The NICs are already set to load internal network first and the external
(state) second. Do we need to look at using static routes? If so, how
would we go about setting these? I failed to mention in the original
posting that the biggest problem is that it will not connect across our
internal T1 until we disable the state connection and let it discover our
network. Sorry about that.
 
Back
Top