Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[gigabit]

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.

[FurryNutz]

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.

[gigabit]

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.


 

[FurryNutz]

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.

[gigabit]

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?

[FurryNutz]

What region are you located?

[gigabit]

North America

[FurryNutz]

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.

[gigabit]

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..

[rasid]

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!

[FurryNutz]

Link>Welcome!
What Hardware version is your DAPs? Look at sticker.
Link>What Firmware 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
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 to find out. How many?
Try turning off Short GI, WLAN Partition,and Extra Wireless Protection if you have it.
Enable WMM Enable

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!

[FrontierDK]

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.

[FurryNutz]

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.

[jmpr]

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?

[FrontierDK]

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.