• April 24, 2024, 03:36:37 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: limited to no connectivity - DIR-615  (Read 5564 times)

shaunkothzr1

  • Level 1 Member
  • *
  • Posts: 1
limited to no connectivity - DIR-615
« on: March 20, 2011, 10:20:59 AM »
I have a D-Link DIR-615 using it only as an AP no DHCP from the router.  I have the security setup as Auto (WPA or WPA2)-PSK

Firmware: 3.10N
Hardware:C1

At least 3 times a week I get limited to no connectivity from 3 different devices, 2 laptops and a smartphone. 
I have checked the logs and i keep seeing Wireless system with Mac address 00:25:xx:xx:xx:xx disassociate reason 8, as well as Wireless system with Mac address 00:23:xx:xx:xx:xx deauthenticate reason 3.  From what I found both those codes mean : Operating System moved the client to another access point using non-aggressive load balancing and The access point went offline, deauthenticating the client.    I am thinking that the access point may be going offline.  the question is how do I correct this?

Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: limited to no connectivity - DIR-615
« Reply #1 on: March 20, 2011, 10:52:17 AM »
What are these devices you are connecting?

What happens if you change from Mixed mode to Single mode G?
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

Hard Harry

  • Guest
Re: limited to no connectivity - DIR-615
« Reply #2 on: March 20, 2011, 11:29:09 AM »
Maybe check the Roaming tendancy on the Wireless NIC's advanced settings? Some can be set to roam, or move to another wireless AP if there is a heavy drop in datarate. But if its happening on multiple computers, we should focus on the drop of the datarate, rather then the fact it's moving. What in the log right before those entries?
Logged