WPA PSK

[Fighting Scot]

I'm having problems connecting to a Cisco 1130 AG wireless access point while
using WPA PSK. Our computers running Windows XP Professional SP2 can't
acquire a network address when trying to connect to the access point. I have
no problem with Vista. They connect very well. I'm using TKIP and AES
encryption. I have the same problem at
home with a Dlink wireless router configured for WPA PSK.

Thanks

 

[Jack \(MVP-Networking\).]

Hi
Assuming that the Wireless cards in the WinXP computers support the security
mode that you want to use.
Apply this patch to the WinXP computers,
http://support.microsoft.com/kb/893357
Jack (MVP-Networking).

 

[ANONYMOUS]

See if this article helps:

http://www.microsoft.com/windowsxp/using/networking/expert/bowman_03july28.mspx

Or this one:

http://www.wi-fiplanet.com/tutorials/article.php/3552826

hope this helps.

 

[Fighting Scot]

I appreciate your help, but the hotfix didn't solve the problem. Symantec
EndPoint Security installs a driver named teefer2 in the network connections.
I found that if I uncheck this driver for the wireless connection my problem
disappears. It isn't an issue until you wish to use WPA security.

 

[Barb Bowman]

that definitely sounds like something that needs to be fixed by
Symantec. have you contacted them?

I appreciate your help, but the hotfix didn't solve the problem. Symantec
EndPoint Security installs a driver named teefer2 in the network connections.
I found that if I uncheck this driver for the wireless connection my problem
disappears. It isn't an issue until you wish to use WPA security.

--

Barb Bowman
MS-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

 

[KB]

Have same issue with Teefer2 when bound to WiFi adapters (Intel 2915,
3935, D-Link DWL-AG660 & D-Link DWA-642) on two AP's using any encryption
std. Adapter only retrieves IP address no encryption. Came accross issues
with same (Teefer2) service with IPSec connectivity.
Teefer2 handing-off packets to Sym. Firewall. Removing this binding isn't
a feasible workaround for me. Out end-users are remote. This (of all
connections) is the most vulnerable.
Agreed, Symantec needs to address this. Looks like a few months have gone
by with no apparent resolution.
Enabling Windows Firewall on this adapter per article in
http://www.wi-fiplanet.com/tutorials/article.php/3552826
is the workaround I'm using. If anyone has any other ideas, I'm open to the.

Tnx,
KB