When a laptop has both wireless and wired connection at the same time, we want to make sure the network traffic is going through the ethernet cable first instead of going via air. A lot of research was telling me that Windows has the preferred route to higher throughput interface. I found this to be true on Windows 7 that it assigned metric 10 on the wired connection and metric 25 on wireless. Here is the problem…
When I have both network connection on and start trasfer files from a server, in Task Manager networking tab I can see the traffic is going through the wired connection as expected. However, if the laptop is “on wireless first” without network cable, then connection to a server, say Server1, is initialed, Windows 7 seems memorize this path or route. Later after the ethernet cable is plugged in, the traffic going to Server1 will be still on wireless interface rather than the wired connection. Looks like metric is not playing the magic any more once there is cache in the system. On the other hand, with both connection on, if I try to connect to another server, the wired connection will be taken. To me, the metric only works for the first time connection.
Any thought to correct the problem and make ethernet connection always be the preferred route?
You must be logged in to reply to this topic.
Create a free account today to participate in forum conversations, comment on posts and more.