× NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Reply

How to access web interface on WAG102 with a modern browser

Glenikins
Aspirant

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 still access the device, or do I need to scrap it?!

Model: WAG102|ProSafe Dual Band Access Point
Message 1 of 23

Accepted Solutions
dixielibrary
Aspirant

Re: How to access web interface on WAG102 with a modern browser

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.

 

View solution in original post

Message 22 of 23

All Replies
antinode
Guru

Re: How to access web interface on WAG102 with a modern browser

> [...] 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.

Message 2 of 23
Glenikins
Aspirant

Re: How to access web interface on WAG102 with a modern browser

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.

Message 3 of 23
antinode
Guru

Re: How to access web interface on WAG102 with a modern browser

> 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.

Message 4 of 23
Glenikins
Aspirant

Re: How to access web interface on WAG102 with a modern browser

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.
Message 5 of 23
Glenikins
Aspirant

Re: How to access web interface on WAG102 with a modern browser

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!

Message 6 of 23
antinode
Guru

Re: How to access web interface on WAG102 with a modern browser

> [...] 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, ...

Message 7 of 23
Glenikins
Aspirant

Re: How to access web interface on WAG102 with a modern browser

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.
Message 8 of 23
Ian_Bertram
Aspirant

Re: How to access web interface on WAG102 with a modern browser

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

 

Message 9 of 23
antinode
Guru

Re: How to access web interface on WAG102 with a modern browser

> 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.

Message 10 of 23
kiwiw
Aspirant

Re: How to access web interface on WAG102 with a modern browser

Hello

 

I have the exact same issues, but I unfortunately have 2 of these (WG102) access points. I have read through all the above posts and I have exactly the same issues and have tried the same methods. 

 

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...

 

The linked post mentioned it was solved by using IE, this does not work, it gives the same error message as does Edge.

 

Hopefully someone at Netgear can be polite and helpfull on how to log in to their products.

 

Can you please help

 

Regards

Warwick

Message 11 of 23
Ian_Bertram
Aspirant

Re: How to access web interface on WAG102 with a modern browser

Hi Warick

 

Like yourself i became very frustrated.  

 

I determined that the problem is that the older Access Points cannot be accessed via any of the newer browsers. IE or Chrome.

 

In my case i was extremely lukcy.

 

I found the oringal laptop that it used to setup the access point those may years ago.

 

It still runs Windows NT with an early version of IE.

 

Started it up and all worked fine.

 

I do work in IT and my tech team told me of the many advantages of throwing the old access points out and getting newer faster units. This is probably your only option..   Else NT rules

 

 

Message 12 of 23
Jmamma2018
Aspirant

Re: How to access web interface on WAG102 with a modern browser

We just experienced the same issue, and none of the snarky answers helped. However we were able to access the device using IE11 on a Windows 7 Machine by checking the Use SSL 2.0 and Use SSL 3.0 boxes in the IE - Internet options - Advanced - Security section. They are probably unchecked for a reason though, so uncheck when finished.

Message 13 of 23
Oharvey
Aspirant

Re: How to access web interface on WAG102 with a modern browser

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 

Model: WAB102|802.11a+b Dual Band Wireless Access Point
Message 14 of 23
schumaku
Guru

Re: How to access web interface on WAG102 with a modern browser

@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.

Message 15 of 23
Oharvey
Aspirant

Re: How to access web interface on WAG102 with a modern browser

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 ££££.
Message 16 of 23
schumaku
Guru

Re: How to access web interface on WAG102 with a modern browser

Almost any - except if "robust" does translate to a heavy duty metal enclosure. The WAC505 is very affordable, 2x2 802.11ac Wave II, for example, without breaking the bank - it starts from about 75 USD for PoE or 85 USD with an external power supply - pricing varies depending on your market/region.

 

Still - considering it's secure enough otherwise (probably no WPA2 AES, vulnerable e.g. to KRACK, ...) - can't your legacy device not be accessed and managed by http anymore?

Message 17 of 23
Oharvey
Aspirant

Re: How to access web interface on WAG102 with a modern browser

Yes - I did mean t
Robust by the fact they are in metal enclosures.

I have been using these for 10 years + / can be picked up for £15 . Frustrates now by inability to access by http / disable Https.

I live/work on a large farm so no real danger of security issues.

I have recently deployed down ubiquiti units but the range is pretty poor compared with these old units

Thanks again
Message 18 of 23
Oharvey
Aspirant

Re: How to access web interface on WAG102 with a modern browser

P.s can't seem to disable auto Https on any of the browsers I have . I can reset the unit but can't access admin panel for setup
Any hints would be appreciated
Message 19 of 23
schumaku
Guru

Re: How to access web interface on WAG102 with a modern browser


@Oharvey wrote:
P.s can't seem to disable auto Https on any of the browsers I have . 

Modern browsers don't have sich a thing - either you have some special settings, some add-ons, or some caching entry doing a redirect ... when using http://192.168.12.34/ or whatever local domain name like http://wirelessap.office.domain.local/ a http connection must be established. Only very few specific domains where some browsers init a dedicated process towards https - but not for ie. an IP address or a generic domain name.

Still, I have no idea what really happens - might be some smart guys have introduced a forced redirect on the port 80 to https on 443. Drop the browser cache, and try...

Message 20 of 23
smhawk
Aspirant

Re: How to access web interface on WAG102 with a modern browser

Seems very strange that this method would only work on a windows 7 machine, but I did what you did IE11 modified SSL options - I can ping my wg102 default 192.168.0.229 but I still can't hit it via browser.(on windows 10) I'm going to try on a windows 7 machine if that is the only issue I am going to be pretty puzzled. 

Message 21 of 23
dixielibrary
Aspirant

Re: How to access web interface on WAG102 with a modern browser

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.

 

Message 22 of 23
Zirax
Aspirant

Re: How to access web interface on WAG102 with a modern browser

Adding to this conversation very late but from my research edge, chrome and firefox cannot access the config page. I have tried to disable everything about the https check but the actual issue is that there is literally no certificate (tested using openssl on opensuse leap). This means that no browser will allow you to access it, the security check fails before everything that you can choose to ignore. All of this despite the access point itself redirecting to https, not the browser. Ironic to me that this was marketed as a professional product, thank you for the solution.
Message 23 of 23
Discussion stats
  • 22 replies
  • 22169 views
  • 0 kudos
  • 10 in conversation
Announcements