Perkdaddy
asked on
Workstations are suddenly taking almost 5-7 minutes to start on SBS network and business domain
Unique issue for me. I have a 50 system business network on a SBS 2003 server. For 6 months everything was great, systems booted and started up very quickly. I keep a strict set of user rules in place for this company and can insure that users have not installed any new programs or altered the workstations in any way. I recently came back from a 2 week vacation to find my systems are taking about 5 minutes to start up, it stays on the screen "applying system settings" for the duration of the start-up. This is a little problematic and probably points to a larger issue at hand. Any ideas?
Server logs check out ok and dont point to anything conclusive.
Note:
All systems are 100% windows updated
All systems are 100% for AV updates and clean from any "known" infections
Server logs check out ok and dont point to anything conclusive.
Note:
All systems are 100% windows updated
All systems are 100% for AV updates and clean from any "known" infections
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Do you have a warning event with ID 4356 in the application log during boot on the computers that have this issue?
ASKER
Ok awesome. I will check all 3 above and get back in a couple min.
ASKER
Ok I think I found it. Out of a random selection of 10 workstations I found 6 are problematic with the boot. On closer inspection I found 5 of those have a mapped network drive. In the application event log I find the following errors on boot.
Event id 1053 USERENV (user or computer name cannot be identified, domain cannot be contacted)
Event id 15 AutoEnrollment (domain cannot be contacted)
Event id 1053 USERENV
Funny thing is the network is fine after I log on, Mapped drive works great and so does ISA
Note: map drive is a vmware drive on a win2003 server OS
2. The boot process experiences the following delays: 2-3 min on initial startup (applying computer settings) and 2-3 minutes during log-in (applying personal settings)
So it seems some kind of network error, where the workstations are not being authorized during login. Any ideas?
Event id 1053 USERENV (user or computer name cannot be identified, domain cannot be contacted)
Event id 15 AutoEnrollment (domain cannot be contacted)
Event id 1053 USERENV
Funny thing is the network is fine after I log on, Mapped drive works great and so does ISA
Note: map drive is a vmware drive on a win2003 server OS
2. The boot process experiences the following delays: 2-3 min on initial startup (applying computer settings) and 2-3 minutes during log-in (applying personal settings)
So it seems some kind of network error, where the workstations are not being authorized during login. Any ideas?
Try to login using different user name (different profile) and see what the result comes. Might be Profile having some issue.
and also you can check your DNS also.
and also you can check your DNS also.
ASKER
I checked the other profiles same thing., It wont authenticate until AFTER fully loading... Very strange. I think it point to a serious bottleneck somewhere... Or I need to purge the DNS by running the SBS netwrok wizard
ASKER
but how would DNS cause login issues
ASKER
How can I check the DNS for problem related to login? this is during start-up, the workstations shouldnt even be contacting the DNS? right or wrong?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I will have a look at this on my SBS box, but surely I know the DHCP is running on this box and on no other device or router. I will purge the DNS after I run the wizard and see if that solves the problem. Thanks for your detailed reply.
The main issue is the client machines may have the ISP as one of their DNS servers. I must be ONLY the SBS.
ASKER
no no no. All client have their ips, gateways, dns defined by the server. I have made sure of this and where the few machines that do have their ip and dns manually entered I used the server IP in the DNS box.
I have completed your checklist above to no avail. This is all SBS wizard things. I'm going to try something else, I will move a system closer to the server (my work bench :) ) and see what happens. If the boot is fine then its a network problem and I will forward this back to those clowns... I will except your answer for point as it is the most in depth and detailed answer I have ever received. lets continue to hash this out. Is there something I can 'run' or analyze to better understand where authentication is failing?
I have completed your checklist above to no avail. This is all SBS wizard things. I'm going to try something else, I will move a system closer to the server (my work bench :) ) and see what happens. If the boot is fine then its a network problem and I will forward this back to those clowns... I will except your answer for point as it is the most in depth and detailed answer I have ever received. lets continue to hash this out. Is there something I can 'run' or analyze to better understand where authentication is failing?
ASKER
Ok I got it... Hardware/device driver error.
2 weeks ago we had an DHCP error becuase of a reset wireless AP. My Asst. Decided to apply static IP's to all computers without first checking what the problem was. All problematic systems had no DNS applied becuase my Asst, thought they didnt need it whilst he was trying to find the DHCP culprit. He found the AP, re-installed and put all systems back on automatic settings, BUT, windows showed the settings empty but the Ethernet card was keeping the settings (so i believe). I uninstalled and re-installed with updated drivers and viola. 1 minute startup times. Thanks for the help
Bad DNS BAD! Go lay down...
2 weeks ago we had an DHCP error becuase of a reset wireless AP. My Asst. Decided to apply static IP's to all computers without first checking what the problem was. All problematic systems had no DNS applied becuase my Asst, thought they didnt need it whilst he was trying to find the DHCP culprit. He found the AP, re-installed and put all systems back on automatic settings, BUT, windows showed the settings empty but the Ethernet card was keeping the settings (so i believe). I uninstalled and re-installed with updated drivers and viola. 1 minute startup times. Thanks for the help
Bad DNS BAD! Go lay down...
ASKER
Split points. Kenmerry was on the right path but Robwill was more in depth an solved the issue. Just trying to be fair...
Glad to hear you were able to resolve.
Thanks Perkdaddy.
Cheers!
--Rob
Thanks Perkdaddy.
Cheers!
--Rob
There might be so many reasons for this.
The main Reason above all
Might be you have mappend any drive & that drive is having some issue (Like that drive is no longer in your network or that drive is having any virus, or that drive is full, etc), causing your Pc to take long to boot, coz mapped drives get mapped at the time of booting.
If so just unmap the drive and check again.