Accessing WG302 via http since the year changed?

This issue is indeed coming from the Netgear WAP WG302. I have several PCs in my house (IT Director at work and a bit of a geek ). I need to configure and make changes now and again. Is there another way to get this updated/fixed? I need to get that certificate renewed or at least a way to access it via console cable or browser.:(

wlan-ap>set system dns primary 0.0.0.0
system dns primary : 10.1.4.2
wlan-ap>set system dns secondary 0.0.0.0
system dns secondary : 0.0.0.0

I downloaded putty and tried those commands, it looks like it wont allow the primary dns to change. Any ideas?

I also have a WG302 V1 that is now shelfed. Weird thing is, my 302 never had the right time in all the times I have logged into it. I tried a lot to get it to obtain the correct time for log purposes, but it never did. Looks like I'll be going to get a Ver2 possibly. Quick question, anyone that has a Version 2, does it say on the outside of the box so I don't have to play the guessing game or buy and return game. Or will they all be Version 2s on the shelf?

Travb81 wrote:
wlan-ap>set system dns primary 0.0.0.0 system dns primary : 10.1.4.2 wlan-ap>set system dns secondary 0.0.0.0 system dns secondary : 0.0.0.0 I downloaded putty and tried those commands, it looks like it wont allow the primary dns to change. Any ideas?

Can anyone offer advice to this?
I dont have a null modem cable, next step if a factory reset

Hope there is some resolution for this issue - I have about 4 of these units around the plant and cannot access them. Thankfully, they are still functioning, but I can't get into them to modify configuration.

Travb81 wrote:
wlan-ap>set system dns primary 0.0.0.0 system dns primary : 10.1.4.2 wlan-ap>set system dns secondary 0.0.0.0 system dns secondary : 0.0.0.0 I downloaded putty and tried those commands, it looks like it wont allow the primary dns to change. Any ideas?

Try using an unallocated IP address from the same subnet. My WG302v1 accepted the changed and now works again.
eg. system dns primary : 10.1.4.99 (where no DNS exists)

tried using an invalid IP address for my DNS on one of my WG302s and it worked.
Thanks for the tip.

Hello,
Same problem in France with our WG302 AP.
After reading all your messages, we used with success the software Putty to be connected to the AP by SSH.
After connection, introduction of the 2 lines to configure the DNS with 0.0.0.0 and reboot, the connection to the AP via IE go well.
All is OK without obligation to be connected with a cable.
Have a nice day
Regards
(excuse for my english)

Unsure if Netgear will even flinch at this but they'll loose my future business if they don't provide a more suitable solution:

I have a Netgear WAG302 Wireless Router. Starting on the year of 2011, the WAP GUI accessed via http no longer allows me to login. When I type my password I get the error: Invalid Login!
Login Again. I can login to the router using SSH with the same password that fails using the web browser GUI. This thread here indicates WG302 and WAG302 v1 are affected as a result of expired certificates. http://forum1.netgear.com/showthread.php?t=60190&page=5

I also read the WAG302 V2 certificate will expire 10/15/2012 at 3:25:58pm with 5.2.3na firmware. I understand Netgear will fix that in firmware but not for WAG302 v1 as it is at end of line. This unethical, we have a few WAG302 V1 throughout our company and because of a coding oversight, as per that article we are forced to disable NTP and point to invalid DNS to prevent the WAP from updating its time/date. This option Netgear is suggesting defeats the purpose of logging in the WAG302 V1 and renders the logs useless as the time stamps are invalid.

I sure hope Netgear retracts from their course of action to not release new firmware for WAG302 V1 as well as include in the new firmware the option to update the certificate with a self signed or CA assigned cert or code the firmware to not blow up when a certificate expires.

I doubt Netgear will even flinch at this but they'll sure loose my future business if they don't retract their course of action:

I have a Netgear WAG302 Wireless Router. Starting on the year of 2011, the WAP GUI accessed via http no longer allows me to login. When I type my password I get the error: Invalid Login!
Login Again. I can login to the router using SSH with the same password that fails using the web browser GUI. This thread here indicates WG302 and WAG302 v1 are affected as a result of expired certificates. http://forum1.netgear.com/showthread.php?t=60190&page=5

I also read the WAG302 V2 certificate will expire 10/15/2012 at 3:25:58pm with 5.2.3na firmware. I understand Netgear will fix that in firmware but not for WAG302 v1 as it is at end of life. This unethical, we have a few WAG302 V1 throughout our company and because of a coding oversight, as per that article we are forced to disable NTP and point to invalid DNS to prevent the WAP from updating its time/date. This option Netgear is suggesting defeats the purpose of logging in the WAG302 V1 and renders the logs useless as the time stamps are invalid.

I sure hope Netgear retracts from their course of action to not release new firmware for WAG302 V1 as well as include in the new firmware the option to update the certificate with a self signed or CA assigned cert or code the firmware to not blow up when a certificate expires.