In article <47D76854-3240-49AE-951C-E3B063B2E8EB@microsoft.com>,
HrundiBakshi <HrundiBakshi@discussions.microsoft.com> wrote:
>"Steve Winograd [MVP]" wrote:
>
>> 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?
>
>It is as simple as surfing into one of these MyIP sites that display yer IP.
>On each of the two NICs I should get different IPs as they connect to
>different/independent ISPs. (Note that I have made no significant changes to
>IE's configuration, and thus I assume it uses the default connection.)
>
>Anyway, even though, as a rule, the default NIC is the one with lower metric
>(wireless Belkin), from time to time it just happens that the system defaults
>to the other one (wired USR). So far I haven't been able to tell *when* that
>happens. (And no, the wireless connection is NOT down when that happens.)
>
>To be sure, given this behavior, I can't really trust this mechanism to
>handle Internet routing, especially in case of very sensitive traffic.
>Microsoft will have to do better than this "metric" tweak. At the very
>minimum, I should be able to disable this annoying "failover" behavior, so
>that just in case my Internet is *not* given by the dsired NIC, Internet
>traffic should at least *not* go via other NICs. In other words, if the
>Internet doesnt go through the desired NIC, then there should be no Internet
>(at least for the application in question).
>
>I don't really like this "default connection" idea. Each application should
>firmly designate the NIC they use for Internet traffic from the get-go.
>(Actually most of the newer applications are indeed designed with some "local
>IP binding" option or other. Unfortunately IE isn't one of them.)

Here are two relevant Microsoft "Cable Guy" articles:

Windows XP and Windows Server 2003 Behavior When Connected to Both
Wired and Wireless Networks
http://www.microsoft.com/technet/com...uy/cg0405.mspx

Default Gateway Behavior for Windows TCP/IP
http://www.microsoft.com/technet/com...uy/cg0903.mspx

Please look at the section on "Dead Gateway Detection" in the second
article. Perhaps that's what's happening on your computer.
--
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