Wired & Wireless Connections simultaneously

kentwjames

Honorable
Apr 19, 2013
1
0
10,510
I am currently living in an apartment with public wireless internet connection. I have a HP 4000 ( I write & print a lot for my job) with ethernet connectivity. Would like to connect to the printer via an ethernet hub/switch. I have 2 computers that I want to connect to the printer. When I connect to the ethernet hub it kills my wireless internet connectivity even though both networks are recognized. Any ideas would be appreciated.
 
I suspect your ethernet hub/switch is more likely a router, or at least has its own DHCP server. If that's the case, then what's probably happening is that when you’re connected to the wired network, its DHCP server is assigning a default gateway which is overriding the default gateway assigned by the wireless connection. And since you can only have ONE default gateway, and the default gateway assigned by the hub/switch isn't really connected to the internet, you lose internet connectivity.

The way to prevent this is to use static IP assignments w/ the local network and NOT specify a default gateway on that network.
 

spectrewind

Distinguished
Mar 25, 2009
446
0
18,790


Another possibility would be changing the BINDING ORDER of your connections, since you have more than one:
Start/Run > NCPA.CPL > Toolbar [Advanced] > Advanced Settings.
In the Advanced settings window, you might try changing the ORDER of the connections. Based on your description, I would guess that your wired connection is above your wireless connection on this list.

Someone also mentioned a router vs. switch. If it is a router, just log into the admin page of it and disable the DHCP server, which will basically turn it into a switch, for what you're doing.
 

spectrewind

Distinguished
Mar 25, 2009
446
0
18,790


You can have multiple default gateways (with cost metrics) under the advanced TCP/IP settings window, IP Settings tab, second window. Basically for devices with more than one interface. I do not see it used much, but it's there.
 
^^ Not a bad idea, but in my experience, the binding order isn't always reliable. Sometimes Windows seems to ignore it, at least for certain things. It *should* work that way, you would think, but I've just run across too many cases where it didn't, so I tend to avoid it as a recommendation. Using static IPs always works however.

Another option (assuming it is a router) is instead of disabling DHCP, disable the WAN. I suspect if you do, then the DHCP server won't return a default gateway at all, and that will correct the problem as well (and of course, you retain the convenience of having a DHCP server). But here again, it's not always a reliable solution because not all routers allow you to disable the WAN. Plus, a lot of ppl wouldn't even know what I was talking about! So once again, static IP assignments to the rescue.

So definitely several ways to skin this cat, take your pick.

 


Yeah, you can have multiple default gateways DEFINED w/ different metrics, but for all intents and purposes, only one is ever used (otherwise it wouldn't be a default). It’s just better to eliminate it and avoid the confusion. Otherwise we’re now into having non-technical users making metric changes (ugg). I always thinking, what’s the EASIEST solution that can be implemented by the MOST ppl w/ the LEAST confusion. In my book, that’s static IPs. But I'll grant you, metrics is plausible.