NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
How to access web interface on WAG102 with a modern browser
I am unable to open the web interface on our WAG102 access point. I've tried Microsoft Edge, IE11, Chrome and FIrefox. All report similar errors, associated with SSL/TLS. Is there any way that I can ...
I needed to reset some things on several WAG102s we have. The answer was to download and install Virtualbox (you could use another if you wanted) then go to
https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/
and download a virtual machine with IE8.
It was fairly easy to get running and easily connects to the WAG102 interface.
> [...] I guess there are no more gems of inspiration or sarcastic
> observations forthcoming [...]
I'm very sorry if the response time here did not meet your
expectations. Perhaps you should demand to cancel your support contract
and receive a full refund.
> Re URL, I simply entered the IP address of the device. 192.168.0.3.
> All browsers that I tried then insist on inserting https:\\ in front.
I'm willing to believe that if you actually did specify a URL with
backslashes, then your "modern browsers" would correct them to forward
slashes, but what evidence have you that "192.168.0.3" is the WAG102?
As I read the (decade-old) Reference Manual for this thing, the default
LAN IP address for it is "192.168.0.232". In fact, that manual
explicitly suggests the URL (with forward slashes),
"http://192.168.0.232". Presumably, this address could have been
changed, but, unless the current firmware differs greatly from that
described in the (old) manual, I would not expect the WAG102 to redirect
an "http://" URL to an "https://" URL (because it would be too stupid to
deal with an "https://" URL).
If you don't already have it, then visit http://netgear.com/support ,
put in your model number, and look for Documentation. Get the Reference
Manual. Read, as necessary.
> [...] Oh look, I can do sarcasm too!
If only you could also follow directions, ...
I'm tickled by the way you insist on skirting around the actual problem by trying to second guess. We've now replaced the WAG102 with another device and all's well, so no longer require assistance with the connection problem. I would be grateful therefore, in order to avoid raising my blood pressure further when I read another of your obnoxious messages, that you stand down on this one. There will be plenty of others keen to hear from you, I'm sure. To clarify for you before I go, the IP address of the unit was 192.168.0.3, already confirmed a) by checking our own documentation from when the thing was installed, b) performing a LAN scan to identify the MAC address and manufacturer of the device (happily we have (had) no other Netgear products on the network) and c) by switching it off and performing another LAN scan to confirm that it had disappeared. We do of course already have the manual, given that we have the device. We also know that it was originally possible to connect to it by entering the URL in exactly the way in which we have been trying recently. The device didn't change; the browser software we are using has undergone several changes. Hence my conclusion that the enhanced security in yes, modern browsers, was causing the problem. That will have to remain only a theory as the WAG102 is now in the bin. Well done in pointing out that I'd used the wrong slash character in my earlier message though. Impressive.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
