Help needed setting up a Home Network

[User217]

Guys,

I run a small home network that consists of a TP Link N750 Router (Non ADSL), TP Link 16 port unmanaged switch, D-Link DPR-1061 Print Server and two Western Digital NAS Drives. I have connected all this hardware with static IP's to the Router as I have found it works best to preserve the IP addresses. I use the routers default IP Address of 192.168.0.1.

To get ADSL to work, I had to connect an TP-Link TD-8840T ADSL modem to the mix. I didn't go for a high end modem as I just need the modem for the ADSL signal. The modem's IP address is the default address is 192.168.1.1.

I have never had issues with this setup. As a matter of fact, anything I connect to the network as always worked, but since I upgraded to Windows 10, all HELL has broken loose!

For reasons totally and utterly unknown, Windows 10 has issues connecting to a network who's IP is 192.168.0.1 wile the ADSL router is on 192.168.1.1! Every time I start Windows 10, it will report that I have a network connection, but that there is no ADSL connection on my network. Running a diagnostic tells me that my broadband modem needs to be restarted. I have to restart my PC multiple times before it decides that it can now see the ADSL connection...

I have tried to link the ADSL modem and the router together so that there is only one range of IP addresses, but nothing I do seem to work! I tried DHCP Relay and I have tried changing the IP address of the modem to fall under that of the router... No joy at all!

Before I kick this modem into martian orbit, can someone PLEASE help!

 

[agentrfr]

That isnt the same subnet by default (255.255.255.0 for the 192.168.0.1 address, but the same for the 192.168.1.1, and NOT 255.255.0.0). Change the modem to 192.168.0.2 and have it bridge to the router, let router do the DHCP

 

[User217]

That isnt the same subnet by default (255.255.255.0 for the 192.168.0.1 address, but the same for the 192.168.1.1, and NOT 255.255.0.0). Change the modem to 192.168.0.2 and have it bridge to the router, let router do the DHCP

IT'S ALIVE!!!

I have been banging my head against the wall for the past few days, never realizing that the solution was that simple! You have made my day!

THANK YOU SO MUCH!

For those interested, I did change the modem IP address as suggested, but that made the modem inaccessible on my network. I then factory reset the modem and only bridged the connection to see what will happen after changing the default password. I then logged into my ISP account via my router and voila!

I still cannot believe it was that simple!

 

[Johnatan56]

That isnt the same subnet by default (255.255.255.0 for the 192.168.0.1 address, but the same for the 192.168.1.1, and NOT 255.255.0.0). Change the modem to 192.168.0.2 and have it bridge to the router, let router do the DHCP

You beat me to it
@OP, I had your problem a month ago setting up at a friends house.

 

[agentrfr]

IT'S ALIVE!!!

I have been banging my head against the wall for the past few days, never realizing that the solution was that simple! You have made my day!

THANK YOU SO MUCH!

For those interested, I did change the modem IP address as suggested, but that made the modem inaccessible on my network. I then factory reset the modem and only bridged the connection to see what will happen after changing the default password. I then logged into my ISP account via my router and voila!

I still cannot believe it was that simple!

np

It boggles my mind as to why they sell these things to the public as a NAT/WAN by default... if you're running a public wifi then sure - but 90% of the people that buy these things are household customers

 

[RoganDawes]

It may be worth detailing exactly how the router, modem and PCs are connected to each other, in order to explain the behaviour you are seeing.