Intel 3945ABG problems on 802.1x

[Christian]

Hi,

I recently bought a T60 2007-63G to one of my co-workers. I re-installed the whole machine because its with a Danish WXP and we only run on English software. Now after installing the 3945ABG wireless card and Access Connections I can not connect to any 802.1x networks at all. I can authenticate successfully but I never get an IP. When I had just installed it with drivers only I sometimes connected OK. On my own PC (T41p with an old 11/A/B/G card) I connect fast and secure and no problems at all. I have tried exporting the Access Connection profile from my computer to the new one with no luck.

Why does it not work? I don't have any MAC address filtering set up or anything.

/Christian

[wareynolds]

I do not use access connections, but Windows Zero Config.
I have no problem. I would recheck the setup and if you can the logs of the Authenticating server.

[Christian]

I do not use access connections, but Windows Zero Config.
I have no problem. I would recheck the setup and if you can the logs of the Authenticating server.

I just installed Odyssey Client Manager and it actually works. There must be some sort of misconfiguration between the Intel driver software and IBM Access Connections

/Christian

[wareynolds]

I just saw an email on the 3945ABG and problems with Trapeze AP's

Here is a blurb from the email which may or may not relate, but still....

> I am going to make a couple of assumptions. First, I am going to assume
> that you are either using WPA, or WPA 2. (I am fairly sure the bug
> doesn't exist for dynamic WEP.)
>
> There is a sequence number that is used in WPA to help it sync up the
> per-packet keys. According to the standards, this value should be set
> to 1 on the AP side, and 0 on the supplicant (client) side.
>
> The problem with the Trapeze (and by extension Enterasys/Nortel) gear is
> that they were setting this value to 0. Depending on how anal the
> driver (or supplicant) developers are, this can cause problems. I
> stumbled on to this bug a couple of months ago, and reported it to
> Trapeze. They claim to have a fixed version in QA right now. (I say
> "claim" because I have not yet had a chance to test it.) For Trapeze, I
> believe this fix is in releases starting with 4.2.2.4. (The current
> release (as of yesterday) on the web site is 4.2.2.3.)

[Christian]

I just saw an email on the 3945ABG and problems with Trapeze AP's

Here is a blurb from the email which may or may not relate, but still....

> I am going to make a couple of assumptions. First, I am going to assume
> that you are either using WPA, or WPA 2. (I am fairly sure the bug
> doesn't exist for dynamic WEP.)
>
> There is a sequence number that is used in WPA to help it sync up the
> per-packet keys. According to the standards, this value should be set
> to 1 on the AP side, and 0 on the supplicant (client) side.
>
> The problem with the Trapeze (and by extension Enterasys/Nortel) gear is
> that they were setting this value to 0. Depending on how anal the
> driver (or supplicant) developers are, this can cause problems. I
> stumbled on to this bug a couple of months ago, and reported it to
> Trapeze. They claim to have a fixed version in QA right now. (I say
> "claim" because I have not yet had a chance to test it.) For Trapeze, I
> believe this fix is in releases starting with 4.2.2.4. (The current
> release (as of yesterday) on the web site is 4.2.2.3.)

Ok! And here is the spooky thing: We use Trapeze equipment! All our AP's is Trapeze. Where did you read about this?

/Christian

[wareynolds]

I read about it on a wireless listserve for educause.

[Christian]

I read about it on a wireless listserve for educause.

I just upgraded the Trapeze system to the newest firmware and it actually fixed my problem. Thank you very much for posting that info! Amazing coincidence but _very_ helpful.

/Christian