"Primera" said:
I have two nics in my winxp prof machine. One is
connected to a local network that has a Red Hat Linux
server on it acting as a PDC/Samba Server. The other nic
is connected to my internet (cable modem). It would
appear that sometimes the computer "stalls" when trying
to find an address as if it doesn't know which nic to
use. Is there a way for me to manually define this?
Thanks
Windows uses the TCP/IP route table to determine which network
connection to use to reach a target IP address. The decision process
is well-defined, and I don't think that it's possible for it to cause
the computer to stall. You can see the route table by entering this
line at a command prompt:
route print
To decide which route to use, Windows examines each route table entry
in turn and does a logical "and" of the target IP address with the
subnet mask of the route. If that value matches the destination IP
address of the route, the route matches. If two or more routes match,
Windows uses the one with the longer subnet mask (more 1's). If the
subnet masks are equal, it uses the route with the lower metric.
To assign a metric to a network connection:
1. Open the Network Connections folder.
2. Right click the desired connection.
3. Click Properties | Internet Protocol (TCP/IP).
4. Click Properties | Advanced.
5. Un-check "Automatic metric".
6. Enter a number between 1 and 9999 for the "Interface metric".
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)
Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.
Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com