WinXP Wireless Connection always has to reconnect at user Logon

[winterwendigo]

I have a Desktop with a wireless card to make it moble. Whenever any user logs on to it is not connected to the network or the domain because it is trying to acquire an IP address. After then ip address is acquired and you log off and log back on it does the same thing it tries to reconnect to the network. This of course makes it very difficult to any other user to log on that has not already logged on because it can not authenicate them to the network without a connection. I looked on the Microsoft KB and it talked about some dll file that deals with encryption but it was for Win2K and I am dealing with WinXP Pro SP2. Here is the Link

http://support.microsoft.com/default.aspx?scid=kb;en-us;244671

would this be the only way of fixing this short of formatting the HD and startring from scratch?

 

[PoliMalaka]

W2K and XP both cache passwords by default.
Has this configuration been changed to disable this?

 

[winterwendigo]

Do you mean the encryption passwords to gain access to the wireless network? If so I am not have to put those passwords in everytime I log on to the machine. It just seems like it disables the network connection everytime a user account is logged off. As though during the closing network connections stage of logging off it is totally dropping itself off the network which would keep it from authenticating any user that has not logged on to that machine

 

[PoliMalaka]

I am referring to the network credentials on your domain.
What is the "middle ware" you are using for encryption? From what i understand it has its own set of credentials correct?
We use Funk Odyssey Server to authenticate. It has an option to use the Windows username and password.

 

[winterwendigo]

I hate to admit to this but I don't know what middle ware we are using, I know that we are using 64bit encryption. Could you tell me how to find out what we are using?

I have all the rights to find out on the network.

 

[paulha]

We had a similar problem with laptops being unable to log on to the network due to the card not initialising prior to the user logging on. Some cards worked ok, some didnt. We basically got round it by rolling out laptops with built in wireless.

However, moving on a bit closer to your problem, we had to put wireless onto a desktop due to lack of ports in the office (!), works fine. You might want to buy one to try out, Belkin PCI card 802.11b 2.4GHz 11Mbps F5D6001uk

 

[ADB100]

It is possible you have 802.1x EAP Authentication enabled on your Wireless Access Points that require the user to authenticate before giving them access to the network. With Windows 2000 & XP you can enable Machine Authentication where your domain member computers authenticate themselves as well as the user:

http://support.microsoft.com/kb/318750/EN-US/

http://www.cisco.com/en/US/products...s_configuration_example09186a00801df0ea.shtml

Good luck

Andy

 

[kmcferrin]

It's going to depend upon how your access points are secured. We're using Cisco Access Control Server and Protected EAP (as suggested previously). In the wireless network configuration on our wireless laptops, there is an option to allow the machine to authenticate to the network using the machine's AD account before a user logs in. That way users who do not have cached credentials can log in, but once they do it switches from the machine's credentials to the users for authentication to the access points.

 

[winterwendigo]

Thanks for the info guys I appreicate the time you all took to help me out.

God Bless you