I have a Toshiba Satellite Pro M10 and I'm trying to get it to login wirelessly to our W2K domain. The notebook is running XP Pro. I can get a wireless connection, but I have to do it manually after windows has booted to the desktop. I need to be able to force the wireless card on prior to the login prompt. If anyone can point me in the right direction I would appreciate it. Thanks.

Normally you make a computer in AD then connect the computer. In this respect there is very little difference between wired and wireless. Your issue is not that of a domain but a wireless config. How is it that you force the wireless card on? It should be issued an ip from the server shouldn't it? Do you get an ip fromt the access point/wireless router?

I did add the laptop to the domain/AD, and it works fine when plugged into the LAN via ethernet. When windows boots up to the desktop, the wireless icon has the red X (in the systray) indicating that it isn't connected to the network. I then have to click on the icon and tell it to connect. It doesn't connect automatically. Because of this, whenever you boot the computer up to the login prompt, the wireless adapter is still not connected - therefore it can't process the login, map network drives, etc. I have tried both DHCP from our server, as well as static addressing on the wireless adapter. I didn't think about the wireless router being able to hand out it's own IP - this might be where I need to be looking. I guess what I'm trying to accomplish is make the wireless adapter connect to the network prior to logging in - that way it's able to process the login request and map the network drives, etc.. Does this make sense? I'm not always the best at explaining things. I do appreciate you taking the time to help. Thanks a bunch.

The following info might help: http://www.velocityreviews.com/foru... http://support.microsoft.com/?id=31...

Thank you very much for the info. I'm looking into it right now even :)