Interesting the way it works. (note that the machine with both interfaces is
still an XP).
Both interfaces plugged in (the wireless is a PC card), power up for a
wakeup from hibernate.
The link for the wireless is established, the wired interface is
established. Begin a transfer it occurs only over the wired interface, the
wireless is ignored - as if it had not completed its setup.
Unplug the wired, transfer fails, did not automatically transfer to
wireless, the wireless completes the setup and announces that it is ready.
Started transfer again and it start over the wireless (natch, wired is
unplugged.) Plug the wired back in announced that it was connected again,
but did not start using it for transfers.
Stopped the transfer. Restarted (now both are connected) began with the
wireless after awhile (this was a 1GB transfer) the wired kicked in also.
The wired was running about 0.4%, the wireless running 25%
My times
Wireless only 12:30
Wired only 01:57
Added wireless , only used wired 01:56
remove wired, but wired back in only used wired 01:57
tried to get to internet ... Dog Slow!!!..
repaired wireless, repaired wired, now network fast again, getting a
streaming video, only used wired
repaired wired, repaired wireless, network fast only used wireless.
My results (on XP!!) are that if the wired is available it is used in
preference to the wireless. (both for local and internet)
Wish I had a Vista with both to test.
"turnstyle" <turnstyle@xxxxxx> wrote in message
news:c8de2006-9fff-429a-8392-7df02b9d4f16@xxxxxx
> I'm not in any dual-network situation -- just a home LAN, with a few
> PCs behind the router.
>
> And it is definitely slower when Task Manager indicates that the
> traffic is over wi-fi rather than the wire (I had even wondered if it
> might be a Task Manager cosmetic bug rather than something funky with
> the network).
>
> Do you have both wi-fi and wire available, Vista laptop? It's easy for
> me to reproduce:
>
> 1) boot with both wire and wireless connections
>
> 2) open Task Manager > Networking tab
>
> 3) browse the Web and copy a file over the LAN -- you should see both
> over the wired connection
>
> 4) unplug the Ethernet
>
> 5) browse the Web and copy a file over the LAN -- you should see both
> over the wireless connection
>
> 6) plug the Ethernet back in
>
> 7) browse the Web and copy a file over the LAN -- now the Web traffic
> shows up under the wired connection, and the local file copy under the
> wireless.
>
> I'd certainly be very interested to know if the same happens for you
> -- but I understand it's a bit of a chore, so no worries!
>
> -Scott