Network connection

[Yba]

Hi,
Running XP Pro SP3.
At office, I connect to the LAN as well as the WAN, with two different NICs
simultaneously. Sometimes, this makes a problem. When connecting to some
local resources, the system seems to "lean" on the active connection and if
it is the WAN, I can not reach that local network resource.
Is there a way to instruct applications which NIC to use when launching?

Thanks
Yba

 

[R. McCarty]

If you open Network Connections and click "Advanced" then
Advanced Settings you'll see your network connections listed.
You can select a connection and change it's priority by using the
up/down arrows to configure to your preference.

 

[John Wunderlich]

Hi,
Running XP Pro SP3.
At office, I connect to the LAN as well as the WAN, with two
different NICs simultaneously. Sometimes, this makes a problem.
When connecting to some local resources, the system seems to
"lean" on the active connection and if it is the WAN, I can not
reach that local network resource. Is there a way to instruct
applications which NIC to use when launching?

Packet routing is done strictly by destination IP address according
to the routing table on your machine. You can examine your default
routing table by bringing up a command window and entering the
command:
route print
The general default is that any IP on the same subnet as either NIC
will go out that port. Anything else will go to the "Default
Router". If certain subnets need to go through a particular NIC,
then you need to add entries to your routing table. To do this, use
the "route add" command.

For more info, see:
"TCP/IP Routing Basics for Windows NT"
<http://support.microsoft.com/kb/140859>
Note that this applies to Windows XP as well.

Also, the last part of this article:
"Multiple Default Gateways Can Cause Connectivity Problems"
<http://support.microsoft.com/kb/159168>

HTH,
John

 

[Etal]

Hi,
Running XP Pro SP3.
At office, I connect to the LAN as well as the WAN, with two different NICs
simultaneously. Sometimes, this makes a problem. When connecting to some
local resources, the system seems to "lean" on the active connection and if
it is the WAN, I can not reach that local network resource.
Is there a way to instruct applications which NIC to use when launching?

I think that if what you do on the the LAN is only 'ms
Networks'-based you could unbind the Client and Server for 'ms
Networks' to the WAN NIC, and unbind the 'TCP/IP' Protocol to the
NIC used only for LAN traffic.