Net Man

Can you disable the Norton services to see if that's blocking network traffic?

I do have some sort of update on this... I turned on boot logging on all locations. However, it did not give any additional info. I compared a recent lock-up to a normal boot and there were no differences. What we did was ask approx 1/3 of the users to reboot in the afternoon instead of morning. (We have a VERY leaky app that almost requires a daily reboot... Believe me - I don't like it either <grin>) This made our situation MUCH better. ' So, here is my theory to what happens if anyone can share their thoughts... XP BOOT START load kernel & drivers start network discover/connect to domain controller notify Domain Controllers we are online display wallpaper/desktop start login process/control-alt-delete For us, I feel the communication is being interrupted during the discover/connect to domain controller. XP is waiting for some type of confirmation from the DC which never comes and causes a lockup. Any experts care to share their thoughts?

Thanks for the reply. Exactly. No logon box. Before we turned on /SOS, the animated scroll bar would simply stop before the screen would display the login window. Adding the /SOS, it now goes to from text mode to graphics mode but hangs on the blue backgroud with the O/S build infomation. I can create the registry keys from here to enable debugging. Will it create any problems to enable the dump feature on all computers (even ones that don't hang) or should this only be done on a few workstations? Thanks again for your help.

Anyone have any ideas? I'm not looking for a miracle fix but if someone know a way to at least turn on more logging, that would be wonderful.

Long time reader - first time poster. We have approx 250 XP pro machines connected (2 per site) to corporate via T1 WAN link. The machines are rebooted daily (we run some really badly written software that needs the daily housekeeping!) When the WAN link is slow and the machines get rebooted, the computers hang before displaying the logon screen. This has been an issue for a little over 6 months. (Coincided with a big bandwidth web app being deployed over the WAN) I have added the /SOS option to the boot.ini file. The machines get through loading the drivers but display the OS version/SP level but never shows the logon box. I'm not sure if the hang is due to inability to see the WAN (should logon using cache though...) Not having the splash screen lets us see all the drivers are being loaded properly. Event viewer logs a shutdown of the event service then a restart when the machine is power cycled. When it's hung, it does not respond to ping (I don't think we've tried Control-alt-delete yet... I'll do that next lockup <G>) We have an APC web enabled power strip we use to reset them once hung since the machines are in a locked rack at each remote location. My question is this - what can I do to enable more logging to find out what's going on? Does anyone know what I can check? Where to look? I'm kinda at a loss and appreciate ANY help. Sorry for the long-winded email, but I wanted to be as through as possible. Thanks.