What I mean is when you are trying to connect to a network with a username and password it logs you on with a local profile and not to the network, so it doesn't map any network drives, but once logged on with the local profile the wireless then makes it's connection.
So far nobody's had much luck getting XP synchronous login to work with wireless, but here's
Microsoft's article on disabling XP's "Fast Login Optimization" feature. The problems may have to do with whether XP or the client wireless software is managing the connection. If XP gets the connection established before login, the domain login should work. At least one wireless vendor, Broadcom if I recall correctly, has a feature that starts the connection sooner. Beware that - people have had to recover their machines after enabling it!
As I said, it's not clear that enabling synchronous login will fix the problem.
What the Microsoft article doesn't say is how to start the Group Policy Editor. That's done with
Start/Run gpedit.msc
In the Group Policy Editor window, expand Computer Configuration\Administrative Templates\System\Logon.
Double-click
Always wait for the network at computer startup and logon, select Enabled and click Ok.
Exit the Local Computer Policy management console.
volcano11
2 Intern
•
28K Posts
0
December 3rd, 2004 19:00
Steve
jorad
3 Posts
0
December 6th, 2004 06:00
jwatt
4.4K Posts
0
December 6th, 2004 16:00
So far nobody's had much luck getting XP synchronous login to work with wireless, but here's Microsoft's article on disabling XP's "Fast Login Optimization" feature. The problems may have to do with whether XP or the client wireless software is managing the connection. If XP gets the connection established before login, the domain login should work. At least one wireless vendor, Broadcom if I recall correctly, has a feature that starts the connection sooner. Beware that - people have had to recover their machines after enabling it!
Jim
jorad
3 Posts
0
December 8th, 2004 06:00
jwatt
4.4K Posts
0
December 8th, 2004 06:00
As I said, it's not clear that enabling synchronous login will fix the problem.
What the Microsoft article doesn't say is how to start the Group Policy Editor. That's done with Start/Run gpedit.msc
In the Group Policy Editor window, expand Computer Configuration\Administrative Templates\System\Logon.
Double-click Always wait for the network at computer startup and logon, select Enabled and click Ok.
Exit the Local Computer Policy management console.
Jim