Forum Discussion
Cannot access my Gateway at 192.168.12.1
Using my VAIO SX14 Windows 10 Pro Laptop: I cannot access my Gateway at 192.168.12.1. Network trouble shooting says "You computer appears to be correctly configured, but the device or resource (192....
After a lot of investigation, I uninstalled the VPN and I can now access my gateway 192.168.12.xx
iTinkeralot wrote:
My guess is that he plugged a router into the T-Mobile router, as you speculated, and it served the 192.168.12.1 DNS server up on its ethernet segment as the DNS server. No way clients on the second broadcast domain can ever be routed out and back as the T-Mobile router will never know of the ethernet segment on the other side of the other router. In effect he needs to turn that to bridge mode and disable the DHCP server or just shut the old router down. Unless there is a demand for expansion of the wireless to try to cover more area the best solution is to just go with the T-Mobile router. The second router would have the double NAT solution and well that could cause issues as well.
My TMHI Gateway is the router, it is an integral part of a single “box”
I would rule out the Windows Firewall first thing. If you disable the firewall, as a test, then you can see if it is blocking the connection to the gateway. I suggest using "Control Panel" to deal with the firewall. Press the Windows start key, type control panel and then select the firewall. I use Bitdefender's security suite so I avoid the W10 firewall myself. If you have at one point or another in time changed FW settings on the laptop restore the defaults and see if that helps.
If you temporarily disable the firewall to test; open a command window and ping 192.168.12.1 with a continuous ping. i.e. [ping -t 192.168.12.1] If the GW responds enable the FW again. If the ping continues then try to web into the router from the client. Another test is to ping the subnet broadcast address, 192.168.12.255 and then look at the ARP table. Issue the command arp -a and see what the client has learned of the other clients on the network. Determine for sure the IPv4 and IPv6 status of the client with the command ipconfig /all. I run a dual stack IPv4 & IPv6 and I have no issues with the Nokia gateway on MAC OS, Linux or Windows 10 Pro so I suggest to run both in the IP stack. Compare the settings for a working client to the laptop client. See if there are different settings.
If you can't ping the router with the FW up or down this is a curious issue.
