802.1x PCs won't get IP addresses

[jamesfed]

Hi all,

 

Until now we have been using WPA2-PSK for our wireless keys with each user being assigned an individual key to their notebook.

 

Recently however we have deployed WPA2-802.1x provided by Windows Server 2008 NPS to allow computers to join the sites Wi-Fi using the machine credentials.

 

Many computers connect perfectly however a number (and it appears to be randomly affecting notebook of all manufactures and OSes (XP/7)) fail to obtain a IP address from DHCP and end up with a local IP address (e.g. 192.168.*.*).

 

The machines appear to be authenticating correctly as they appear as success messages in the NPS logs.

 

All PCs have been told to obtain IP addresses form DHCP with no statically assigned IP/DNS settings on the affected PCs.

 

Our conventional WPA2-PSK wireless appears to be working normally.

 

An example of the error message that I see on one of the PCs that is affected would be-

‘Your computer has automatically configured the IP address for the Network Card with network address xxxxx. The IP address being used is 169.254.161.168.’

 

Any help or pointers would be greatly appreciated

 

Thanks!

[accura2000]

Check your DNS settings/sevrer is working correctly as this can sometimes stop machine getting IP addresses and also, my XP clients had a similar problem until i turned WPA2 AES off and used WPA2 TKIP.

[jamesfed]

Just tried changing over to TKIP and did a ipconfig /renew and by chance saw a new error message-

 

'An error occourred while renewing interface Wireless Network Connection : unable to contact your DHCP server. Request has timed out.'

Edited December 6, 2010 by jamesfed