New Router on Different Subnet

MarkHNC

Honorable
Jun 2, 2012
6
0
10,510
I seem to be in an endless loop/conundrum. I just bought a TP-Link Archer C7 AC1750 router to replace an aging/flaking well-out-of-warranty Netgear router. As context, on my wired gigabit Ethernet home network, I have a Windows server that provides, among other things, DHCP and DNS. I have the server set with a static IP of 192.168.1.200 and subnet mask of 255.255.255.0. The DHCP server address pool for clients is 192.168.1.201 to 192.168.1.251. The Netgear router's IP is 192.168.1.1 with DHCP disabled. No problems, other than the wireless recently winking out, requiring the router to be reset -- the reason for replacement. Wired LAN connectivity is solid whether wireless is working or not. All of my PC's are members of a non-public/internal domain controlled by the Windows Server, which is likely contributing to my problem.

I disconnected the Netgear, and connected the TP-Link according to instructions (cable modem off; connect new router to cable modem; cable modem on and wait for full connect; power router). Proper lights all 'round. The TP-link router's address is, according to the documentation, 192.168.0.1. However, attempts to reach the router from wired PC's at either http://tplinkwifi.net or http://192.168.0.1 results in "not found."

If I am understanding my problem correctly, I cannot get into the router's interface to change it to a different address (i.e. subnet) without first changing it to a different subnet. It was an easy matter to connect my Droid mobile to the TP-Link's 5G WiFi using the default password on the router's label, thinking that I could use the Droid's browser at least get in and change the router's IP. I thought that, surely, connecting the Droid directly to the TP-Link router wirelessly would get the Droid an address on the same subnet as the router, and so solve the problem. Same results as with the wired IP: "not found." So I connected the Droid to 4G cellular and downloaded the TP-Link tether app, and then re-enabled WiFi/reconnected to the TP-Link via wireless, and the app found no devices, despite being wirelessly connected to one.

Anyone got any idea how I get out of this maddening endless circle?
 
Are you sure the ability to configure the tplink device from wireless is enabled by default. Many device can only be configured via ethernet the first time. It tends to be tricky on ethernet also because as soon as you change it you loose connection until you change the ip on your pc to the other range. It almost appears as if the router crashed. Some routers you can not set a static ip on the PC you have to use dhcp the first time.

Because DHCP is enabled by default you almost always must use a dedicated pc plugged into the router to configure it. If you plug it into your main network even for a short time to configure it can cause issues.
 
Thanks for your responses. While at work (I couldn't get this router off my mind), and so before I had a chance to see your responses, I had decided to try something different. I have a Windows 8.1 Pro tablet which I have not made a member of the domain. It is almost always used away from home, so domain join was not necessary. It's so much a "regular" Windows PC, only squeezed into a very thin box, that I'd almost forgotten it wasn't a domain member like the rest of my Windows devices. As a result, it takes whatever address is provided to it by the access point in question.

So, I disconnected my old router, and connected my new one. This time I only connected the cable modem, and did not connect the new router to the switch that concentrates all of my Ethernet connections. I was then able to log into the management web app on the router. First, I tried to make all the customizations I wanted, and the router stopped responding on either the new IP or the old one. So I reset the router to factory defaults and this time only changed the IP address for the router from 192.168.0.1 to 192.168.1.1, and restarted the router. Once I could reach it from my tablet, I then turned off DHCP on the router, and as it was restarting in response to that, I connected the cable from my switch to the first LAN port. I was then able to see the router from all of my wired devices, and have now completed customization.

Strangely, the cable modem received a new/different WAN IP with this router than with the previous one. I'd been receiving the same IP for a very long time. Go figure . . . as long as it works.

Now I need to start to watch for questions from others to pay it forward!

Thanks again for taking the time to respond!