Question : Getting "The print spooler service is not running" Win2k3 domain, XP Boxes

Server:
Windows 2003 AD, Exchange 2003, Symantec Ent. 10, Backup Exec 10, Print Server.  PLENTY OF HDD SPACE, PLENTY OF RAM.
Workstations:
HP Notebook nx6125 Win XP Pro, fully updated through Microsoft Updates, 1GB RAM, Plenty of Hard Drive space.
HP L2000 WinXP Pro, fully updated, 1GB RAM, Plenty of HDD space.
Users:
All 'Domain Users'
Network:
Gigabit network, CAT6, 4 3COM 3870 Switches Stacked.
In-house users = approx 55
DHCP, DNS
Printers:
2 Konica-Minolta CF3102 with Fiery
2-HP1100, HP1200, HP1300, Lexmark C522, & an unplugged HP4500 (Printer still installed in server)

Problem:  
I have a couple of users who when they print the computer sometimes seems to print but nothing comes out of the printer and sometimes they get an dialog box that states "Your file could not be printed due to an error on \\10.10.1.20\Bizhub CF3102 Second Floor on Ne02:.  There are several possible reasons:"
Checked the spooling service and it is still running.  Starting and stopping service does not help.  Right clicking on the printer under Printers & Faxes gives an error messages that states "The print spooler service is not running".
When this occors I can also no log into that server from that workstation.  If I click on Start -> Run -> \\servername it prompts for a username and password (which it shoudln't do).  At that point I can't log in as the user or as the administrator as it just bounces the box back as if there is an authentication error.
A reboot doesn;t work.

If I could assign 5000 points to this one I would.  

Answer : Getting "The print spooler service is not running" Win2k3 domain, XP Boxes

Check your Event Log (especially the System Log).  Look for errors regarding "trusted connection", "COMPUTERNAME$", or similar things.  Look for these on the server as well as on the client (on the server, it may be in the Active Directory logs).  I bet that the trusted connection is corrupted.  If you see those errors, joing the client to a workgroup and then go to the server (in Active Directory Users & Computers) and reset the client computer account (right-click on account and select "Reset" or whatever) and then join the client back to the domain.

See if this fixes it.

<-=+=->