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

Forum Discussion

txnintn's avatar
txnintn
Aspirant
Apr 12, 2021
Solved

WNR2000v5 shows the Current Time: Wednesday, Dec 31, 1969 16:06:18 above log window.

Firmware version updated from v1.0.0.72 to v1.0.0.76 no change.

Check out the current time above the log window.

Anyway to check the router real time / date?

txnintn

 

 

 

  • Ok fixed it.  I went to Security Schedule, Time zone was Pacific, I corrected it, then checked automatically adjust for daylight savings time and appied.  Now the time and date over the log is correct.  Weird bug.

3 Replies

  • > Operating Mode: Access Point

     

       How, exactly, is the WNR2000v5-as-WAP connected to the main-router
    LAN?  (Hint: If a device has different types of Ethernet ports, then
    "connected to device" is not enough detail.)

     

       Visit http://netgear.com/support , put in your model number, and look
    for Documentation.  Get the User Manual (at least).  Read.  Look for
    "Use the Router as a Wireless Access Point".  How closely does your
    configuration agree with the documented configuration?

    • txnintn's avatar
      txnintn
      Aspirant

      My main wireless router is a NetGear WNDR4500v2, it shows the correct time and date in the log files.  The only LAN cable plugged into the WNDR4500v3 goes to the WNR2000v5's yellow port labeled internet.  I have two desktops plugged into the WNR2000v5's LAN ports.

       

      AP is manually configured  simular to the article How do I change my NETGEAR router to AP mode after setting it up? 

       

      The WNDR4500v2 is DHCP 192.168.x.1) and the WNR2000v5 is on the same subnet, DCHP off and ip is 192.168.x.250.

      Txnintn

      • txnintn's avatar
        txnintn
        Aspirant

        Ok fixed it.  I went to Security Schedule, Time zone was Pacific, I corrected it, then checked automatically adjust for daylight savings time and appied.  Now the time and date over the log is correct.  Weird bug.