This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
I just took a new WAC720 out of the box, plugged it in, and tried to access the management interface. Chrome says: "This site can’t be reached. The webpage at https://192.168.7.30/ might be temporarily down or it may have moved permanently to a new web address. ERR_SSL_BAD_RECORD_MAC_ALERT." IE gives a similar error. The network has a DHCP server which assigned the IP to the AP. A port scan shows the AP on that IP and that it has HTTPS open. I can connect to the AP's Wi-Fi, but still get the same error when trying to connect to the web console.
I finally got into it. I got a laptop and connected it directly to the AP with cat5 & set the laptop's IP to be on 192.168.0.x. Then the web portal loaded without problems. The AP had the 3.1.1.0 firmware. I updated the firmware to the newest, configured it with static IPs, and it seems to be working fine now.
Only 2 complaints:
1) You have to be the same subnet to access the management interface. I have it in 192.168.9.x & would like to be able to manage it from 192.168.7.x.
2) The NTP client doesn't like using Windows Servers as time sources; the date changed to something in May & when I use the default netgear NTP it doesn't recognize daylight savings time.
IE 11.589.10586.0 Update Versions 11.0.35 - I get the "There is a problem with this website's security certificate" page, I click to continue to the website, then get "This page can't be displayed".
Firefox 33.1.1 - error: "Unable to connect - Firefox can't establish a connection to the server."
I am able to connect and login using putty & SSH, but I don't know how to do anything with it through the CLI.
I finally got into it. I got a laptop and connected it directly to the AP with cat5 & set the laptop's IP to be on 192.168.0.x. Then the web portal loaded without problems. The AP had the 3.1.1.0 firmware. I updated the firmware to the newest, configured it with static IPs, and it seems to be working fine now.
Only 2 complaints:
1) You have to be the same subnet to access the management interface. I have it in 192.168.9.x & would like to be able to manage it from 192.168.7.x.
2) The NTP client doesn't like using Windows Servers as time sources; the date changed to something in May & when I use the default netgear NTP it doesn't recognize daylight savings time.
Kaspersky Endpoint Security was blocking the web interface for some reason. When I added the WAP's IP to KES's trusted list, it loaded fine from different subnets.
The time seems to be updating correctly from the Windows Server also now. Not sure what changed there, but it's working.
We are glad to know that the issues were resolved. We encourage you to mark the appropriate reply as the “Accepted Solution” so others can be confident in benefiting from the solution. The Netgear community looks forward to hearing from you and being a helpful resource in the future!
