Discussion Locked

SBS 2003 Logon/logoff takes a long time

0 helpful
14 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Logging onto and off of my SBS 2003 server takes a long time. Having checked my event logs I did not find any event that would indicate why the long delay. I usually run the server without a keyboard, mouse, or monitor and log on using Remote Desktops mmc. I tried connecting a monitor and keyboard and noticed the same delay logging on locally. I plan to implement Microsoft article ID 325376, but as of yet have not. Does anybody have any ideas of how resolve or troubleshoot this problem?

-Andy

14 replies

by 3xp3rt

It's only a suggestion: your hardware configuration and amount of RAM isn't low?
My Windows 2003 SBS server?s hardware configuration is dual Intel Xeon 2.8 GHz processor, 2 GB RAM on Intel MB and my storage controller is an Intel SCSA raid controller on PCI. So I never meet your problem on remote login and logout.

by andy

Poster rated this answer.
System has been fine up till now. Specs are within MS recommended specs.

by icb's corner

When you shut down the server, the services going to stop and they make that in order because there are dependent one on another. If the server is Exchange then shut down last longer because it performs much operations to close the services.
I don't know if its a good idea to rush this process. I think that Microsoft Id 325376 can give a clue of what server does.

by andy

Poster rated this answer.
Im not shutting the system down, just logging on and off.

by andy

Off hand I don't have the system specs but they are above microsoft recomended specs. I am not shutting the system just loggin on and logging off. This issue just started within the past couple of weeks. The system has been in operation for around 3 months. This morning I logged onto the system it took around 1 hour for me to get a desktop.

by andy

Poster rated this answer.
Checked my version of the Rdpdr.sys file and I have v5.2.3790.1830 which is later version than the fix. Also my delay in logging is present if I log in at the console or remotely. I scanned my security event logs during the timeframe I performed a logon and did not notice anything that struck me as strange. Maybe I am not auditing enough info to get a log of my problem. What do you recommend I audit? Is there a log file somewhere else that I should be looking at?

by andy

Having taken the steps in 325376 I now have a new message during the login process. The message states "executing wlnotify.dll" I will have that message for around 10 minutes then it dissappears. After that I have a blank blue screen for another 10 minutes or longer till the desktop appears. In my testing I logged on once remotely, while still logged on I started another terminal session and logged in with the same user account. The 2nd login happened in mere seconds. But logging off of the 2nd login is taking several minutes.

by curlergirl

Have you scanned this server for adware/malware/spyware and viruses? This sounds suspiciously like something is hogging all the memory or redirecting your server's communication somehow.

Hope this helps!

by andy

Poster rated this answer.
Ran a scan today of the system and it came up clean.

by cg it

winnotify.dll is a Windows library file that handles Winlogon and is required for logon/logoff.

long log on times can be a multitude of items especially if your remoting in from the internet throught routers and firewalls [which you don't mention].

Without any other information, suggesting other ideas is just going to get them rejected.

by andy

Poster rated this answer.
Poster rated this answer.
I am not going passing thru any firewalls or routers. The server is on the same LAN as my workstation. I have another server on the same segment as the problem server. Logons to the good server happen at acceptable pack. This issue occurs even if I logon on locally at the server its self. The server specs are 1.13 ghz with 1gb of ram. I have been using the server for the past 3-4 months and have not had a problem till recently. I first noticed the problem on Aug 19th when I was wanting to check event logs. The only software installed on the machine is the default SBS standard software and WSUS. Per my firewall logs the only outgoing packets are for WSUS getting updates. The machine is not accessabile via the internet. The only change that I have made on the server since its introduction is to add an HP Business Inkjet 1100 series and a HP Laserjet 1100. Both printers are on the network via jetdirects. The inkjet has a built in jetdirect and the laserjet is using a jetdirect 170x. I receive daily reports of of system processes based on top 5 memory and CPU usage. These reports have been consistent since building the machine. I have manually scanned running processes and services and have not noticed any new items. Once logged in the system response time is the same as it has been prior to the long log in times occuring. The only issue with the machine is logging on and logging off wether I am at the machine locally or using remote desktop the long log in and log off times are present. I only have two accounts in the domain that can perform a log in to the machine. Only I have access to these two accounts the issue is present on both accounts. Please let me know if you need any more information.

As this webpage will not allow me to post a comment with out first accepting or rejecting the answer you are correct in that I will be rejecting answers so that I may still continue to receive answers to the question.

by mstrmir

I have the same issue and i'm struggling to resolve it.

the server takes 6 minutes to log off and 20 minutes to restart or shutdown.

this happens to me after updating HP system drivers and application

I have been looking for the answer like crazy for two months now with HP Technical support and Microsoft.

the last thing I got is the network card driver has confliction updates
also, this suggested by microsoft
http://support.microsoft.com/kb/827610

I wish you could help with this if you resloved it so far.

thanks

This discussion is closed to new replies.