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.
> [...] All report similar errors, [...]
And, with my weak psychic powers, I can't see any of them. As usual,
showing actual actions with their actual results (error messages, LED
indicators, ...) can be more helpful than vague descriptions or
interpretations.
If all you're seeing is a complaint about sending some user
credentials over an unencrypted/insecure link ("http://" instead of
"https://"), then the easy thing to do is ignore the warning, and
proceed. Presumably, you're talking to your own gizmo on your own LAN.
If someone can overlisten to that traffic, then you're already in big
trouble.
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 connection192.168.0.3 uses an unsupported protocol.
ERR_SSL_VERSION_OR_CIPHER_MISMATCHThe 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.
Hi Antinode
Just reading through this discussion thread and I'm really suprised that this problem has not been raised by more Netgear customers.
I have exactly the same problem..
I've had the same Netgear WG102 Access Point for many years now, but when I try to connect to it using the new MS Edge browser I receive the following message.
"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"
As background. I use the same instructions from the Neatgear Support page to access my WG102 each time.
1) Connect to WG102 via a Ethernet cable, 2) Change Ethernet IP4v to address specificed, 3) Type in the default Netgear IP address for the WG102 as instructed.
Always worked in the past but now I receive the error above and cannot proceed any further.
The only time that has changed is that I have Win 10 installed and attempting to use Edge (although I've tried IE.11)
Can anyone assit
> Just reading through this discussion thread and I'm really suprised
> that this problem has not been raised by more Netgear customers.
There may be others, but they may have found a more appropriate forum
than this one. My quick Google search for:
site:community.netgear.com wag102
found, for example:
https://community.netgear.com/t5/x/x/td-p/1044681
If firmware newer than the Reference Manual really does force
"https", but the gizmo's web server configuration is so old/lame that
modern browsers won't tolerate its obsolete security scheme, then your
only hope might be to use an older browser. Or its equivalent, if your
current browser allows it, by establishing an exception (site-specific)
to its normal security requirements.
Wow!!!!! What a sarcastic unhelpful response! I have the same problem and reading this, your further responses illustrate that me a capabactevh guy but have zero social skills
kiwiw wrote:
I am very surprised by the tone of the Netgear's responses (very rude, and more importantly, unhelpfull), if I have to replace I definitely won't be choosing Netgear next time...
Can't find a single official Netgear post in this thread.
Oharvey wrote:
Wow!!!!! What a sarcastic unhelpful response! I have the same problem and reading this, your further responses illustrate that me a capabactevh guy but have zero social skills
We're community members here, you don't talk to Netgear here.
If your well-aged WAG102 - you are looking to support an embedded device launched into the market in Q4 2002, so almost 16 years ago - does still allow plain http access this should remain workable. If the firmware set to redirect hard to https (this was asked above by a community member and nobody gave the other community members [which most don't have such legacy devices still in service or at hand] nobody answered) you are most likely out of luck if you don't have a legacy system/OS/browser at hand..If it's a software setting a factory reset (button) might allow plain http access - how shall we know? But it appears none of the WAG102 owners is able to reply in a kind of community-social way. Seriously, you should consider to phase-out these legacy devices anyway - I doubt Netgear does still maintain these device firmware, so an update to support current https variants is more than unlikely.
- Yeah I realize it's legacy product but as they say"if it ain't broke don't fix it" ! The response by the 'community' member doesn't exactly help build a community if the response to a perfectly reasonable question is met with sarcastic snooty responses. As for the wg102 - can you recommend a similar AP with the same robust build quality. I just use for on the fly AP for staff on site without spending ££££.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
