Unable to reach 192.168.1.1 and 192.168.0.1
Unable to reach 192.168.1.1 and 192.168.0.1
Hello, today my ISP changed my router and I wanted to go into it's settings to port forward. However I could not open neither 192.168.1.1 or 192.168.0.1. I tried both wireless and LAN but to no avail. Not even on the router there is URL to go into to set up the router. The router model is Smartcom DE GB. Here is a picture of ipconfig:
Check your network configuration and consider turning off IPv6 on your adapters, as it may lead to issues. Determine the router model using its IP address—your screenshot confirms it’s 192.168.1.1. Have you tested the alternative IP 192.168.1.1:8080?
Do you currently possess a stable internet link? Is your system deliberately assigning a static IP address and gateway within the Windows network configuration?
Open command prompt, type ping 192.168.1.1, check response time. Make sure it works for better accuracy.
Running a 192.168.X.X network places you in a Class C range. With a subnet mask of 255.255.255.0, your possible addresses span from 192.168.0.1 to 192.168.0.254. If your device is at 192.168.1.5, it won’t connect to the 0.1–0.254 range. Check if your router uses 192.168.0.1 and adjust accordingly. For DHCP users, release and renew addresses with the commands provided. View detailed info via ipconfig /all or update adapter settings in Network and Sharing Center.
Adjust your IP address manually through the adapter settings. Look for Ethernet in the Windows Start menu and follow the instructions provided.
The issue lies in the fact that OP appears to be already within the right subnet. Their IP is .1.5 and the gateway is .1.1. It's more likely OP manually set the .1.x subnet for their old router, while the new one uses .0.x. This should be clear since Windows would notice the lack of internet access. The best approach would be to enable Automatic Assignment and let Windows detect the gateway via DHCP. Then they can later adjust static IPs as needed.
I believe everyone is adding unnecessary details before we gather all the facts. I’ll assume the most basic and probable situation for the person asking this. The original device likely used an IP like 192.168.0.1, which has been removed and replaced by a newer router with IP 192.168.1.1. The machine now has a fresh IP from DHCP, and it’s assigned 192.168.1.5. The user attempted to reach 192.168.0.1 but that failed, while trying 192.168.1.1 worked but didn’t.
Routers can be set to ignore that IP address, like when your ISP assigns a non-default port instead of the usual 80. Often, the password isn’t known either, so you might need to contact your provider to find the correct port and login details.