I've been searching for this problem on Experts Exchange and found several ways to clean printer drivers and registry, but somehow my situation is different because the problem remains..
I've got a printserver with 3 shared HP Color Laserjets 2600n. On the clients (windows xp sp2) I connect the printers via the UNC path (\\server\printershare). Pretty normal I would say.
When the pc user tries to print, the job comes in the queue and stays there saying it's printing. When I login using an account that has never logged on that pc before the printer works (Normally when you login with an account that doesn't have a local profile on that pc yet, it will be created with a new 'default profile'), and the job will be printed.
I can't find the reason why the profile of the user is not working, and when I have a new (default profile) it works.
I've tried to clean the entire pc with the procedure from Bruce Sanderson (registry cleaned, and using the CLEANSPL.EXE from the resource kit), but it looks like it must be somewhere in the userprofile.
When the job is in status 'printing', and I stop and start the printspooler on the server, the job will be printed...
Does anyone know if there is anything in the profile that can cause this ? We have about 20-30 users that use these printers, so deleting all profiles is not an option (we would need to rebuild all profiles, exchange accounts, etc..)
Thanx for you help !