Slow xp logon

Status
Not open for further replies.
There is a ceritifcate issue with Windows 2000 Active Directory and Windows XP Sp1+.

It is to with the default certificate communication settings in AD causing an issue with the default communication settings in XP SP1, this issue is easily resolved.

The symptons are extemely slow logins etc. This issue only effects Windows 2000 AD and XP SP1+ clients, if this is the issue you are having let me know and I will look up the setting changes required on the server to fix.

Thanks

Lee
 
Yes, I'm having slow logins. As I said in my post, I've solved (kind of) the issue hard-coding the ip address of the ad server in the "dns servers" section of the lan connection.

I suppose I have a misconfigured dhcp server, or maybe it's because of the issue you are talking about.

I'd like very much to have further information about the issue you mentioned because we are starting to have more and more xp sp2 clients.
 
Hi,

This issue is specifically between Windows 2000 AD and Windows XP SP1+

In the Default Domain Controllers GPO > Computer Configuration > Windows Settings > Security Settings > Security Options > Explicitly disable all Digitally sign client and server options (4 of them).

I stress this is a very specific fix.

Thanks

Lee
 
Misconfigured dhcp

The DNS servers listed in my DHCP server were in the wrong order: the first two were the external ones, and the AD server was the last one.

Moving the AD server's ip address as first solved the issue.

The security settings you mention have the value "undefined" in my setup.

I don't want to break things, so I won't touch them until everything works fine...

Thanks anyway, I'll keep this thread in my "tips'n'tricks" repository should need arise.
 
Hi,

no problem as I said this fix is for a very specific set of circumstances.

DNS is critical in AD so it can cause all sorts of problems.

Cheers

Lee
 
Slow XP Logon Sony Vaio Wireless Adapter

I'm bringing this thread back, as I just spent way too much time working on this issue myself and just found this thread. Going way back to the original post, the user at my company has a Vaio laptop with Xp Pro and the Intel Pro Wireless 2200BG adapter.
Computer would boot fine to the logon screen, but after entering the username and password would take 2-3 minutes to move on and continue booting. Would do this whether it was connected to the domain or not. For the life of me, couldn't figure it out. Triple checked my DNS, DHCP, etc. Removed the PC from the domain and added back. Tried some reg hacks I found articles on related to the slow logon subject. It was crazy I tell you. No other user or laptop experiencing this issue.
But, today I find this and my frustration is gone. Never played with the wireless. The wireless adapter actually had the switch set to off, and was only booting while connected via wire to domain. If I disabled the wireless adapter, all booted up fine. Amazing! So how to enable and still boot normally? Using the Windows Wireless advanced tab and set it to only connected in infrastructure mode. No ad-hoc. And it works like a charm. How stupid is that?
I'm done with it at this point, although I am curious as to what the real conflict/issue is when the wireless adapter is set to allow ad-hoc wireless connection that causes the 2-3 minute delay and why others do not have this issue. Anyway, I'm happy.
This goes to show, that although many times it is DNS, it is not always.
 
Wireless networking was the problem.

All
I had the same problem recently and this forum help me solve the problem.

This problem normally appears if I am trying to login to a network that is not my home domain. Ie When I take my laptop home from work.
The rule is if you are logging into a cached profile then you must not physically be connected to any network during the logon process. Otherwise XP goes looking for a non existent domain controller and takes several minutes before it gives up.

Now to the problem
I was doing as I said above but was still getting the logon hanging even though wireless was off ( at the switch ) and no ethernet connected.
I had recently been playing with computer to computer networking and the wireless driver was still trying connect even though it was physically off.

The fix was to login with local admin rights
delete all computer to computer connects in the advanced wireless networking tab( leave normal wireless connections alone )

disable and renable the wireless device and the laptop was all happy again.
 
I also just had this issue and this helped me fix it. If wireless card is enabled with Windows, even if the Wireless adaptor is switched off (i.e. in our case on Dell laptops, you can press Fn F2 to switch it off), the 2-3 minutes of hanging during the logon process occurs.

Disabling the wireless card through Windows fixes the issue and logon occurs instantly. We went so far as to create a VB application which disables users' wireless cards at boot up and also a group policy which sets the "Wireless Zero Configuration" service to manual so no one gets this issue. If they need to use wireless, once Windows has loaded, they can right click on a system tray app, choose connect to wireless network and it then disables ethernet card, enables wireless card and starts the "Wireless Zero Configuration" service. This has fixed the slow boot up and logon problem for all our laptops.

Many thanks!
 
I am having the exact same issue that was originally posted. It's definitely a Wireless card issue, confirmed several times.

Those people that said to rename the Active Directory domain to .local clearly have no knowledge of how DNS works, that was a mere fluke that it actually worked for anybody. I shudder to think how much time would be wasted doing that at even a small 10 PC shop, let alone 1700 where I work.

Anyway, back to the wireless issue. Does anybody know what causes this? I have tried all of the methods posted which allows you to leave it on and it doesn't work for me. The issue only goes away for me if the wireless is completely disabled. This works on a Dell D620 and D630 which I have been testing.

The interesting thing for me though, is that this issue only seems to occur if the laptop is imaged using our Unified image with SMS. But if Windows is installed from scratch and manually brought up to the same config as the image, the issue does not occur.

I have yet to find a way to make the wireless work while having a quick login time, however, at least we now know that disabling the wireless device fixes the issue.
 
Interesting you say if you install Windows manually, it doesn't have the issue. I don't work on the build team so haven't a chance to try this out but do you think it could be anything to do with Sysprep running on a machine? Just a thought since I would have thought most people getting this issue in companies build their machines from images...
 
I thought about that actually, it seems possible, considering that ends up being the only difference once the laptops are brought up to the standard config when they're built from scratch. The thing is, that doesn't make any sense, Sysprep isn't really doing that much, just changing the SID on the machine and re-installing drivers.

I'm thinking that it might be more likely that the Sysprep is simply accelerating whatever is happening in the background that causes this issue. I guess the next logical step would be to build a machine from scratch and just Sysprep it to see what happens. When I get some extra time I'll work on that.
 
Yup, fair enough - as i said, just a thought! Unfortunately I can't test this myself but if anyone else can and finds out the result, I'd be interested to know!

Many thanks!
 
I wanted to post my experience here. I'm with the IT department of the company I work for. One of the users was experiencing about a three minute delay after logging in (post username and password). The screen would go to the blue background and you could move the mouse around as it would wait about three minutes before it would get to the login script and show the icons.

Just on a hunch, one of the first things I did was disable the wireless network card via the device manager, and that resolved the situation. I wasn’t going to leave his laptop like this, but it did isolate the problem down to the (built in) wireless card. I now knew it was either the physical hardware or a software component of the wireless. I turned off the wireless / Bluetooth via the button on the laptop, which did nothing to alleviate the problem. This led me to conclude it wasn't the hardware. Figuring it was something software related (corruption of the driver, etc), I uninstalled the built in wireless driver, and reinstalled it. Now it runs like a champ. Everything is working and login time is about six to ten seconds.

Hope this helps anyone that might still be experiencing this problem.
 
Speedy71 said:
Guys,

Im a tech at a large security company in Australia. I've been reading all of your posts and we seem to have the same problem, I myself have had the issue on my IBM Thinkpad T40 and now the issue is happening on our new Dell D610's.

The issue, just to recap is that once we logg a user onto our 2000 AD network all seems ok, then, you basicly unplug the laptop's LAN connection and try logging into it using the cached domain account, you get as far as the background loads and the mouse is available, but no icons, no start bar, nothing. I've actually left it for about 2 hours with no errors.

I then powered the laptop off and started it again not plugged into our LAN and it sometimes let's me log into the pc.

A solution that may work which I have not tested as yet, but thought I might throw up on the forum to see if any of you can try it to see if it resolves your issues. Is to: Disable the "WebClient" Service, I was told today by one of our techs that, thit, resolved a similiar issue in our Queensland operation.

This may be all we need to do, Ill get the chance to test today, and if my findings work I will post them... if not.. ill post that too.

Cheers all

Speedy71 :bounce:
Click to expand...
I have had a similar problem with logging onto an XP machine that has been physically disconnected from a network. It reaches the desktop picture and hangs for a few minutes waiting for icons and the task bar to appear. I found that it was manually mapped network drives that try to reconnect when logging in -- it cannot find the network resource and hangs waiting for a response from something that isn't there. If you disconnect the machine from the network and wait until the desktop does appear (after restarting and logging in) the manually mapped network drives will be the only ones left (assuming you are using a log-in script of some kind). Delete these.

On another note, I am currently experiencing same trouble with the windows logging in screen taking 3 minutes to authenticate. I have been told it is something to do with SMB digital signing but have not checked it out yet.

XP clients.
Server 2003.
 
wireless card dilemnas

I had the same problem with several laptops around the office; 2-3 minutes from login to desktop. I disabled the wireless card and login went down to the normal 10 seconds. I then found and changed the network access in the windows wireless network connection properties advanced window to infrastructure only and re-enabled the wireless card and all was well. Thanks for all the help!
 
This is the SOLUTION I found

HI all.
After getting crazy for fours months here the solution to save you some pain.

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.
 
Disabling the Wireless adapter through Windows (by simply right clicking and choosing disable) solved my issue with a Toshiba laptop that was experiencing this problem.

I also removed many of the cached wireless connections (over 40) and it logged in to Windows in less than 10 seconds.

Thanks for your help, as I had tried numerous registry hacks, Windows re-installs, driver updates, DNS entries, etc...without any luck.
 
WINS caused problem for me

WINS was my main issue and removing that caused the login slowness to disappear. Basically the DHCP service we had, was out of date and removing the offending WINS entry caused everything to speed up to the same speed as a local account login.

I also removed the machine from the domain and rejoined but I'm pretty sure that WINS was the cause and not leaving and rejoining the domain.

BTW my domain was already .local - just FYI.
 
XP Slow Logon

I had the exact same problem with a user. If I logged in as her, it was painfully slow. If I logged in as me, it was very fast. After trying all the tricks, and tweakes, I saw someone had come up with wireless card problem. When I went and look, my users had 15 different wireless networks that the laptop was looking for, before if would log in. Set to look for infrastructure only, and Bang...problem solved.
Thanks to all that posted for the help.
 
Hi all, I had the same problem wit slow logon on XP and disabling the wireless card worked for me. After that also the Cisco VPN client was again able to start before login. Two issues solved with such a simple solution! Computer is a hp laptop. Many thanks for all the great tips here. Headache is gone :)
 
same here but no wireless adapter

Hi all. I have the same delay problem on a tower pc in a domain since I installed a new domain controller to replace the existing one. When the user on this particular machine logs on the login window disapear and the wallpaper and mouse are the only things around for 40 seconds precisely. After many attempts I realised that by disabling the "Plug and Play" service the 40 seconds are gone. So I enabled the service again and disconnected the usb connection of the phone (for address book) and the logon was now delayed of only 5-10 seconds. I post here because when I ran BootVis this 40 seconds lap was pointed to a "Network Delay" showing 3 files as delaying the boot process. Unfortunately for me this computer has no wireless adapter and the domain is a .local and the dns works fine (server side) and the mapped drives are all working and there is no WINS server and it's a windows 2003 domain controller working in mixed 2000 mode (there is another domain in the same network which has a windows 2000 domain controller).

I have run ipconfig /flushdns but maybe there are other old junk to clean but I don't know where and how to, do you have any thoughts? Thanks.

PS for the ones with wireless you can change the priority order of use of your network adapters in the settings of the windows where you can see all your network connections under windows xp. in some cases it solves the slow logon because it will directly try with cable.
 
What worked for me

I was going crazy with the slow login process problem, and here is what finally worked for me. I went in and saw that the user having the problem had more than 10 wireless networks that he had attached to and they were all set to automatically connect. I deleted all but one wireless connection (which was his main home wireless connection), and then shutdown and restarted. Login time went down to 20 seconds from beginning to end. This is what finally worked for me, so here's hoping it helps others out there. Cheers!
 
Status
Not open for further replies.

Similar threads

A
LinkedIn accounts targeted in worldwide hijacking campaign
Replies
2
Views
407
netman
netman
midian182
  • Locked
Google sues alleged crypto scammers who uploaded fraudulent apps to the Play Store
Replies
24
Views
245
emmzo
E
A
Google OAuth secrets exposed as account-hijacking MultiLogin vulnerability discovered
Replies
4
Views
251
Jme Kerul
J

Latest posts

Back