• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Intel 2195ABG + WAP = no-no!

V

vfouquereau

Member
Ok, right to the point :

I have 3 computers, 2 desktop and 1 laptop.

Routeur = DI-624.

Settings : Click here for settings

In my 2 desktops, D-Link cards, latest drivers. No problem, everything dandy.

On my laptop, Intel 2195ABG, latest drivers. Can't get the card to get an IP adress.

I use a USB Key to transfer the key and copy/paste the key in. No chances it's not the good one. Zero chances. There is no return char or space anywhere in the key.

I rebooted the laptop and the router a couple of times.

Anyone has any clue?

Edit:

Forgot to mention that the laptop works at my girlfriend's house in which I setted up a DI-524 to work on WPA-PSK and the laptop has no problem there. What am I doing wrong at home?
 
It's not a bad key. I pasted the key in my router from a notepad file on my laptop, confirmed, drop the CAT5 then pasted it into my WiFi app, from the same clipboard. It's absolutely impossible that it's a bad key problem.

WPA-PSK, 63 ASCII char. Works fine at the girlfriend's house.

Trying to connect the laptop seems to lock the other 2 connections. Once I try to connect the laptop, the 2 other computers drop from the net.

I reverted the laptop from the Intel wifi app to the pure Windows management app. Exact same parameters as my desktop who also use the Windows management. No deal.

I'm puzzled.
 
bad key

try using a simple one like badkey.

-edit-
make sure you're using the same encryption/key methods on both ends.
 
Ok. For the last time, just to make extra sure it's clear : its not the key. The key is fine. It's A-ok. If you don't know why I'm having problem, it's no big deal, you can't resolve all the problems in the world, nobody will think any less of you. Now, if you don't have any more clues than the key, move on please.

Let the record show that I did try a simple 9 characters, all letters key and it did not work.

-edit to answer to edit-

I am sure of it since way before I posted here.
 
Ok, got some things working. I am currently writing this message from my laptop (using a bad key it seems, joking) and I find that if I assing an IP without DHCP, it's working. So it's not the key, the encryption or whatnot, it's the DHCP lease that is not working. But why only on my laptop? 😱 The mystery thicken. I'll get to work on that, with a static IP it seems.
 
sorry if I was short, keyboard problems on my laptop.

It's just that 99.999% of the time you are describing a bad key, or not having the same encryption settings on both ends. Associating to the AP but not being able to communicate at layer2/3 is literally always a bad key or disagreement on encryption.

Failing that, upgrade the drivers on the intel.

I don't see any mention of what kind of cipher (tkip, aes, and all the other alphabet soup stuff) or version of WPA the client and access point are running? Check that.


-edit-, well if you have good communication at layer3 and above using your key and encryption, make sure the DHCP server can hand out enough addresses.
 
Yeah, thanks for making sure I was using the good key, but I did encounter this type of problem before and I'm quite aware that these are the symptoms.

My DHCP should be able to give out 49 IP.
192.168.0.1 ~ 50.
Well, not really the 1st one... 😉

There are 3 computers on the network.
 
Made a quick mistake here, marked 192.168.0.1 as DHCPable. Fixed by putting the range from 192.168.0.10 ~ 50. Rebooted everything : computers, modem, router.

Still not working on the laptop, still working on the desktops.
 
Well, that's it. I fixed it by putting a static IP on my laptop. It's fixing a leak with scotch tape but eh, when nothing works, this works. I don't have a clue why this is happening. I'll put a list of keywords in hope that someone will stumble on the same problem I have, use this temporary solution to fix his laptop long enough to get things done and find a solution.

Intel Centrino ABG 2195 2915 DLink D-Link Router DHCP Static "Keep on truckin"

If anybody has the slightest clue what this is all about, send a PM my way.
 
I've never had any problems with my 2915...

I would turn security off and try again?

barring that, get a laptop with Airopeek eval and sniff the air to find out what's happening
 
Hmmm never had that problem under windows, only Linux....

and before someone calls me crazy again... from ipw2200 page...

Fix problem with broadcast packets (DHCP, etc.) with 1.0.11, 1.0.12.: patch
If you experience problems with DHCP stalling out and not being able to obtain an IP address, but statically configuring an IP address allows you to access the network, you may need this patch to change how broadcast packets are detected with older kernels.
Click to expand...

BTW make sure you have turbo, accelerated mode, etc... off.... they tend to mess up non-atheros/D-Link branded cards. Also make sure you have the latest firmware, sometimes routers just dont like centrino.
 
The following is what I found out after trying various things:

With D-Link DI-624 wireless router configured with WPA-PSK encryption, when a computer with Intel PRO 2915ABG wireless adapter tries to connect, connection will fail at the stage where an IP address is requested from the DHCP server in the router. There was no problem when WEP was used instead of WPS-PSK. There was no problem when the same computer with Intel PRO 2915ABG connects to other routers with the exact same setting (including D-Link DI-524). There was no problem when other computers with different wireless adapters connect to DI-624. It was the exact combination of WPA-PSK, DI-624, and Intel PRO 2915ABG which caused the problem.

There is a workaround which works most of the time: Configure the wireless adapter setting with a fixed IP address so that the DHCP server in the router does not have to be invoked.

I just noticed on the D-Link web site today that there is a new beta 2.75 version of the firmware
http://support.dlink.com/products/view.asp?productid=DI%2D624%5FrevC
This solves the problem.

It is incredible how much time of my time this stupid problem wastes!
I hope this helps others in the same situation.

 
You must log in or register to reply here.

TRENDING THREADS

Back
Top