D-Link Forums
D-Link Wireless Access Points For Business => DAP-2553 => Topic started by: jhg on June 14, 2011, 03:23:49 PM
-
We have a new DAP-2553 configured in AP mode, DHCP enabled, nothing out of the ordinary.
It came with firmware 1.12, and kept crashing/hanging every few hours. Since upgrading to 1.21 the frequency of hangs has gone to once every 1-2 days. When it hangs, the web management interface also stops responding, and the only way to get it working again is to power-cycle it.
Hardware Version: A1
Firmware Version: 1.21 14:00:21 11/23/2010
Suggestions?
-
Same issue. I actually have 2 running, one crashes all the time the other never seems to. The one that crashes is set to master the one that doesn't is set to slave.
Interestingly it seems to still work in terms of client connections but going to the web console shows a 500 error.
-
Same issue here. We have around 20 units and they all do the same. The web interface crashes as does SNMP. Usually they continue to function as access points but not always. D-Link will not acknowledge the issue.
-
same issue here , i am an manufactureing firmware 1.12 , but seems it does not help upgrading to 1.21?
my devices were running for about a month , now wireless was still working on 1 device , but webpage was unaccesable , i got 500 error
after power cycle , it was working again...
i also see on the ftp server of d-link a newer firmware 1.25 , but seems that file is corrupted , it is 0 kb ...
ftp://ftp.dlink.pl/dap/dap-2553/driver_software/
-
I would contact your local D-Link support office and ask them about that file thats corrupt.
-
In my experience, all DAP-2553 and DAP-1353 have this odd problem - after some run time, no one is able to connect to the devices via WLAN. I have seen this in just about all locations with these devices. While not being able to connect to them, they can still be accessed via LAN. Also, resetting the device (or power cycling it) usually fixes them...
-
What FW version are you using on the DAP-2553?
In my experience, all DAP-2553 and DAP-1353 have this odd problem - after some run time, no one is able to connect to the devices via WLAN. I have seen this in just about all locations with these devices. While not being able to connect to them, they can still be accessed via LAN. Also, resetting the device (or power cycling it) usually fixes them...
-
My own 2 DAP-2553s are running with 1.26. I've updated them recently, hoping that it would fix this very problem, but it hasn't made any difference. One runs 2.4GHz, one runs 5GHz. The one running 2.4GHz seems to freeze quite a lot more often than the 5GHz.
I have some customers WHO also have the same devices, and they have a whole range of different firmware versions...and experiencing the same. The "have you tried power cycling it?" question is always my first question to customers...
I have invested in a WySpy analyzer and I've checked that there's no analoque transmissters around here.
-
These running in AP mode?
-
Yes, all in AP mode
-
yeah, samething here
i saw a "new" firmware though, 1.26 , any1 same issues on 1.26 ?
thnx
-
Nope. The new firmware documentation only mentions a change to the NTP-server.
Here's the change log 1.25 to 1.26:
F/W: Change NTP server IP from 207.232.83.70 to 61.67.210.241
F/W: Change default MAC to 00:15:E9:2C:75:00, which is used when manufacturing data removed
-
Are they using Difference channels?
Try to set them up manually using manual channel and turn OFF Auto channel scan. Set one for channel 1 and the other to channel 11 and test.
Try single mode G or mixed G and N.
Test at 20Mhz and Auto 20Mhz/40Mhz.
-
They're not at the same location - they're at multiple locations, in multiple configurations...and all failing on the same thing - error 8, and no new user is able to connect. Some run N, some just B/G...some run 2.4GHz, 2 of them runs 5GHz.
A simple Google search reveals that me and my clients aren't the only ones...
-
Ok, Seem like you have an error condition. I recommend that you phone contact D-Link support, ask for level 2 or higher and give them the error and details of whats going on.
I hope this will be resolved. Keep us posted on how it goes.
-
I have already reported it to a so-caled "Dlink TAC Engineer", but haven't heard anything from the guy for almost 2 weeks now...
-
Keep try to make contact with that engineer if you can. I have forwarded this on to my contact for review. I can't promise anything but we'll never know if we don't try.
Keep us posted.
-
So far, no update from Dlink. Asked a few days ago, and I was told, that they were still working on it.
So far, it seems to include XP + Vista + 7 + 8 PCs, iPhone 4, 4s and 5, Android 3+4 and 3 different MAC computers (at different clients). A strong feeling, from "the force", is telling me that it follows the general rule of IT trouble-shooting - the common denominator is usually the culprit. Also, a DAP 2553 power cycle fixes it for all clients...for a while.
-
Thanks for the update. I presume they are working on it and it will take some time to get resolved at the FW level.
Keep in touch with them as needed.
Good Luck.
-
Same issue. Firmware v1.27
-
Yup. And I still haven't gotten any solution from D-link.
I have already instructed our sellers and buyers not to buy/sell any more D-link until this case has been solved.
I guess having to switch D-link off/on all of the time is needed - the D-link DIR-655 we have at the repairshop has also been taken out. Internet is either non-existing or slow. Replacing it with a Zyxel USG-20W fixed everything.
D-link...what is happening? Ever since the AP-2000 and up...freezing is the general experience.
-
My DIR-655 has been working fine for me as others. There are other factors about that can contribute to Wifi routers not working well.
Let us know if your DIR-655 comes back online. Can post in the DIR-655 forum if you need further help.
What is the AP-2000?
Have you been in contact with D-Link about your 2553?
-
Yes, I have been in contact with D-link support about all the DAP-2553 we have sold. Not ONE of them runs OK - they all have reason 8 problems, no matter the client or location.
The AP-2000 is now an obsolete product but it had the same problem.
We were so tired with the DIR-655 that we have replaced it - and my collegues would be very mad if I set it back.
-
Ok, I have asked D-Link for review on this again. Can't promise anything. I hope something will come about and soon.
As for the DIR-655, what Rev is it.
What region are you located?
I'd be interested in checking on your 655 with you at some point...not in a customer environment.
Was the 655 in a home or business?
-
The DIR-655 used to run at our repair work shop - placed outside the city. There's only one neighbor WLAN, so it's not like it's the neighbor WLANs hammering it down...
I can't remember the revision, will check it tomorrow.
-
It seems Dlink has given up on us - they can't seem to reproduce the problem.
In ALL places, where we have sold a DAP-2553, they all loose all WiFi connectivity ability after a few days, some times less than a day. As stated above, it seems to go fastest in the places where a lot of other WiFi stations are placed.
I have also noticed this with smaller consumer models but would have expected a business model to be able to withstand roque stations - I was wrong.
Alternative?
We have, because of all this, been looking for other brands and one really seems to stand out from the crowd - Ruckus. We have set up a unified system (array of APs with central management) in the worst and busiest sites of all places, and we're able to walk several hundred feet, from one end of the campus to the other, without a single download ever stopping or stalling. It's been almost a month since we set it up and we haven't had a single comlaint since. THAT's the way it should work :-)
-
Glad you found a solution that works.
Good Luck.
-
Can someone review this and see if it works for you?
http://forums.dlink.com/index.php?topic=56048.0 (http://forums.dlink.com/index.php?topic=56048.0)
-
Tried that too, both a local NTP server at one site and a national NTP server at a second site - didn't do any difference.
-
Tried that too, both a local NTP server at one site and a national NTP server at a second site - didn't do any difference.
I think he refers to the "Group Key Update Interval" setting, not the NTP topic.
-
Gotcha.
I don't use multiple SSID, so it shouldn't be an issue...
-
There is a new firmware. Please test and tell the experience.
-
This is a NA region only release. I'll try and find out if other regions will get it as well. Can try if you like, just not officially supported on other regions.
http://forums.dlink.com/index.php?topic=56751.0 (http://forums.dlink.com/index.php?topic=56751.0)
-
I have tried this firmware for some time now (got it from Dlink support) and while it does seem to help...it doesn't remove the problem. We still have to reboot the DAP-2553 in the few places left where we see this AP...
NTP server is working in all places (using IP, not DNS name) + different expiration for each WLAN...
-
I would presume that if your still seeing this issues, it's either a environment condition or HW issue that is causing this problem...
I would recommend taking one of the problem APs and moving it or testing it in a different location, home or another place where there maybe less interferences as a test to see if the problem follows.
-
The 1.30 firmware has significantly improved but not fixed the hang problem with the DAP-2553. It still requires a reboot every week or two. I am pretty sure that it is not an environment problem as we have tested other access points on the network for weeks without issue. It is not likely a hardware problem as others have reported the same problem in this thread. Can D-Link please take another pass at this problem as we can not purchase more D-Link equipment without assurances that D-Link stands behind its products and will make things right?
-
Link>Welcome! (http://forums.dlink.com/index.php?topic=48135.0)
- What Hardware version is your DAP? Look at sticker under DAP.
- What region are you located?
- Was a Factory Reset performed before and after any firmware updates then set up from scratch?
Wireless Configurations
Links>Wireless Installation Considerations (http://forums.dlink.com/index.php?topic=48327.0) and Managing Signal Congestion (http://forums.dlink.com/index.php?topic=53228.0) and Good Neighbour Policy (http://forums.dlink.com/index.php?topic=10634.0)
- What wireless modes are you using?
- 2.4Ghz and 5Ghz routers: Try single mode G or N or mixed G and N on 2.4Ghz and single mode N or AC on 5Ghz?
- Channel Width set for Auto 20/40Mhz or try 20Mhz only.
- Try setting a manual Channel (http://en.wikipedia.org/wiki/Wireless_channel) to a open or unused channel. 1, 6 or 11. 11 for single mode N if the channel is clear. 13 for EU regions.
- What security mode are you using? Preferred security is WPA-Personal. WPA2/AES Only. Some WiFi adapters don't support AES (http://en.wikipedia.org/wiki/Advanced_Encryption_Standard), so you might want to try TPIK (http://en.wikipedia.org/wiki/Temporal_Key_Integrity_Protocol) only or Auto TPIK and AES.
- What wireless devices do you have connected?
- Any 2.4Ghz or 5Ghz cordless house phones or WiFi APs near by?
- Any other WiFi routers in the area? Link> Use InSSIDer (http://www.metageek.net/support/metageek-software-archives/) to find out. How many?
- If you have any of these options, Try turning OFF or ON Short GI (http://www.smallnetbuilder.com/wireless/wireless-features/30969-what-do-80211ns-optional-features-mean-for-you), WLAN Partition, Extra Wireless Protection and HT 20/40 Co-existence if you have it. Also testing with HT20/40Mhz Co-existence enabled will impact results as well. I prefer to use this option OFF. Recommended settings are default. Under Advanced/Advanced Wireless.
- Try setting Medium or Low power output settings and test again Under Advanced/Advanced Wireless.
The 1.30 firmware has significantly improved but not fixed the hang problem with the DAP-2553. It still requires a reboot every week or two. I am pretty sure that it is not an environment problem as we have tested other access points on the network for weeks without issue. It is not likely a hardware problem as others have reported the same problem in this thread. Can D-Link please take another pass at this problem as we can not purchase more D-Link equipment without assurances that D-Link stands behind its products and will make things right?
-
Hardware version A1
Located in USA
Factory reset performed before firmware upgrade to 1.30 and again after update
Only 2.4Ghz 802.11N used on main WiFi router and AP,
Main WiFi router signal is -80db on channel 1, this AP is on Ch 11, other WiFi signals in the area are weaker than -90db
There is a rarely used wireless DECT 6.0 house phone about 15ft away from the AP. There has been no correlation with phone use and AP problems,
Encryption is WPA2, AES, channel width 20Mhz, group key interval 1800, manual update
Short GI disabled, IGMP snooping disabled, connection limit disabled user limit is default value of 20 (there are about a dozen total , 1 Windows 7 laptop, Android and Apple pad computers and smartphones total that make occasional use of the AP.)
Intrusion detection disabled, QOS disabled,
Transmit power was 100% but changing it now to 50% per your guidance
-
I'd like you to test the channels by swapping from 11 to 1 on the AP and from 1 to 11 on the main host router please and test.
I'd test with QoS enabled on the AP as well just as a test.
Are there any 40Mhz supporting devices? You could try testing Channel Width set to Auto 20/40Mhz.
What is the Mfr and model of the main host route please?
Is there a option on the AP thats called HT20/40Mhz Co-existence? Some APs have this some dont. If your using single mode N, HT20/40Mhz co-existence can be disabled.
Keep us posted...
-
OK I've made the above suggested changes. I don't see HT20/40Mhz Co-existence.
The system is on an AT&T Uverse 2wire router as follows
Manufacturer Pace Plc
Model 3800HGV-B
Hardware Version 2700-100531-006
Software Version 6.9.1.42-plus.tm
While examining the main router I noticed that it is 802.11g while the AP was set for 802.11n only. Therefore I have also changed the setting on the AP to be mixed mode G,N & B. Let's see if this is the culprit I think it is!
-
Another test would be to disable the Wifi on the ISP modem. ISP modems may not have the best radios i them. :-\
-
Unfortunately the router WiFi is needed in its location and can not be disabled for long without a lot of people getting grumpy! ;-) Let's see what switching to mixed mode does.
-
Ok. Understand. ;)
-
Just an update on this issue. The DAP-2553 AP still locked up after 3 days with the above settings. At this point I gave the AP to a friend with a non AT&T Uverse 2wire base router to try in case it is the 2wire. Meanwhile I have installed a low cost TP-Link TP-WA901ND as an access point off of the Uverse 2wire. The purpose is to definitively determine if the problem is related to the 2wire or the DAP-2553. I hope to have a definitive follow up here in a few weeks.
-
Keep us posted.