Wow! That worked. Changed the metrics to 1 (LAN) and 100 (Wireless),
then pulled the internet on the lan and still have internet access and
can still print. Excellent job, Jamie!
On 11/22/2017 9:27 AM, Jamie Furtner wrote:
Try changing the interface metric like I said below. By default
Try changing the interface metric like I said below. By default Windows
will prefer a wired connection over a wireless one. I don't know if that
will work or not though but it's worth a shot. It's worth a shot though
I don't know if it will work.
On 2017-11-22 6:56 AM, Steve Tomporowski
Well, I knew this was going to be a learning experience. I took Thane's
advice and changed my DHCP network to 192.168.2.1. Did the stupid and
forgot to change the subnet mask. Reset the router, changed both
address and subnet mask, then found out that I had to run the Windows
troubleshooter
The behaviour you're seeing is likely because there's a router handling
DHCP on the wired network, and that DHCP packet also has a default
gateway. When you plug in the cable, the computer receives a DHCP
response from the router saying that it's a valid connection, and most
of the time
If you have two networks (with different IP blocks) then it should work
fine:
NIC 1 - 192.168.1.x
NIC 2 - 192.168.2.x
T
We're dealing with Win10 here. We are trying to get rid of an extra
cable internet connection at my house. The downstairs currently has
it's own internet with a wired network that includes two servers and a
printer. What I need to do is keep the wired network without internet
and access the
