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.
Oh, sarcasm, always great to read. Especially at 11pm. Thank you.
Ok, I've pasted the actual results, below, for the avoidance of doubt. NB no LED indicators change state, of course. Sadly none of these responses give me the option to ignore the warning and proceed with a connection. Happily, the LAN in question is not open to external connections and I do not therefore believe myself to be in trouble, other than the distressing problem I find myself facing in that I am unable to change the SSID of the device in question.
My layman's conclusion, having Googled the issue before posting here, is that some things called SSL or TLS security settings used by the WAG102 are not compatible with those used in modern browsers, which consequently choose the safe option and refuse to connect. My feeble attempts at changing the browser configurations as suggested in some forums has not resolved the problem.
On attempting to connect via Microsoft Edge or IE11:
Can’t connect securely to this page
This might be because the site uses outdated or unsafe TLS security settings. If this keeps happening, try contacting the website’s owner.
On attempting to connect via Google Chrome:
This site can’t provide a secure connection
192.168.0.3 uses an unsupported protocol.
ERR_SSL_VERSION_OR_CIPHER_MISMATCH
The client and server don't support a common SSL protocol version or cipher suite.
On attempting to connect via Mozilla Firefox:
Secure Connection Failed
An error occurred during a connection to 192.168.0.3. Cannot communicate securely with peer: no common encryption algorithm(s). Error code: SSL_ERROR_NO_CYPHER_OVERLAP
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.
> Oh, sarcasm, always great to read. Especially at 11pm. [...]
Sorry. Couldn't divine your time zone, either.
> Ok, I've pasted the actual results, below, [...]
The URL which produced these results remains a mystery.
> Can't connect securely to this page
If you were using "https://", then you might try plain-old "http://".
Knowing nothing, I'd guess that that might get you to the warning which
I had guessed that you had gotten.
> [...] showing actual actions with their actual results (error
> messages, LED indicators, ...) can be more helpful than vague
> descriptions or interpretations.
Still true. _Both_ parts, actions and results.
- 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. Attempts to specify http: failed, as this was replaced with https: as soon as I hit ENTER.
Well, thanks anyway. I guess there are no more gems of inspiration or sarcastic observations forthcoming so I'll give up with this and purchase a new access point which I will be able to configure. Was a real pleasure dealing with you. Oh look, I can do sarcasm too!
> [...] 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, ...
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
