D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DGL-4500 => Topic started by: Reinvented on August 20, 2008, 02:12:23 PM
-
I've been using 1.12 for a while now, and I'm having trouble using my Laptop's wireless 2200BG connection. It cannot connect to the router at all under WEP/WPA/WPA2. It just completely refuses it. This is using the latest Intel drivers, and also the old ProSet Wireless 11 series.
Just wondering if anyone else is having problems, or if you have noted it so it can be fixed under the next release.
Thanks!
-
:'(
Are you guys even aware of this?
-
I'm pretty sure that I have a laptop with this card and it's working fine. The only difference is that I switched to unsecured with MAC filtering to hopefully improve stability.
Seems like 1.12 with MAC filtering is fairly stable with my wireless connections on both the 2200BG and my 4965AGN. I switched to unsecured with MAC filtering at 1.02 and haven't switched back to try it on 1.12.
-
Still doesn't work...
-
I have confirmed that I do indeed have an Intel 2200BG, and it is working fine.
There must be some issue on your side....
-
Are you using WEP/WPA/WPA2? You said you weren't, so your claim is invalid.
-
My claim is not invalid. My card is working. I told you that I didn't use the security and instead used MAC filtering. Your reply was "still doesn't work". I think that anyone would assume with that minimal response that you tried MAC filtering with no success.
My response is perfectly valid - like I said, my card is working. If you care about getting your card working, now you know how. I was only trying to offer you assistance.
-
Woogie,
Are you saying that MAC filtering is working for you?
-
Yes, MAC filtering is working for me. I just wish it was wireless-only MAC filtering.
1.12 seems to be much more stable as far as connection drops for me - both wireless and wired.
-
Lycan,
Any info on this?
Because, it's not working with any encryption at all.
Just causes it to hang and not pull up an IP address.
The above is not something I want to do, just to get my stuff to work, and isn't really a solution at all.
-
No, thats a tricky one. We don't have that adapter here to test with.
If you remove the encryption it still doesn't connect?
-
I removed all encryption, and left it in the default mixed mode for N, B, and G.
Connects just fine.
Again, I tried it with different versions of the Pro/Set Wireless tools, and they are giving me problems.
It didn't do this with 1.11, or 1.10. So, it's definitely either something with the drivers, or else a compatibility with the firmware itself.
Somewhere though, it has trouble authenticating itself.
Thanks!
Edit: Here's the router logs regarding it.
[INFO] Thu Sep 04 17:04:33 2008 xxxxxxxx: Wireless system with MAC address 000000000000 disconnected for reason: Authentication Failed
[INFO] Thu Sep 04 17:04:21 2008 xxxxxxxx: Wireless system with MAC address 00166F5C36B3 associated
[INFO] Thu Sep 04 17:04:21 2008 Above message repeated 1 times
[INFO] Thu Sep 04 17:04:20 2008 xxxxxxxx: Wireless system with MAC address 000000000000 disconnected for reason: Received Deauthentication
[INFO] Thu Sep 04 17:04:10 2008 xxxxxxxx: Wireless system with MAC address 00166F5C36B3 associated
[INFO] Thu Sep 04 17:04:10 2008 Above message repeated 1 times
[INFO] Thu Sep 04 17:04:10 2008 xxxxxxxx: Wireless system with MAC address 000000000000 disconnected for reason: Authentication Failed
[INFO] Thu Sep 04 17:03:58 2008 xxxxxxxx: Wireless system with MAC address 00166F5C36B3 associated
[INFO] Thu Sep 04 17:03:58 2008 Above message repeated 1 times
[INFO] Thu Sep 04 17:03:58 2008 xxxxxxxx: Wireless system with MAC address 000000000000 disconnected for reason: Authentication Failed
[INFO] Thu Sep 04 17:03:46 2008 xxxxxxxx: Wireless system with MAC address 00166F5C36B3 associated
[INFO] Thu Sep 04 17:03:46 2008 Above message repeated 1 times
[INFO] Thu Sep 04 17:03:45 2008 xxxxxxxx: Wireless system with MAC address 000000000000 disconnected for reason: Received Deauthentication
[INFO] Thu Sep 04 17:03:37 2008 xxxxxxxx: Wireless system with MAC address 00166F5C36B3 associated
[INFO] Thu Sep 04 17:03:37 2008 Above message repeated 1 times
[INFO] Thu Sep 04 17:03:37 2008 xxxxxxxx: Wireless system with MAC address 000000000000 disconnected for reason: Authentication Failed
[INFO] Thu Sep 04 17:03:25 2008 xxxxxxxx: Wireless system with MAC address 00166F5C36B3 associated
[INFO] Thu Sep 04 17:03:25 2008 Above message repeated 1 times
[INFO] Thu Sep 04 17:03:24 2008 xxxxxxxx: Wireless system with MAC address 000000000000 disconnected for reason: Received Deauthentication
[INFO] Thu Sep 04 17:03:23 2008 xxxxxxxx: Wireless system with MAC address 00166F5C36B3 associated
[INFO] Thu Sep 04 17:03:23 2008 Above message repeated 1 times
[INFO] Thu Sep 04 17:03:23 2008 xxxxxxxx: Wireless system with MAC address 000000000000 disconnected for reason: Authentication Failed
[INFO] Thu Sep 04 17:03:11 2008 xxxxxxxx: Wireless system with MAC address 00166F5C36B3 associated
[INFO] Thu Sep 04 17:03:11 2008 Above message repeated 1 times
[INFO] Thu Sep 04 17:03:11 2008 xxxxxxxx: Wireless system with MAC address 000000000000 disconnected for reason: Received Deauthentication
[INFO] Thu Sep 04 17:03:05 2008 xxxxxxxx: Wireless system with MAC address 00166F5C36B3 associated
[INFO] Thu Sep 04 17:03:05 2008 Above message repeated 1 times
[INFO] Thu Sep 04 17:03:05 2008 xxxxxxxx: Wireless system with MAC address 000000000000 disconnected for reason: Authentication Failed
[INFO] Thu Sep 04 17:02:53 2008 xxxxxxxx: Wireless system with MAC address 00166F5C36B3 associated
[INFO] Thu Sep 04 17:02:53 2008 Above message repeated 1 times
[INFO] Thu Sep 04 17:02:53 2008 xxxxxxxx: Wireless system with MAC address 000000000000 disconnected for reason: Authentication Failed
[INFO] Thu Sep 04 17:02:41 2008 xxxxxxxx: Wireless system with MAC address 00166F5C36B3 associated
[INFO] Thu Sep 04 17:02:41 2008 Above message repeated 1 times
[INFO] Thu Sep 04 17:02:41 2008 xxxxxxxx: Wireless system with MAC address 000000000000 disconnected for reason: Authentication Failed
[INFO] Thu Sep 04 17:02:29 2008 xxxxxxxx: Wireless system with MAC address 00166F5C36B3 associated
[INFO] Thu Sep 04 17:02:29 2008 Above message repeated 1 times
[INFO] Thu Sep 04 17:01:55 2008 xxxxxxxx: Wireless system with MAC address 000000000000 disconnected for reason: Received Deauthentication
[INFO] Thu Sep 04 17:01:46 2008 xxxxxxxx: Wireless system with MAC address 00166F5C36B3 associated
[INFO] Thu Sep 04 17:01:46 2008 Above message repeated 1 times
[INFO] Thu Sep 04 17:01:46 2008 xxxxxxxx: Wireless system with MAC address 000000000000 disconnected for reason: Authentication Failed
[INFO] Thu Sep 04 17:01:34 2008 xxxxxxxx: Wireless system with MAC address 00166F5C36B3 associated
[INFO] Thu Sep 04 17:01:34 2008 Above message repeated 1 times
[INFO] Thu Sep 04 17:01:28 2008 xxxxxxxx: Wireless system with MAC address 0018DE163B4E associated
[INFO] Thu Sep 04 17:01:28 2008 Above message repeated 1 times
[INFO] Thu Sep 04 17:01:28 2008 xxxxxxxx: Wireless system with MAC address 000000000000 disconnected for reason: Received Deauthentication
[INFO] Thu Sep 04 17:01:28 2008 Wireless link is up
-
IF you use windows zero config does this continue?
-
Yes, it still does.
-
Gotcha. Escalating to PM.
-
Hi Lycan,
Thanks for the update. Let me know if you need any other information regarding this at all.
-
hi Lycan,
I've thrown in my DGL-4300 for a bit, to see if it did the same thing. I forgot to check with it running 1.8 FW, but sure enough, it does it with 1.9 FW, and 2200BG. I don't have time to test, but it still gets stuck at the authenticating part, and then disconnects.
Still using the same encryption and all... WPA2-Personal. AES-CCMP as well.
This is also using the latest Intel drivers 12.0.4.0.
Hope this helps!
Thanks!
Edit: I haven't tried to force it using the WPA, or even TKIP, but I'm sure it won't work unless encryption is off.
-
have you looked at intels site? Do they have any information about this or this problem with other routers?
-
Checked the release notes, and the only major problem that I could see was that for draft N speeds to be achieved, WPA mode had to be used, with either AES/CCMP, or no encryption at all.
I haven't seen any updates since August 1st, but I doubt they can fix this problem. They are pretty uncooperative when it comes to fixing drivers. They are rock solid, but I'm wondering if there's anything you can do on your end?
-
It's a difficult issue to tackle becuase it's a specific adapter we're having trouble with. Not a very broad issue.
I'll ask the Pm to see about obtaining the adapter and see what happens..
-
It's only like one of the most widely used adapters.
I would like to think that DLink would be interested in confirming one of these would work correctly with their equipment.
Seeing how 1.12 code has been having all kinds of problems, I will not be updating my unit until I see more positive results. Personally I have 4 laptops with that adapter (2 from work, 2 personal) among other units I bring home from work frequently for testing.
I would be more than willing to test, but not on my router.
-
Any word on this Lycan?
I've got a MacBook Pro coming in a few days, and I'd like to try out the "N" wireless network.
Running in Mixed Mode, for B, G, and N, on the 2.4 Ghz, channel 11 stuff; will I see any problems?
I'm hearing all sorts of things, as to why it won't work, and what might my maximum achievable connection be?
I'm just hoping that I can get all my wireless devices connected without much issue at all.
Let me know!
Thanks!
-
I am having the same problem - My Intel Pro has had all sorts of problems - but an XPS1730 has been rock solid. I did have some luck adjusting rts thresholds and fragmentation thresholds down to 2100. It actually ran well for 3-4 hours. I then reactivated the Gamefuel section (it had been off) and trouble returned. I'm running mixed mode, WAP, 1.12.
-
Are you guys running WiSH?
-
Hi Lycan,
yes, we are running WISH.
-
Disable it, see if the behavior continues.
-
I just updated to the 1.13 beta code, and should I still test it? I haven't tried anything else yet.
-
Continue to test and report behavior. I'd like feed back, I'm having a hard time replicating the issues seen with this unit.
Any and all feed back is welcome. (as long as it's helpful and not slanderous)
-
What version of the Intel pro/set wireless are you using? I'm using 12.0.4.0...which is the latest.
On top of that, it works with no encryption at all, but WEP, WPA/WPA2 fail to work.
2.4 GHz Band
N and G Only
Channel 11
Visible
Auto Channel Width
Automatic Rate
WPA-Personal
Auto WPA/WPA2
3600 Update
WISH has been enabled and disabled, but still nothing.
This isn't good at all.
While on the topic of wireless:
-Wireless streaming is slow, and takes a really long time to buffer a video via network.
-With 1.13 Code: Setting Wireless network to 2.4 GHz Bands N and G ONLY and Manual Channel select of channel 11, as well as Channel Width of Auto 20/40 results in secondary channel to be used. Is this normal? It keeps the channel width at 40 also...which is strange.
-Incorrect reporting of phys connection rates.
-Signal strength generally low.
-Incompatibility with various wireless adapters. ie 2200BG, and 3945ABG de-authenticating yet once again. (This didn't even get fixed in the 4300's 1.9 FW) On the 4500, it can't even authenticate the 2200BG with any encryption, even though it supports both WPA and WPA2.
-
Whats the serial number of your unit?
-
F3OB182003891
HW: A1
F/W Version: 1.02
-
Also to add to the list, it produces a lot of errors when doing LAN file transfers, via wireless. Wired -> Wireless, Wireless -> Wireless, and Wireless -> Wired.
Kinda needs to get fixed a bit too...
-
I had read somewhere else WiSH could be a problem - so I had it off.
-
Any update on this Lycan?
-
What version of the Intel pro/set wireless are you using? I'm using 12.0.4.0...which is the latest.
On top of that, it works with no encryption at all, but WEP, WPA/WPA2 fail to work
go down to the 11 series
I had problems with the 12 series as well. 11 fixed me just fine though
running WPA2
Any word on this Lycan?
I've got a MacBook Pro coming in a few days, and I'd like to try out the "N" wireless network.
Running in Mixed Mode, for B, G, and N, on the 2.4 Ghz, channel 11 stuff; will I see any problems?
I'm hearing all sorts of things, as to why it won't work, and what might my maximum achievable connection be?
I'm just hoping that I can get all my wireless devices connected without much issue at all.
Let me know!
Thanks!
these use Broadcom cards, so you should be fine
I have a 2.33 and a 2.5 and both are working fine
:edit
still running 1.02 until I see more positive results on newer firmware
-
Just to correct you, they use Aetheros chips, not Broadcom.
I've heard mixed reviews about it. Seems to work okay on the MBP, but the max speed is so bad.
So, it makes me a bit upset.
I tried reverting back to the 11 drivers, but that didn't help much. It caused me to de-authenticate on the new FW.
-
Just to correct you, they use Aetheros chips, not Broadcom.
I've heard mixed reviews about it. Seems to work okay on the MBP, but the max speed is so bad.
So, it makes me a bit upset.
I tried reverting back to the 11 drivers, but that didn't help much. It caused me to de-authenticate on the new FW.
my brand new 2.5 is using Broadcom drivers in Bootcamp mode, so I assume it is Broadcom.
As for the 2.33, it could be Atheros, I have never done Bootcamp on it to confirm in that regard.... probably should check the PCI info and cross reference that for true confirmation.
as for the v11 drivers. Sorry to hear it didn't help. I couldn't get any of my 3 2200BG computers to connect to router with the v12 series. I didn't screw arond with the router at all, just downgraded the driver and software to v11 and all 3 have been working great.
:edit
just cross referenced the PCI vendor code and the 2.5 does indeed use Broadcom while the 2.33 uses Atheros.
-
All of the new MBP's since February should be using Broadcom chips. While the older Core Duo, and what not should be running Aetheros.
Personally, I'm not a big fan of either. But at least it works.
More compatibility would be great too.