 |
 |
802.1X issue
|
|
|
|
|
Dedicated MacNNer
Join Date: Aug 2002
Status:
Offline
|
|
I've got a user on my network that is having problems with his MacBook Pro.
In a nutshell, the wireless adapter is trying to get an address via DHCP before it authenticates using 802.1X. The result is he gets a 169.254 address and then 5 minutes later, as per the RFC, DHCP is tried again and he gets the correct address.
What I'm looking for is a method to delay DHCP until the wireless adapter has authenticated.
Any insights?
|
|
|
| |
|
|
|
|
|
|
|
Administrator  Join Date: Apr 2001
Location: San Antonio TX USA
Status:
Offline
|
|
Doesn't authentication have to be related to the adapter? How can the adapter be identified if it doesn't get an IP address-and thus register its MAC address?
|
Glenn -----OTR/L, MOT, Tx
|
| |
|
|
|
|
|
|
|
Dedicated MacNNer
Join Date: Aug 2002
Status:
Offline
|
|
ahh good point. I wonder why the adapter is assigning itself an address then, it must not be seeing the AP at first. If you give it the 5 minutes, it'll fix itself automatically.
Could it be related to the zeroconf stuff?
|
|
|
| |
|
|
|
|
|
|
|
Administrator Join Date: Apr 2001
Location: San Antonio TX USA
Status:
Offline
|
|
More likely it's just being slow. How's that computer's signal strength? Does the user get good speeds once he's connected?
|
Glenn -----OTR/L, MOT, Tx
|
| |
|
|
|
|
|
|
|
Dedicated MacNNer
Join Date: Aug 2002
Status:
Offline
|
|
I think everything is fine once he's connected. There's another MacBook Pro user who has no issues. I would poke around on the Mac itself more, but the upper management here is lame and doesn't want me "wasting time" on it.
I'm going to pick up a MacBook for myself as soon as Leopard ships so I guess I'll experiment more when I have my own machine.
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
 
|
|
|
Forum Rules
|
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|
Top