NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Can't connect to new Orbi at 192.168.1.1 on my PC
Hi - I am having huge issues connecting to my new Orbi Configuration at http://192.168.1.1 on my main PC. I am running Win7x64 SP1. My main PC is connected to one of the Orbi Router's Ethernet ports....
SOLUTION FOUND: I have Kaspersky Anti-Virus 2017 installed. This was the root of the problem.
I had previously tried disabling KAV2017 and exiting KAV2017 as part of my debugging effort. However, access to 192.168.1.1 was still blocked even when I had terminated KAV2017. So for a while, I thought KAV wasn't the problem. The clue I found just a few minutes ago was that I noticed that the "Can't access this page" browser error message changed slightly depending on whether KAV2017 was disabled (paused) or whether it was terminated. When KAV2017 was terminated, there was additional information available in the browser error message that pointed to KAV as the culprit.
When I temporarily uninstalled KAV2017, I was able to get to 192.168.1.1 again. Whew!I find it interesting that KAV2017's "protection" (if you want to call it that) was so thorough and at such a low level, that it prevented access to 192.168.1.1 even inside Virtual Machines that didn't have any Anti-Virus software installed at all. It's actually pretty impressive how comprehensive Kaspersky's protection is, except that it was undesired operation for me (and probably a lot of other folks).
When I added http://192.168.1.1 and https://192.168.1.1 to the KAV2017 Web Anti-Virus URL Advisor Exclusion List, I can get to 192.168.1.1 fine now on my main PC.
Cheers!AzJazz
peteytesting - AniDutta mentioned that they are having the exact same issue (also unresolved), so it isn't entirely an isolated case to just my setup. The Orbi Router is connected directly to my cable modem. My main PC is connected to one of the (3) available Orbi Router Ethernet ports. I have a QNAP NAS connected to one of the other Ethernet ports. After that, I have a 8-port Gigabit switch connected to the third Orbi Router Ethernet port to break out more available wired connections. Since the Orbi Router is the only DHCP server on my LAN that I know of, I am not sure at this point where there could be another 192.168.1.1 IP address conflict coming from. I have already tried a couple of factory resets on this Orbi and another Orbi Router, and it didn't help in the past. I can get to the Orbi configuration via another PC, so I don't know if another factory reset will help.
MarkC1024 - I checked my Windows hosts file, and there aren't any 192.168.1.1 entries. An ipconfig/all shows the LAN gateway at 192.168.1.1.
It would seem that if you can get to the config page from another PC, the router is operating properly. So must be something about the path of the PC having problems. Have you tried disconnecteing your NAS and other switches to test? I'd take an approach of breaking things down to a simple config and then add things back in as testing succeeds. Just need to isolate what is introducing the problem.
I would try configuring the Orbi to user another subnet or IP range and see if the problem continues. Switch it to 192.168.2.x or use the 10.x.x.x range.
Hi, murchman
Soooo ... I tried reconfiguring my Orbi Router to 192.168.2.1 (Something I had also planned as a last-ditch response)
I was able to get to the Orbi Router configuration page again on my main PC since it wasn't at 192.168.1.1 anymore.
After a bit of work, my home's LAN was eventually reconfigured and most (but not all) of my network stuff was working again.
However ... Netgear thinks I must be absolutely crazy to set my Orbi Router to 192.168.2.1. When I rebooted my Orbi Router I couldn't get to the internet anymore - I couldn't understand why.I tried opening my browser to 192.168.2.1, and I saw a Netgear message pop-up that told me that my Orbi Router's base IP address was automatically reset back to 192.168.1.1 for my protection (With no option to prevent the reassignment).
:manfrustrated: :manfrustrated: :manfrustrated: :manfrustrated: :manfrustrated: :manfrustrated: :manfrustrated: :manfrustrated: :manfrustrated: :manfrustrated:SOLUTION FOUND: I have Kaspersky Anti-Virus 2017 installed. This was the root of the problem.
I had previously tried disabling KAV2017 and exiting KAV2017 as part of my debugging effort. However, access to 192.168.1.1 was still blocked even when I had terminated KAV2017. So for a while, I thought KAV wasn't the problem. The clue I found just a few minutes ago was that I noticed that the "Can't access this page" browser error message changed slightly depending on whether KAV2017 was disabled (paused) or whether it was terminated. When KAV2017 was terminated, there was additional information available in the browser error message that pointed to KAV as the culprit.
When I temporarily uninstalled KAV2017, I was able to get to 192.168.1.1 again. Whew!I find it interesting that KAV2017's "protection" (if you want to call it that) was so thorough and at such a low level, that it prevented access to 192.168.1.1 even inside Virtual Machines that didn't have any Anti-Virus software installed at all. It's actually pretty impressive how comprehensive Kaspersky's protection is, except that it was undesired operation for me (and probably a lot of other folks).
When I added http://192.168.1.1 and https://192.168.1.1 to the KAV2017 Web Anti-Virus URL Advisor Exclusion List, I can get to 192.168.1.1 fine now on my main PC.
Cheers!AzJazz
