Search results for query: *

It sounds like you have a computer account issue, read this article in Microsoft Technet (Q150298). If you have renamed both of your DC's, you may have an a real problem, but I think that you can fix this using the procedures outlined in the document I mentioned.

First, check your print drivers, you may have one that is corrupt. Check any IP printers, one may be unavailable, and hanging the system. Best solution, move the printers off of the Terminal Server to another Win 2000 box, NOT NT! Moving the printers is the best solution...

If your local DNS servers resolve to public addresses try pointing them there, or better yet, use the DNS from a known good client. If they are remote to your site, and other clients come in fine, then routing is not the issue (Or it would be a global issue). Do the clients with issues have...

You need a Serial Cradle. Next you need a USB to serial converter (yes they exist $20 or so). Then use a script to map the serial port on the client to the "new" serial port on the client system. You'll know that the device works when you see a serial port beneath the USB root hub...

If you want to boot straight to a desktop, get them thin clients, and re-issue the "real" computers to users who need them. Criminal waste of resources not to.... -Just my opinion

Sounds to me like your users have very large user profiles. Check things like IE Cache, My Documents, files on the desktop etc. The smaller the profile, the quicker the session will launch.

Map the serial connection to the client.