• October 14, 2019, 03:44:03 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: Year 2012 Date Bug Advisery  (Read 8674 times)

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 47834
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Logged
Cable:200mb/10Mb>NetGear C7800>DIR-882>DGS-1100>HP 24pt Gb Switch. COVR-3902/2202/1203,DIR-2680,890L,882,880L,868L,DNR-202L,DNS-345x2,DCS-933L,936L and 960L.
Go Here>Router Troubleshooting

bryboob

  • Level 1 Member
  • *
  • Posts: 21
Re: Year 2012 Date Bug Advisery
« Reply #1 on: April 10, 2013, 06:25:34 PM »

hi, i have a dir-632 with the same problem, date only go's
upto 2012 is there a fix for it?
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 47834
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Year 2012 Date Bug Advisery
« Reply #2 on: April 11, 2013, 06:44:43 AM »

You can attempt to update to v1.03NA and see if this fixes it.
Have you tried using the NTP services options under Tools/Time?

If you decide to update FW, please follow this guide:
FW Update Process
Logged
Cable:200mb/10Mb>NetGear C7800>DIR-882>DGS-1100>HP 24pt Gb Switch. COVR-3902/2202/1203,DIR-2680,890L,882,880L,868L,DNR-202L,DNS-345x2,DCS-933L,936L and 960L.
Go Here>Router Troubleshooting

BarretFox

  • Level 1 Member
  • *
  • Posts: 1
Re: Year 2012 Date Bug Advisery
« Reply #3 on: April 13, 2013, 11:17:21 PM »

I have a DIR-615 REV-C.  Same 2012 date ceiling, I've updated the firmware and set the date to be automatically configured via NTP,  which seems to have gotten around the date ceiling. 

Hope this helps someone!

-Barret
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 47834
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Year 2012 Date Bug Advisery
« Reply #4 on: April 14, 2013, 10:24:51 AM »

Glad NTP is working for you. Thanks for sharing.

Enjoy.

I have a DIR-615 REV-C.  Same 2012 date ceiling, I've updated the firmware and set the date to be automatically configured via NTP,  which seems to have gotten around the date ceiling. 

Hope this helps someone!

-Barret
Logged
Cable:200mb/10Mb>NetGear C7800>DIR-882>DGS-1100>HP 24pt Gb Switch. COVR-3902/2202/1203,DIR-2680,890L,882,880L,868L,DNR-202L,DNS-345x2,DCS-933L,936L and 960L.
Go Here>Router Troubleshooting

SuperPuppy

  • Level 1 Member
  • *
  • Posts: 2
Re: Year 2012 Date Bug Advisery
« Reply #5 on: May 19, 2013, 05:25:41 PM »

OK, I feel super smart here.
I bought five DIR-615 over the past few years to use as access points on several networks at the vacation homes I rent out

My tenants have been complaining that the WiFi internet access from these Access Points have been unreliable since the beginning of the year.

My tenants have been able to reconnect by unplugging and replugging in the DIR-615 which works for a short time until it fails again.
I can only explain that all five of the same DIR-615 Access Points that are configured the exact same way, suddenly failing in the exact same manner after New Years has to do with the 2013 date bug.

I cannot connect these DIR-615 as an Internet Gateway, which might be the reason why the NTP Server does not work.  My internet provider forces me to use their proprietary gateways.
The DIR-615s all have the same firmware (Hardware Version: E3,   Firmware Version: 5.10) and updating the same latest firmware doesn't help.

The only way I can make the DIR-615 show the year 2013 is by changing the date to 12/31/2012 11:59:50, and letting it roll over to the next year, but I can't fix the rest of the date without screwing up the year again.

You have known about this issue at least since January, it is now the middle of May, when will you have this fixed?

Does anyone want to buy five slightly used DIR-615s?
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 47834
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Year 2012 Date Bug Advisery
« Reply #6 on: May 19, 2013, 05:41:15 PM »

Since you are not using them as main host routers, then try this instead:
Turning a router into an AP.

the time isn't really needed as these routers work with or with out the time. Could be other problems causing wireless issues.
« Last Edit: December 25, 2014, 03:32:07 PM by FurryNutz »
Logged
Cable:200mb/10Mb>NetGear C7800>DIR-882>DGS-1100>HP 24pt Gb Switch. COVR-3902/2202/1203,DIR-2680,890L,882,880L,868L,DNR-202L,DNS-345x2,DCS-933L,936L and 960L.
Go Here>Router Troubleshooting

SuperPuppy

  • Level 1 Member
  • *
  • Posts: 2
Re: Year 2012 Date Bug Advisery
« Reply #7 on: May 19, 2013, 06:16:19 PM »

Thanks for the link, but it is all basic stuff on turning a router into an AP.

When I purchased the DIR-615s, I don't recall seeing any disclaimer anywhere that D-Link does not support the device being used as an AP.

I am not sure why you recommend using 192.168.0.50-.59 for the IP address for the AP.  Is there a reason for that?
I reserve .2-.9 as APs, set my reserved PCs and other devices .10-.30, and set the DHCP for .31-.255
Since I have three networks using the APs that double as a switch, and many devices, this makes it easy for me to remember when I got from network to network.

I purchased the DIR-615s one at a time over the years, I don't know how many years to be exact.
They all worked perfectly out of the box, and worked perfectly in my networks after changing the settings.

My tenant complaints started at the beginning of this year on all three networks.  All being the same complaints.
I did not change the settings or make any changes to the networks during this time.

It has to be either the date bug or some other sort of of time bomb set in the device.

Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 47834
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Year 2012 Date Bug Advisery
« Reply #8 on: May 19, 2013, 06:22:49 PM »

The date bug has nothing to do with operation or connections of the routers, is only to keep a date and log entries. Reason for .50 range is most APs are defaulted to that. Keeps conflicts from happening.

You probably have wireless interferences or not configured correctly.

Links>Wireless Installation Considerations and Managing Signal Congestion
Ensure the default (dlink) SSID name is changed. Can be anything and not something thats already in use by any neighboring WiFi routers. Under Setup/Wireless/Manual.
What wireless modes are you using?
2.4Ghz Routers only: Try single mode G or N or mixed G and N?
Channel Width set for Auto 20/40Mhz or try 20Mhz only.
Try setting a manual channel to a open or unused channel. 1, 6 or 11. 11 for single mode N if the channel is clear.
What security mode are you using? Preferred security is WPA-Personal. WPA2/AES Only. Some WiFi adapters don't support AES, so you might want to try TPIK only or Auto.
What wireless devices do you have connected?
Any cordless house phones?
Any other WiFi routers in the area? Link> Use InSSIDer to find out. How many?
Try turning off Short GI, WLAN Partition,and Extra Wireless Protection if you have it. Under Advanced/Advanced Wireless.
Enable WMM Enable Under Advanced/Advanced Wireless.
« Last Edit: December 25, 2014, 03:32:55 PM by FurryNutz »
Logged
Cable:200mb/10Mb>NetGear C7800>DIR-882>DGS-1100>HP 24pt Gb Switch. COVR-3902/2202/1203,DIR-2680,890L,882,880L,868L,DNR-202L,DNS-345x2,DCS-933L,936L and 960L.
Go Here>Router Troubleshooting