In article <A0C63DB4-BA1B-41AE-91F9-3582E0D5C271@microsoft.com>,
HrundiBakshi <HrundiBakshi@discussions.microsoft.com> wrote:
>"Steve Winograd [MVP]" wrote:
>> To be sure what's happening, you have to look at every entry in the
>> route table. Open a command prompt window (Start | Run | cmd) and run
>> this command to write the route table to a file:
>>
>> route print >route.txt
>>
>> Then, open the "route.txt" file and copy/paste it into a newsgroup
>> reply.
>
>Here it is:
>
>************************************************* ***********
>Interface List
>0x1 ........................... MS TCP Loopback interface
>0x2 ...xx xx xx xx xx xx ...... Belkin 802.11g Network Adapter - Packet
>Scheduler Miniport
>0x3 ...xx xx xx xx xx xx ...... U.S. Robotics 10/100 PCI NIC TX - Packet
>Scheduler Miniport
>0x4 ...xx xx xx xx xx xx ...... U.S. Robotics 802.11g Wireless Turbo Adapter
>- Packet Scheduler Miniport
>================================================= ====
>================================================= ====
>Active Routes:
>Network Destination Netmask Gateway Interface Metric
> 0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.100 20
> 0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.104 2
> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
> 192.168.0.0 255.255.255.0 192.168.0.100 192.168.0.100 20
> 192.168.0.100 255.255.255.255 127.0.0.1 127.0.0.1 20
> 192.168.0.255 255.255.255.255 192.168.0.100 192.168.0.100 20
> 192.168.1.0 255.255.255.0 192.168.1.104 192.168.1.104 2
> 192.168.1.104 255.255.255.255 127.0.0.1 127.0.0.1 2
> 192.168.1.255 255.255.255.255 192.168.1.104 192.168.1.104 2
> 192.168.123.0 255.255.255.0 192.168.123.100 192.168.123.100 100
> 192.168.123.100 255.255.255.255 127.0.0.1 127.0.0.1 100
> 192.168.123.255 255.255.255.255 192.168.123.100 192.168.123.100 100
> 224.0.0.0 240.0.0.0 192.168.0.100 192.168.0.100 20
> 224.0.0.0 240.0.0.0 192.168.1.104 192.168.1.104 2
> 224.0.0.0 240.0.0.0 192.168.123.100 192.168.123.100 100
> 255.255.255.255 255.255.255.255 192.168.0.100 192.168.0.100 1
> 255.255.255.255 255.255.255.255 192.168.1.104 192.168.1.104 1
> 255.255.255.255 255.255.255.255 192.168.123.100 192.168.123.100 1
>Default Gateway: 192.168.0.1
>================================================= ====
>Persistent Routes:
> None
>************************************************* ***********
>
>Believe it or not, the default NIC is 192.168.0.100, i.e. the one with
>metric 20. (I guess this can also be seen from the "Default Gateway" field
>above). This happens to be the wired Ethernet card. I was counting on the
>wireless (Belkin) NIC to act as the default, hence the lower metric (2).
>
>Why is this happening? What am I doing wrong?
>
>(Thanks for the replies btw.)
Thanks for posting the route table.
I see what you're saying, and I can't explain why it shows the Default
Gateway as 192.168.0.1. How do you know that the system is actually
using the wired Ethernet card for Internet access?
I'm trying to duplicate the behavior on my computer by specifying
various metric values for two network connections, but I haven't been
able to so far. I've opened the Status window for each connection,
and I'm looking at the Sent and Received packet counts to be sure
which connection it's using. I'll post a reply if I find out anything
more.
--
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