windows 7 - Ethernet (intranet) and Wi-Fi (internet) to work simulatenously
2014-04
Amy
I have seen a couple of questions about this, but I am so limited in my networking knowledge that I have been unable to get those solutions to work for me.
I am trying to connect to an intranet so that I can navigate to internal sites (such as Sharepoint, etc.), but I also need to be able to access my internet over a Wi-Fi connection, which is a 3G Mi-Fi.
What's currently happening is that, when I have the ethernet cable plugged in and Wi-Fi on at the same time, my internet works, but I cannot access the intranet. And it is really a huge pain to switch between the two.
My network details are below (not sure what other details would be needed?):
Wireless:
Default Gateway: 192.168.1.1
IPv4 Address: 192.168.1.102 (preferred)
Subnet mask: 255.255.255.0
DNS: 192.168.1.1
Wired:
Default Gateway: 172.23.42.1
IPv4 Address: 172.23.42.165 (preferred)
Subnet mask: 255.255.255.0
DNS: 172.24.130.12
My Operating System is Windows 7.
Edit - Additional Info:
===========================================================================
Interface List
15...60 67 20 52 19 f8 ......Intel(R) Centrino(R) Advanced-N 6205
19...60 67 20 52 19 f9 ......Microsoft Virtual WiFi Miniport Adapter #2
16...60 67 20 52 19 f9 ......Microsoft Virtual WiFi Miniport Adapter
14...d4 be d9 6a 63 f0 ......Broadcom NetXtreme 57xx Gigabit Controller
18...74 e5 43 54 5d a4 ......Bluetooth Device (Personal Area Network)
1...........................Software Loopback Interface 1
26...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
20...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #5
11...00 00 00 00 00 00 00 e0 Microsoft Teredo Tunneling Adapter
23...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #6
25...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #8
===========================================================================
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.101 281
0.0.0.0 0.0.0.0 172.23.42.1 172.23.42.164 276
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
172.23.42.0 255.255.255.0 On-link 172.23.42.164 276
172.23.42.164 255.255.255.255 On-link 172.23.42.164 276
172.23.42.255 255.255.255.255 On-link 172.23.42.164 276
172.23.45.0 255.255.255.0 172.23.42.1 172.23.42.164 21
192.168.1.0 255.255.255.0 On-link 192.168.1.101 281
192.168.1.101 255.255.255.255 On-link 192.168.1.101 281
192.168.1.255 255.255.255.255 On-link 192.168.1.101 281
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 172.23.42.164 276
224.0.0.0 240.0.0.0 On-link 192.168.1.101 281
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 172.23.42.164 276
255.255.255.255 255.255.255.255 On-link 192.168.1.101 281
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
172.23.45.0 255.255.255.0 172.23.42.1 1
===========================================================================
IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
1 306 ::1/128 On-link
14 276 fe80::/64 On-link
15 281 fe80::/64 On-link
14 276 fe80::7d76:b186:8068:d63a/128
On-link
15 281 fe80::d0f1:717e:6cbb:fa95/128
On-link
1 306 ff00::/8 On-link
14 276 ff00::/8 On-link
15 281 ff00::/8 On-link
===========================================================================
Persistent Routes:
None
Please advise.
Cesar
You need to add static routes for the intranet network.
Example: (from a CMD box)
route add 172.23.45.0 mask 255.255.255.0 172.23.42.1 -p
172.23.45.0 is the network you want to reach. 172.23.42.1 is the gateway that will get you there. -p to make it persistent, it will remain after you restart your computer.
BillP3rd
I think your problem is that you have two default routes (0.0.0.0).
So I'm clear, your Internet connection is via the wireless interface (192.168.1.x/24) and your intranet is via the wired interface (172.23.42.x/24). Is that correct? I'm further assuming that your intranet exists entirely at 172.23.42.x/24 and that 172.23.45.x doesn't actually exist. (Not sure where @Cesar got that from). Note: The '/24' annotation is shorthand for a 24-bit netmask, or 255.255.255.0.
On the assumption that the above is accurate, you need to delete the default route for the intranet interface.
route delete 0.0.0.0 mask 255.255.255.0 172.23.42.1
The following route, from your routing table, takes care of getting intranet traffic to the right place:
172.23.42.0 255.255.255.0 On-link 172.23.42.164 276
tim11g
On my previous notebook, the Dell/Broadcom wireless adapter had an option to automatically disable wireless when a wired network is connected, so I never dealt with multiple active interfaces. My current system has an Intel wireless adapter, and they apparently haven't figured out how to turn it off when there is a wired connection. Unless I explicitly remember to disable wireless when docked, the connection is active.
That shouldn't be a problem (in theory), since the route metric will cause traffic to go over the fastest network (as indicated by the lowest metric in the routing table).
Apparently not - I'm running a backup and seeing the throughput at 25Mbps or so (which is consistent with 802.11g) when a perfectly good Gigabit Ethernet interface is also connected.
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.254 192.168.1.104 10
0.0.0.0 0.0.0.0 192.168.1.254 192.168.1.109 25
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
Windows has correctly identified the Ethernet interface (.104) and assigned it the lower (preferred) metric. So the Ethernet interface should be used exclusively, right?
Why is the Ethernet connection not being used? What other factors are involved? (This is with Windows 7 if it makes a difference)
Entire output of "route print" command (see comment below):
C:\>route print
===========================================================================
Interface List
11...00 18 de 3e 53 82 ......Intel(R) PRO/Wireless 3945ABG Network Connection
10...00 15 c5 af 80 0e ......Broadcom NetXtreme 57xx Gigabit Controller
1...........................Software Loopback Interface 1
17...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
12...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
===========================================================================
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.254 192.168.1.104 10
0.0.0.0 0.0.0.0 192.168.1.254 192.168.1.109 25
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
192.168.1.0 255.255.255.0 On-link 192.168.1.104 266
192.168.1.0 255.255.255.0 On-link 192.168.1.109 281
192.168.1.104 255.255.255.255 On-link 192.168.1.104 266
192.168.1.109 255.255.255.255 On-link 192.168.1.109 281
192.168.1.255 255.255.255.255 On-link 192.168.1.104 266
192.168.1.255 255.255.255.255 On-link 192.168.1.109 281
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.1.104 266
224.0.0.0 240.0.0.0 On-link 192.168.1.109 281
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.1.104 266
255.255.255.255 255.255.255.255 On-link 192.168.1.109 281
===========================================================================
Persistent Routes:
None
IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
12 58 ::/0 On-link
1 306 ::1/128 On-link
12 58 2001::/32 On-link
12 306 2001:0:4137:9e76:3005:82a:b3a3:1099/128
On-link
10 266 fe80::/64 On-link
11 281 fe80::/64 On-link
12 306 fe80::/64 On-link
11 281 fe80::11ad:fcef:18ff:97a9/128
On-link
12 306 fe80::3005:82a:b3a3:1099/128
On-link
10 266 fe80::9524:5f90:dd0:86fb/128
On-link
1 306 ff00::/8 On-link
12 306 ff00::/8 On-link
10 266 ff00::/8 On-link
11 281 ff00::/8 On-link
===========================================================================
Persistent Routes:
None
David Schwartz
Your routing table looks good, now that we see the network routes. That should cover traffic that doesn't try to influence the networking stack. But some applications try to select an interface themselves, and generally, these applications will take the first suitable interface they find.
So let's make sure your wired interface is ahead of the wireless one. To do this, run ncpa.cpl from the Run bar. Under Advanced, select Advanced Settings. In the top pane, find your wired interface and select it. Hit the green up arrow just to the right to move that interface to the top. You will need to reboot to make sure all running programs see the new order.
(Though the KB article is for a different OS, the method and concept is the same.)
Aaron C. de Bruyn
This may be helpful: http://support.microsoft.com/kb/299540 It implies that metrics are assigned specifically for the scenario you describe.
...except in your situation it isn't working. Without access to the source code or definitive information from Microsoft, it's pretty tough to tell why Windows is acting that way in your case.
My only 'guess' would be that maybe your wireless interface comes up first and Windows starts talking with certain remote machines--and those connections stick to the interface they started with to prevent an IP change during an established conversation (which would break the connection). Then you plug your laptop in to Gig Ethernet and Windows doesn't move established traffic over to that connection to avoid dropping those connections.
One way to test that would be to plug in via Ethernet, switch off the wireless and then verify you have fast connectivity. Then turn the wireless back on and see if you keep the faster connectivity.
ultrasawblade
A long shot, but if you are running a backup to another local host on your LAN, perhaps that is changing things somehow.
Any TCP/IP stack can infer that, if a network adapter is set to something like 192.168.111.1 subnet 255.255.255.0, then it can reach any address 192.168.111.2 through 192.168.111.255 simply by sending traffic out of that interface. It wouldn't touch the default gateway, and indeed, Windows may be "short circuiting" for some reason and not bothering to consult the route table for a directly connected subnet.
It also may be due to NetBIOS sending out a broadcast on both interfaces and then Windows received a reply from your machines via the wireless first, so it continued to used that interface for further traffic. This is a very long shot, I don't know too much about the internals of NetBIOS.