This is caused by the asyncronous loading of networking during the boot up process. This speeds up the login process in a stand-alone workstation by allowing the user to log in with cached logon credentials before the network is fully ready.
To disable this "feature" and restore your domain logons to their normal speed, open the MMC and add the group policy snap-in. Under Computer Configuration-->Administrative Templates-->System-->Logon, change "Always wait for the network at computer startup and logon" to ENABLED.
This can be fed to clients via a group policy from a Windows 2000 server by upgrading the standard policy template with the XP policy template. Since this is an XP only command, non-XP systems will ignore it in a domain distributed group policy.
Comments
Comment #1
(Posted by an unknown user) Rating
POtential usefulness is limited as I do not know what MMC is?
Comment #2
(Posted by an unknown user) Rating
Where could I get the XP policy template?
Comment #3
(Posted by an unknown user) Rating
Heay When i find MMC. This is shortcut from ?
Comment #4
(Posted by an unknown user) Rating
I dont know that too
Comment #5
(Posted by an unknown user) Rating
to run the group policy editor : start
un gpedit.msc
enjoy...
nrj45
Comment #6
(Posted by an unknown user) Rating
What is windows? just kidding, great tweek :D
Comment #7
(Posted by marco) Rating
it worked for me - THANKS!
Comment #8
(Posted by an unknown user) Rating
What is MMC? Plz tell in detail. It's not a good way.
Comment #9
(Posted by an unknown user) Rating
Thanks, right to the point. I have the slow log-on only on the recently installed XP computers, the XP computers I put in the domain previously never had the slow log-in issue. I wonder if Microsoft changed the settings with the latest XP installs. I also noticed that the new XP computers wil not allow me to add domain users to thier local computer accounts. The domain will not even show up under the locations, even though domain users can log in.
Comment #10
(Posted by Kalle J) Rating
Very useful indeed. And to those who doesn't know what MMC is, I would strongly discourage you to even touch a computer connected to a domain.
Comment #11
(Posted by an unknown user) Rating
The site is for information exchange. Leave it that way. It's up to the individual to decide what to do with the info.
Comment #12
(Posted by an unknown user) Rating
As someone who knows exctly what you are talking about. I found this very informtive. Thanks! Oh and for the rest of you who don't know what you are doing you probably shouldn't mess with the policy settings on your PC anyways. Especilly on a company PC.
Comment #13
(Posted by an unknown user) Rating
You know it really is amazing how many people in this worls are total asses. At least half of the responses to this post were asking what an MMC is. Subsequent responders who clearly have the answer preferred to bask in the kindergarten glory of - I know but I'm not telling. This is how intelligent computer users copped the name 'nerds' because some of us are social cripples.
The Microsoft Management Console (MMC) allows a user to perform a range of administrative and maintenance tasks easily. You can access this utility by typing MMC in the command line. Click START, and then click RUN. There, you will type the letters MMC.
For an overview goto: http://www.networkclue.com/os/Windows/commands/mmc.aspx
Comment #14
(Posted by an unknown user) Rating
;p-p=[
Comment #15
(Posted by Sam Peter) Rating
HI all.
After getting crazy for fours months here the solution to save you some pain.
http://techrepublic.com.com/5208-11184-0.html?forumID=47&threadID=197152&messageID=2311170
Once I've fould out that the workstation service was slowing the all start up / login process with windows XP.
Here I am posting some considerations.
First the problem appear as a very slow login after typing your passord prior the desktop to appear.
The problem also appeared as an infinite need to repair continuously the connection (right clicking on the wireless icon) or often as inability to
connect wirelessly.
The SOLUTION to the problem "login to XP takes forever" is to remove any other software that manages the wireless card and let only the native Windows
Wireless Zero Configuration to handle it but the problem immediately desappear!!!.
Once you unistall any other software excepts the drivers of the wireless card, you must go on control panel/network
connections/advanced/general/properties/wirelss network and click on Use
Windows to configure my wireless network settings which will anable the native Windows Wireless Zero Configuration.
The problem is probably found in many computer that have the intel centrino chip set which uses the Intel(R) PRO/Wireless 3945ABG Network Connection but
maybe is with any other wireless
card that uses the intel software to manage.
Myself I did also utilize a second D-Link wireless card which was also utilizing its own software to manage and could work with the native Wireless Zero
Configuration) but it turned out because of the Intel(R) PRO/Wireless manager.
Myself just to be safe I unistalled also the D-Link softwarebut is not really necessary.
TWO MORE IMPORTANT Considerations:
THE PROBLEM DID NOT IMMEDIATELY GO AWAY!
1)
I had to reinstall (from an image I had) the entire operating system and then remove the Intel Wirelss manager from it.If I was not removing the Intel SW
the problem after few hours the problem reappeared (I restored the OS from the image like 30 times so I am certain).
For many people the problem will go away immediately just unistalling the wirelss software but that was not my case.
If you do not want to uninstall the operating system.you may go through a procedure to reset entirely the networking in your OS, I know there is a way to
do it but I never researched it.
(Maybe all you need to do is to remove all network conncections by uninsalling all drivers I chose to restart with a new XP)
2)
I utilize 2 wireless cards and I am having a second minor issue:
IF I DISABLE the wireless switch of my Intel card and connect the 2nd one, the pc still says that there are network available on the 1st. In other words
the card is not entirely off. I use a brand new DELL LATITUDE D820. Maybe this is to avoid the Plug&Play procedure.
As result I see two wireless icons on the bottom right when I only want one and altough the external DLINK says that is correctly connected to the
wireless network, Windows still seem to remain internally connected to the Intel one and as result will still be unable to see a webpage.
In order to "connect" Windows to the correct external network card I must click on its repair button (right click on its icon) and then everything is
ok. Maybe this is another bug of the os which wouldn't come as a real surprise.
I hope this all note will be useful to you and save you a lot of time.
Good luck!
PS
If you find on the web that the prefetcher is the problem.. I think it is not true.
Comment #16
(Posted by an unknown user) Rating
Thats great man i want more solutions like this would u mail me these solutions
Comment #17
(Posted by an unknown user) Rating
Don't be a douche bag, the users who don't know what the MMC is should not be messing with it. If being a tech was easy then everyone would be one. How about this is you really want to know get the proper training so you don't create more problems than you solve.
Comment #18
(Posted by an unknown user) Rating
Ha...nerds are funny. Thank god for newschool tech people.
Comment #19
(Posted by an unknown user) Rating
didn't help
Comment #20
(Posted by an unknown user) Rating
WOW you guys that know what MMC is must be really cool. You can mess with servers...and everything.
Comment #21
(Posted by john brown) Rating
This worked for me. The banter over MMC is interesting. I have to agree with those who say that if you don't know what MMC is, don't be messing with the machinery. I agree. Those who don't know what MMC is should at least try Googling the term and picking up a bit of knowledge on their own before whining about how this article does them no good: "This article ain't no good. I dunno wut MMC is an I be too stoopid to even look it up myself. I want someone to do that for me."
Right. MoveOn to the next whine.
Comment #22
(Posted by an unknown user) Rating
Actually, users who don't know how to USE the MMC should not be messing with it. Users who don't know WHAT the MMC is should be TOLD about it. That's how people learn. I suppose you once didn't know anything about it either, then you learned what it was, and only then have you learned how to use it. So please let others learn about it, too. That's a better way to avoid them creating more problems than they solve.
Comment #23
(Posted by an unknown user) Rating
to get this settings type 'gpedit.msc' in run dialog box and press OK
Comment #24
(Posted by an unknown user) Rating
great information. thanks. PEOPLE WHO DONT KNOW WHAT MMC IS SHOULDN'T TOUCH A SERVER!!
Comment #25
(Posted by meghan.nelson@aei.com) Rating
Is there any microsoft documentation on this? This fix worked on a few computers in our domain and in order for our IT department to push this out i need microsoft documentation thanks!
Comment #26
(Posted by bill) Rating
Just buy a MAC.
/Images/icon_Email.gif){kind=icon}
/Images/icon_PrintArticle.gif){kind=icon}
/Images/icon_Favourite.gif){kind=icon}
/Images/icon_ReadLater.gif){kind=icon}
/Images/RateSecA.gif)
/Images/RateSecI.gif)