D-Link Forums
D-Link Wireless Access Points For Business => DAP-2553 => Topic started by: brooksthepro on August 09, 2012, 09:54:12 AM
-
We have 6 of these AP's in 3 different offices. One office with 3, one office with 2 and one office with 1.
We seem to be having the most problems with the office with 3 AP's. Sometimes every day, sometimes every couple hours, at least one of the AP's stops working. Devices can still connect to it, but they just get a 169 IP, they will never get a local IP. Sometimes though, if I set the client IP to static I can then connect, but not always. When an AP is having an issue sometimes I can't access the web GUI as well, it just times out. I then have to powercycle the AP and it will work again for another couple hours or sometimes a day then it drops again. I have tried adding static ARP entries and static IP assignment in our Sonicwall, same problem. Our Sonicwall handles DHCP.
When I first installed these in our office they worked fine for a couple months, now I am having this issue and its driving me crazy. I have been on the phone with DLINK business support, we have tried changing the channels around, turning encryption on and off, change the signal power, update to the latest firmware, downgrade to the previous firmware. I have tried just using one router instead of all 3, same problem. I have tried resetting back to factory settings, same problem.
The other two offices dont seem to have as many issues, they will go for a few days before they get the same issue, sometimes a couple weeks. But I always end up getting a call and having to reset them at some point during the week.
All offices have Sonicwall's and we VPN to all the offices. I have spoken with sonicwall and as far as they can see there is nothing in the sonicwall that could cause a problem like this.
I also just added a bonjour print service for iOS printing called Fingerprint on the network, not sure if that would cause any issue.
Again, I have spoken with the DLink business support but the only solution they could give me is to RMA the AP's. I am not convinced this will solve the problem, since it isnt just one device that is having the problem.
Any help would be greatly appreciated. Thanks.
-
What wireless modes are you using? Under Setup/Wireless/Manual.
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. Ensure each AP is on a different channel.
Any other WiFi routers in the area? Link> Use InSSIDer (http://www.metageek.net/) to find out. How many?
I would start with turning OFF 2 of the 3 APs and test to see if one works for a while, then switch to the other one until the 3rd one is tested with out the other APs going. See if any one of them exhibits this problem. Then I would turn on 2 AP and test to see if the problem presents again. Then the 3rd. Might help narrow down if there is a particular unit exhibiting this problem or if just using 1 AP while testing works.
Possible environment interference or could be HW related. IF you find that one particular AP exhibits the problem, I would move it to the other office and see if the problem follows, if it does, then you'll know it needs to be RMAd.
Keep us posted.
-
Currently we are using Mixed N G and B.
Channel Width is set to Auto 20/40mhz
I am using channels 1,6,11
There are many networks detected on InSSIDer but the only strong signal close to us is using channel 6.
I will do what you suggest and see if it makes a difference, its just frustrating/hard to troubleshoot because it takes so long before it acts up again to know if changes I made, made a difference. So it will probably take some time before I can try all of your suggestions. I will try all of them and let you know my results.
-
If there are many networks near by, be aware they can impact and be a cause of interference. Everyone is trying to use a open and clear channel. And only having 11 available, might be running into others. I call this WiFi congestion. ::)
-
I've been experiencing the same problems with some of our DAP-2553's.
One setting that I can't change to match your suggestion with the current firmware is the G-N-B settings. On my current AP's the only options are:
Mixed N-G-B
Mixed G-B
N Only
N Only isn't going to work for us, and when trying the other two settings doesn't appear to make a difference. It takes about a day or so, but then we need to reboot the AP's to make them accept clients. On the upsite, the current firmware, 1.25 does allow you to reboot from the GUI and doesn't require a hard power reset anymore like 1.21 and prior firmware did.
DLink really needs to address this AP and get the firmware issues resolved.
-
Any other WiFi routers in the area? Link> Use InSSIDer (http://www.metageek.net/) to find out. How many?
What region are you located?
I've been experiencing the same problems with some of our DAP-2553's.
One setting that I can't change to match your suggestion with the current firmware is the G-N-B settings. On my current AP's the only options are:
Mixed N-G-B
Mixed G-B
N Only
N Only isn't going to work for us, and when trying the other two settings doesn't appear to make a difference. It takes about a day or so, but then we need to reboot the AP's to make them accept clients. On the upsite, the current firmware, 1.25 does allow you to reboot from the GUI and doesn't require a hard power reset anymore like 1.21 and prior firmware did.
DLink really needs to address this AP and get the firmware issues resolved.
-
We're out of town a bit, no close neighbors to our facility so that eliminates cross contamination from other AP's.
We're a little southeast of Toledo Ohio.
-
Any cordless house phones?
I might suggest contacting DLink support, level 2 on the phone and see if there is any additional help. Been some cases there needs to be an RMA done.
-
I know this thread is a little older but EXACT same issue, did you ever get it resolved??
Thanks
Brad
-
Could you answer some of the questions posted in relay #1?
I know this thread is a little older but EXACT same issue, did you ever get it resolved??
Thanks
Brad
-
only one ap, connected to a dfl-260E running as the dhcp and dns server.
20mhz only, CH 11 (checked insider and ch11 is pretty clear in area), Mixed B, G, N, WPA Personal, this is second unit in this environment to do this, this unit is fresh from RMA dept with FW 1.26. Have already talked to tier 3 support and they don't have any "ideas" of the cause. Funny thing is I have these units working together at other sites NO problem..
-
Others site have same FW and configuration settings?
Would be a good test to swap this unit into place at one of the other sites and test to see if the problem follows.
Try single mode G or N or mixed G and N if B mode isn't needed.
-
can not do the swap, the other sites are separate business's. BUt they use a windows dhcp/dns unlike this one that uses the DFL. I do have a DIR-130 with a DAP-2553 at home that works just fine. Dosnt make sense. the units remain connected just no net ability.
-
Can you test this one at home to see?
Need to see if this unit works in a different area and if the problem follows. This could be environment related...
-
will do tomorrow , and post results.
Brad
-
Had the same issue, however, it was an issue of timing and schedules?
What I discovered was due to NTP failure which force a default time reset to Jan1 2000. The "scheduled on" time was out of whack and the Multi-SSID radio was not active. I run three Units in an array with (M,MB and S) and 5 VLANs over 4 SSID's.
-
So did correcting the NTP time and values correct your problems?
Had the same issue, however, it was an issue of timing and schedules?
What I discovered was due to NTP failure which force a default time reset to Jan1 2000. The "scheduled on" time was out of whack and the Multi-SSID radio was not active. I run three Units in an array with (M,MB and S) and 5 VLANs over 4 SSID's.
-
So did correcting the NTP time and values correct your problems?
Yes, however, with the 1.25 firmware the NTP get is irradic. If there is a power loss to the AP then it may or may not perform the NTP get correctly against the configures ntp server. If it does not and the time is well beyond your scheduled on time then it appears as though the AP is failing. The reality is that the AP is performing against the set schedule.
Other issue is I could not set the external NTP server via the gui I had to set the IP via CLI... Notice this with the time setting on the master as well. The time had to be set via CLI.
-
What region are you located?
Is this CLI process documented in the User Manual some place or is this a back door work around?
What router or Internet services is this DAP connected too?
I would recommend that if NTP services seem to be not acting correctly, I would recommend that you phone contact DLink support and inquire about it. There could be an issue with NTP services in FW. NTP services should be fully configurable in the GUI.
-
The Process' for setting both time, Date Manually and setting up NTP via CLI is covered in the CLI manual. But these two issues are very much a problem in 1.25 as verified through all three DAP-2553's I have do the same thing. It may be a while before I have time to contact support on this. Your welcome to run with it. I fix all my stuff via an ssh start-up script. :)
any idea why AP Manager II is not avaiable for download from the ftp site? Know a trusted source that I can get it along with and 1.25 updates?
-
What region are you located?
-
North America
-
All items posted to the web are linked here:
ftp://ftp.dlink.com/Wireless/dap2553/
I don't own this unit. Just here to provide support if I can. You'll need to contact DLink support directly if you need to.
I'll forward this on to DLink and see if they respond.
-
All items posted to the web are linked here:
ftp://ftp.dlink.com/Wireless/dap2553/
I don't own this unit. Just here to provide support if I can. You'll need to contact DLink support directly if you need to.
I'll forward this on to DLink and see if they respond.
Thx..
-
We have the same issue as well.
Config: 3 APs (DAP-2553), all with same SSID, different channels. Not many other wireless devices in the area.
Symptoms: Everything would be fine for a couple days. Then out of the blue, some people couldn't get an IP address but other people could continue using it for a while longer. Then, eventually, no one could use it. The APs need a restart and then work again. OR, if the computers were assigned static IPs, they worked.
Here is what I found out: I waited until the issue started. Then, I did WireShark packet captures at two points, one behind the access point and one at the wireless laptop. The laptop sent out the DHCP broadcast, the wireless received it and forwarded it along to the wired network. Our DHCP server responded with a DHCP offer and sent the broadcast back out over the network. This is where the issue happens. THE APs DON'T FORWARD ANY BROADCAST TRAFFIC BACK OUT THROUGH THE WIRELESS! That's why people get the 169.x.x.x address because they don't receive back a DHCP offer. This isn't just DHCP, it's ALL BROADCAST TRAFFIC. The AP receives wireless broadcasts but won't pass broadcasts back out through the wireless.
Here is my thoughts on why: I have NO FRIGGIN clue! But knowing it's an outbound broadcast issue should make it an easy find for the firmware developers.
Please help ASAP because I'm about to dump these brand new DAP-2553's and buy 3 Aruba Networks APs!
-
Link>Welcome! (http://forums.dlink.com/index.php?topic=41537.0)
What Hardware version is your DAPs? Look at sticker.
Link>What Firmware (http://forums.dlink.com/index.php?topic=47512.0) version is currently loaded?
What region are you located?
How are the DAPs connected to the main host router?
Has a Factory Reset been performed?
Try using only 1 DAP connected to the main host router and test to see if the connection drops using the one AP while the others are turned OFF.
Link>Wireless Installation Considerations (http://forums.dlink.com/index.php?topic=48327.0)
What wireless modes are you using? Under Setup/Wireless/Manual.
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 (http://www.metageek.net/) to find out. How many?
Try turning off Short GI, WLAN Partition,and Extra Wireless Protection if you have it.
Enable WMM Enable (http://forums.dlink.com/index.php?topic=50738.0)
We have the same issue as well.
Config: 3 APs (DAP-2553), all with same SSID, different channels. Not many other wireless devices in the area.
Symptoms: Everything would be fine for a couple days. Then out of the blue, some people couldn't get an IP address but other people could continue using it for a while longer. Then, eventually, no one could use it. The APs need a restart and then work again. OR, if the computers were assigned static IPs, they worked.
Here is what I found out: I waited until the issue started. Then, I did WireShark packet captures at two points, one behind the access point and one at the wireless laptop. The laptop sent out the DHCP broadcast, the wireless received it and forwarded it along to the wired network. Our DHCP server responded with a DHCP offer and sent the broadcast back out over the network. This is where the issue happens. THE APs DON'T FORWARD ANY BROADCAST TRAFFIC BACK OUT THROUGH THE WIRELESS! That's why people get the 169.x.x.x address because they don't receive back a DHCP offer. This isn't just DHCP, it's ALL BROADCAST TRAFFIC. The AP receives wireless broadcasts but won't pass broadcasts back out through the wireless.
Here is my thoughts on why: I have NO FRIGGIN clue! But knowing it's an outbound broadcast issue should make it an easy find for the firmware developers.
Please help ASAP because I'm about to dump these brand new DAP-2553's and buy 3 Aruba Networks APs!
-
It seems to be a problems with most Dlink access points for some reason - not being able to get any LAN connectivity through most Dlink access points, after running for some days.
Power cycling the 2553 unit removes the problem...for some days. I really wish this problem would be removed, because it's otherwise really a good access point, with gigabit on the back, it's FAST.
-
Thank you for the feedback.
What version of FW do you have loaded on your unit?
What model DAP do you have?
I recommend that you phone contact D-Link support and get help and information on this. This is an issue with FW and is beyond support here in the forums and must be addresses directly with D-Link.
Thank you.
-
Same problem here. I have a 2553 in Spain, and it looses "life" after about 2 days. I have tried all sorts of setups with the same result. It is perfect when it is restarted, but in some hours...
Any notice of a future fw that will solve this?
-
No solution as of yet. No matter which client I have sold this model to, they all have the same problem - as you have described.
I have been sending configurations, logs etc. to Dlink - no solution yet.
We recently had Dlink visiting on a seminar on surveillance solutons - but we have instructed our sales dpt. not to buy/sell any Dlink until this has been resolved.
-
Please read my new topic "the solution to..." I think it may help you. My problem has been solved.
http://forums.dlink.com/index.php?topic=56048.0 (http://forums.dlink.com/index.php?topic=56048.0)
-
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)
-
The file ends in WW, so it is worldwide version, and I have downloaded it from http://tsd.dlink.com.tw the global site.
-
Thank you for confirming. ;)