D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-625 => Topic started by: jwarren73 on February 26, 2008, 01:55:19 PM
-
I picked up the DIR-625 last week, and have had serious issues maintaining a stable connection, and I'm wondering whether its worth holding onto - sometimes it'll connect right when I boot up, sometimes I can't even force it to connect, and it'll just eventually work on its own.. when it does connect, the Windows wireless connection is showing it as an 802.11g broadcast, while the D-Link connnector is showing 300 Mbps connection... when its being screwy, I can't force a connection through either the D-Link or Windows connectors... The funny thing is, my wife's laptop connects perfectly every time, so it must be something in my local settings, or the wireless-n (645?) d-link adapter - the laptop is just connecting with the built in g adapter for now..
Mostly, I'm getting a ton of the following errors:
[INFO] Tue Feb 26 13:40:21 2008 Lease 192.168.0.134 renewed by client xxxxxxxxxxxxx
[INFO] Tue Feb 26 13:40:17 2008 Wireless system with MAC address xxxxxxxxxxxxx associated
[INFO] Tue Feb 26 13:40:17 2008 Wireless system with MAC address xxxxxxxxxxxxx disconnected for reason: Received Deauthentication.
[INFO] Tue Feb 26 13:40:16 2008 Lease 192.168.0.134 renewed by client xxxxxxxxxxxxx
[INFO] Tue Feb 26 13:40:12 2008 Wireless system with MAC address xxxxxxxxxxxxx associated
[INFO] Tue Feb 26 13:40:11 2008 Wireless system with MAC address xxxxxxxxxxxxx disconnected for reason: Received Deauthentication.
[INFO] Tue Feb 26 13:40:09 2008 Wireless system with MAC address xxxxxxxxxxxxx associated
[INFO] Tue Feb 26 13:39:50 2008 Wireless system with MAC address xxxxxxxxxxxxx disconnected for reason: Received Deauthentication.
Also, a bunch of:
[INFO] Tue Feb 26 13:50:46 2008 Blocked incoming TCP connection request from xx.xxx.xx.xxx:xxxx to xx.xxx.xx.xxx:xxxx
[INFO] Tue Feb 26 13:50:28 2008 Blocked incoming UDP packet from xx.xxx.xx.xxx:xxxx to xx.xxx.xx.xxx:xxxx
[INFO] Tue Feb 26 13:48:58 2008 Blocked outgoing TCP packet from xx.xxx.xx.xxx:xxxx to xx.xxx.xx.xxx:xxxx with unexpected acknowledgement 2752381048 (expected 3330153765 to 3330219285)
[INFO] Tue Feb 26 13:48:31 2008 Blocked incoming UDP packet from xx.xxx.xx.xxx:xxxx to xx.xxx.xx.xxx:xxxx
[INFO] Tue Feb 26 13:40:30 2008 Previous message repeated 4 times
-
I've seen the same sort of behavior with some of the computers on my network with the DIR-625. Either they get disconnected with the "Received De authentication" message, or not able to get a new DHCP lease and just kind of sitting there for a long while, endlessly trying to reconnect.
What seemed to clear that up for my troublesome machines was to set the computers to use a static IP address on the network, instead of DHCP. This will cause problems if you try to connect to a different network with the computer, so you'd have to switch back to using DHCP when wandering on other networks. Bit of a hassle, but it seems to work here.
-
my issue is related to this one, although i do not use the DIR-625 to assign IP addresses, since i have a server based network. this mostly happens with the wireless devices on the network. not sure why, but i get the deauthrization entry right about the time the network connection is dropped. i can still get on the internet just fine, but if i have to use the printer [attached to a dlink print server] or access a network drive, no go. connection lost.
i've tried editing the group policies on both notebooks and the server itself to no avail. i'm about to go back to the old router, since i never had issues with it.
-
I have encountered this. Turned out that it was caused by my Internet security software (Norton 360.) Check your questionable system and look at the firewall software / anti-virus software. You may have to tell the software to trust the wireless router's SSID.