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
Can you ping the 192.168.1.1?
murchman - Yes, I can ping 192.168.1.1 without any problems, with a fast response time of < 1 msec.
DarrenM - Unfortunately, I can't get the network map to appear. The network map did work with my previous R6300v2.
Now ... Just to add more confusion to the mix ... I also have a Win10 and an Ubuntu Virtual Machine installed on my PC. I could ping 192.168.1.1 inside both VMs, so I decided I would try to use the browsers within those VMs to try to get to 192.168.1.1. Couldn't get any cleaner than that - I never tried to get to my previous routers in a VM before, so there wouldn't be any browser-related issues involved.
Again, I see the "Connection was reset" error in both VMs. :mansad:
Something is very wrong at a very low level here. Is there anything useful I can provide with a Wireshark log?
and seeing no one else is having the same issue it just about removes the orbi from the equation , the only explanation is you have an ip conflict
factory reset everything and start again
what is the orbi connected to on the upstream side ? as it may be causing the ip conflict
