Computer [on domain] 'Hangs' during bootup

We have a PC in our office that runs Windows XP SP2 with all the patches. We log into a domain as part of the boot process. A screen appears showing our drives we're attached to. That requires an 'OK' button to proceed. Then the systems seems to hang - the background comes up on the monitor but no icons, task bar, etc ever appear. The workaround at this time is a reboot.

I was told by a fellow techie that being connected to HP printers can sometimes cause this issue, that the printer drivers can be problematic. Perhaps this is so, but the problem started only recently on this particular PC that has been 'rebuilt' software-wise. I'm connected to the same printer - as are others in the office - and we don't have the same problem. The printer involved is a networked HP3800 color laserjet.

I'm thinking it's probably NOT the printer drivers causing the problem but I'd appreciate input from anyone else with possible causes. Thanks!

 

Hanging on boot (domain login)

We don't use roaming profiles. I don't think it's the script either or it should be affecting the same way no matter which PC the person logs on to. And as I mentioned, it seemed to have started when the 'new' PC was put into place. And as I forgot to mention, it happens for anyone who logs in to that machine (we have users in a group with appropriate permissions to do so).

 

If you think it might be the printer you try installing the drivers directly from the driver CD onto that computer (normally it would get the drivers from the server).

Check the drivers for the LAN/ethernet adapter. It may even be in the cables or connections.

Does it have the problem from a "cold" start, then work OK when it is rebooted? That might indicate a hardware resources problem with the LAN adapter. If you have another adapter, remove or disable the current one in the BIOS settings and try the other.

Matt

 

Personally I would check that script. It is the most obvious starting point. Sure it might not be the cause, but discounting it just because the script works on other PCs is not a good way forward. There may well be something peculiar to this computer that causes a problem with the script.

Have you tried running your log-on scripts after log in to see if you get any errors then?

One problem I have seen that gives unexpected problems is if someone has manually mapped a drive that clashes with a drive a log-on script is trying to create. My experience is that this is not gracefully handled by many log-on scripts.

This is an example of a log-on script error that can occur on one PC in spite of all other PC using the script without error. There will be more.