Two PC's on crossover kills WiFi
in [Wireless]
|
Prev: "Wireless switch not on"?? Prev good network, now gone.
Next: "Wireless switch not on"?? Prev good network, now gone.
From: just bob on 15 Apr 2008 12:46 Connecting two PC's with a crossover cable kills the wifi internet. When we travel we usually have two laptops connected to the same public WiFi to check email and surf the web but we also need to share many very large files between the two laptops. Since both computes have gigabit NIC's I tried using a crossover cable to link them to get better speeds than over WiFi. Both laptops are identical Dell D630 with internal Wifi adapters. Laptop-A's GB NIC is assigned 172.16.16.1 and Laptop-B is 172.16.16.2, subnet mask is 255.255.255.0 and gateway is themselves. When I do this the two PC's see each other just fine but the WiFi to the internet stops working. I believe it is a routing to default gateway issue but I'm not sure how to cure this. How do you force the PC to use the WiFi as the default gateway, if that will solve the problem? I have tried using the route command but even though I craft the command statement exactly as the help doc says it comes back with an error. route add 0.0.0.0 MASK 255.255.0.0 192.168.1.10 If you have any ideas how to make this work please let me know! Thanks, -Bob
From: John on 15 Apr 2008 13:12 Set the "interface metric" on your WiFi NIC to be higher than that of wired NIC. Read the following: http://technet2.microsoft.com/windowsserver/en/library/6c7c7ab2-cfdc-4dfe-8560-570d3859f5b11033.mspx Particularly the following section: Using multiple gateways If you have multiple interfaces and you configure a default gateway for each interface, TCP/IP by default automatically calculates an interface metric that is based on the speed of the interface. The interface metric becomes the metric of the default route in the routing table for the configured default gateway. The interface with the highest speed has the lowest metric for its default route. The result is that whenever multiple default gateways are configured on multiple interfaces, the fastest interface will be used to forward traffic to its default gateway. "just bob" <kilbyfan(a)aoldotcom> wrote in message news:JK2dnd4QmKVzRpnVnZ2dnUVZ_tijnZ2d(a)supernews.com... > Connecting two PC's with a crossover cable kills the wifi internet. > > When we travel we usually have two laptops connected to the same public > WiFi to check email and surf the web but we also need to share many very > large files between the two laptops. Since both computes have gigabit > NIC's I tried using a crossover cable to link them to get better speeds > than over WiFi. > > Both laptops are identical Dell D630 with internal Wifi adapters. > > Laptop-A's GB NIC is assigned 172.16.16.1 and Laptop-B is 172.16.16.2, > subnet mask is 255.255.255.0 and gateway is themselves. > > When I do this the two PC's see each other just fine but the WiFi to the > internet stops working. I believe it is a routing to default gateway issue > but I'm not sure how to cure this. How do you force the PC to use the WiFi > as the default gateway, if that will solve the problem? I have tried > using the route command but even though I craft the command statement > exactly as the help doc says it comes back with an error. > > route add 0.0.0.0 MASK 255.255.0.0 192.168.1.10 > > If you have any ideas how to make this work please let me know! > > Thanks, > -Bob > > >
From: John on 15 Apr 2008 13:16 I meant to say "lower" instead of "higher". Lower interface metric has higher precedence. "John" <a> wrote in message news:egkrsvxnIHA.5692(a)TK2MSFTNGP03.phx.gbl... > Set the "interface metric" on your WiFi NIC to be higher than that of > wired NIC. > > Read the following: > http://technet2.microsoft.com/windowsserver/en/library/6c7c7ab2-cfdc-4dfe-8560-570d3859f5b11033.mspx > Particularly the following section: > > Using multiple gateways > > If you have multiple interfaces and you configure a default gateway for > each interface, TCP/IP by default automatically calculates an interface > metric that is based on the speed of the interface. The interface metric > becomes the metric of the default route in the routing table for the > configured default gateway. The interface with the highest speed has the > lowest metric for its default route. The result is that whenever multiple > default gateways are configured on multiple interfaces, the fastest > interface will be used to forward traffic to its default gateway. > > > "just bob" <kilbyfan(a)aoldotcom> wrote in message > news:JK2dnd4QmKVzRpnVnZ2dnUVZ_tijnZ2d(a)supernews.com... >> Connecting two PC's with a crossover cable kills the wifi internet. >> >> When we travel we usually have two laptops connected to the same public >> WiFi to check email and surf the web but we also need to share many very >> large files between the two laptops. Since both computes have gigabit >> NIC's I tried using a crossover cable to link them to get better speeds >> than over WiFi. >> >> Both laptops are identical Dell D630 with internal Wifi adapters. >> >> Laptop-A's GB NIC is assigned 172.16.16.1 and Laptop-B is 172.16.16.2, >> subnet mask is 255.255.255.0 and gateway is themselves. >> >> When I do this the two PC's see each other just fine but the WiFi to the >> internet stops working. I believe it is a routing to default gateway >> issue but I'm not sure how to cure this. How do you force the PC to use >> the WiFi as the default gateway, if that will solve the problem? I have >> tried using the route command but even though I craft the command >> statement exactly as the help doc says it comes back with an error. >> >> route add 0.0.0.0 MASK 255.255.0.0 192.168.1.10 >> >> If you have any ideas how to make this work please let me know! >> >> Thanks, >> -Bob >> >> >> > >
From: Phillip Windell on 15 Apr 2008 18:10 Two choices: Choice #1 - The easy way Manually configure The TCP/IP specs of the nics you're using with the crossover cable. Make them the same subnet with each other, but different than the wireless Nics Leave the Default Gateway blank,..it is used for crossing subnets and they are not crossing subnets,..it is therefore not supposed to be used,..leave it blank Choice #2 - The long annoying and possibly less stabile way Change the binding order of the nics. Set the WiFi nic as the first. I'll use XP as the example,..you can translate it to Vista if you run Vista. Properties of Network Places--> Advanced from the Top Menu--> Advanced Settings from the Dropdown Menu--> Use the side arrows at the Upper box the set the Nic you want to be at the top Now it should "favor" that nic if they both have conflicting Default Gateways Default Gateways are supposed to be treated as *global* for the whole machine, hence there should only be one on one nic. This situation is an example of why a machine should never have more than one Default Gateway unless the Default Gateway IP#s are in the same subnet and are bound to the same Nic (used for Dead Gateway Detection, see below). That has been the Rule for years since TCP/IP was invented,...things haven't changed much. If it doesn't work after this then you just simply will not be able to dependably use the Wifi at the same time as using a crossover between the wired nics. You'll have to pick one or the other at a given moment by disabling the other. I hope the links are still good,...they are getting kind of old. Q128978 - Dead Gateway Detection in TCP/IP for Windows NT http://support.microsoft.com/support/kb/articles/Q128/9/78.ASP Q171564 - TCP/IP Dead Gateway Detection Algorithm Updated for Windows NT http://support.microsoft.com/support/kb/articles/Q171/5/64.ASP Q1157025 - Default Gateway Configuration for Multihomed Computers http://support.microsoft.com/support/kb/articles/Q157/0/25.ASP Q175767 - Expected Behavior of Multiple Adapters on Same Network http://support.microsoft.com/support/kb/articles/Q175/7/67.ASP -- Phillip Windell www.wandtv.com The views expressed, are my own and not those of my employer, or Microsoft, or anyone else associated with me, including my cats. ----------------------------------------------------- "just bob" <kilbyfan(a)aoldotcom> wrote in message news:JK2dnd4QmKVzRpnVnZ2dnUVZ_tijnZ2d(a)supernews.com... > Connecting two PC's with a crossover cable kills the wifi internet. > > When we travel we usually have two laptops connected to the same public > WiFi to check email and surf the web but we also need to share many very > large files between the two laptops. Since both computes have gigabit > NIC's I tried using a crossover cable to link them to get better speeds > than over WiFi. > > Both laptops are identical Dell D630 with internal Wifi adapters. > > Laptop-A's GB NIC is assigned 172.16.16.1 and Laptop-B is 172.16.16.2, > subnet mask is 255.255.255.0 and gateway is themselves. > > When I do this the two PC's see each other just fine but the WiFi to the > internet stops working. I believe it is a routing to default gateway issue > but I'm not sure how to cure this. How do you force the PC to use the WiFi > as the default gateway, if that will solve the problem? I have tried > using the route command but even though I craft the command statement > exactly as the help doc says it comes back with an error. > > route add 0.0.0.0 MASK 255.255.0.0 192.168.1.10 > > If you have any ideas how to make this work please let me know! > > Thanks, > -Bob > > >
From: just bob on 15 Apr 2008 19:21
Choice 1 worked nice except.... XP will not let me share files. I can ping each other now and both machines can access the internet, so your tip worked. I just do not know how to share files between domain members when they are not on the domain. Any ideas? Thanks again! "Phillip Windell" <philwindell(a)hotmail.com> wrote in message news:u$017V0nIHA.2188(a)TK2MSFTNGP04.phx.gbl... > Two choices: > > Choice #1 - The easy way > Manually configure The TCP/IP specs of the nics you're using with the > crossover cable. > Make them the same subnet with each other, but different than the wireless > Nics > Leave the Default Gateway blank,..it is used for crossing subnets and they > are not crossing subnets,..it is therefore not supposed to be used,..leave > it blank > > Choice #2 - The long annoying and possibly less stabile way > Change the binding order of the nics. Set the WiFi nic as the first. > I'll use XP as the example,..you can translate it to Vista if you run > Vista. > > Properties of Network Places--> > Advanced from the Top Menu--> > Advanced Settings from the Dropdown Menu--> > Use the side arrows at the Upper box the set the Nic you want to be at the > top > > Now it should "favor" that nic if they both have conflicting Default > Gateways > > Default Gateways are supposed to be treated as *global* for the whole > machine, hence there should only be one on one nic. This situation is an > example of why a machine should never have more than one Default Gateway > unless the Default Gateway IP#s are in the same subnet and are bound to > the same Nic (used for Dead Gateway Detection, see below). That has been > the Rule for years since TCP/IP was invented,...things haven't changed > much. > > If it doesn't work after this then you just simply will not be able to > dependably use the Wifi at the same time as using a crossover between the > wired nics. You'll have to pick one or the other at a given moment by > disabling the other. > > I hope the links are still good,...they are getting kind of old. > > Q128978 - Dead Gateway Detection in TCP/IP for Windows NT > http://support.microsoft.com/support/kb/articles/Q128/9/78.ASP > > Q171564 - TCP/IP Dead Gateway Detection Algorithm Updated for Windows NT > http://support.microsoft.com/support/kb/articles/Q171/5/64.ASP > > Q1157025 - Default Gateway Configuration for Multihomed Computers > http://support.microsoft.com/support/kb/articles/Q157/0/25.ASP > > Q175767 - Expected Behavior of Multiple Adapters on Same Network > http://support.microsoft.com/support/kb/articles/Q175/7/67.ASP > > > -- > Phillip Windell > www.wandtv.com > > The views expressed, are my own and not those of my employer, or > Microsoft, > or anyone else associated with me, including my cats. > ----------------------------------------------------- > > "just bob" <kilbyfan(a)aoldotcom> wrote in message > news:JK2dnd4QmKVzRpnVnZ2dnUVZ_tijnZ2d(a)supernews.com... >> Connecting two PC's with a crossover cable kills the wifi internet. >> >> When we travel we usually have two laptops connected to the same public >> WiFi to check email and surf the web but we also need to share many very >> large files between the two laptops. Since both computes have gigabit >> NIC's I tried using a crossover cable to link them to get better speeds >> than over WiFi. >> >> Both laptops are identical Dell D630 with internal Wifi adapters. >> >> Laptop-A's GB NIC is assigned 172.16.16.1 and Laptop-B is 172.16.16.2, >> subnet mask is 255.255.255.0 and gateway is themselves. >> >> When I do this the two PC's see each other just fine but the WiFi to the >> internet stops working. I believe it is a routing to default gateway >> issue but I'm not sure how to cure this. How do you force the PC to use >> the WiFi as the default gateway, if that will solve the problem? I have >> tried using the route command but even though I craft the command >> statement exactly as the help doc says it comes back with an error. >> >> route add 0.0.0.0 MASK 255.255.0.0 192.168.1.10 >> >> If you have any ideas how to make this work please let me know! >> >> Thanks, >> -Bob >> >> >> > > |