Domain Upgrade - Printing Slow

I am upgrading my users from a peer-to-peer network to a Windows 2003 domain enviornment.  I have an HP Laserjet 4250 network printer on the LAN that several users print large documents to.

Normally, users sending jobs to this printer find it very fast to spool and print.  Now, after joining the domain, they find the same print jobs take several minutes (5 or 10 or more minutes) to spool and print.

I can log into the computer locally and print a job without a problem.  I can then log into the same machine with domain authentication and the same print job can take 5 or six time longer to print.

Any ideas?

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Is this printer on a server and then shared out to the workstations?  If it isn't, try giving that a shot.  Also, I have noticed that the HP laser printers using the PCL6 driver will print significantly slower at times.  Try using the PCL5 driver, that should fix your problem.
very odd situation, i am wondering if you have the printer published in AD.

how do you have the printer networked? internal NIC or installed locall on the server and shared?

check printer properties and make sure the printer is published in AD
BillBrosiusAuthor Commented:
The printer has an internal nic and is using the printer software to facilitate sharing on the network.  It would not be possible to physically connect the printer to another computer to share.  The printer has no feature for adding it to our domain.  Can I still make it a domain object in AD?  Is that what you are referring to when you say "publish in AD"?  I have added the printer hostname to our DNS that serves our AD and that didn't help.

Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

where is the printer software installed, is it locally on a machine on the network or is it 100% standalone?
BillBrosiusAuthor Commented:
The printer software gets installed to the local machine when they are configured for the printer.
you might want to try and install the software on the server and then from there, share the printer out on your net and make sure its published in ad

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
BillBrosiusAuthor Commented:
Trying that now.
you just have to check on the actual printer properties on the machine that the printer is installed on    there you can publish it, usually it will be by default if installed in a domain environment, but it depends if you installed with a domain account or not
BillBrosiusAuthor Commented:
Ideally the printer would not be "shared" via any computer.  Each user would print to the printer directly.  That is they way it worked before upgrading the user to a domain and it worked fine.  Something changes after the user joins the domain.  Very frustrating!!

Thanks for all the suggestions though.  I am exploring all options.
its shared as its own entity but its must still be installed locally on a machine and therefore shared via that machine, ie, to connect to the printer, you still have to \\servername and then right click and connect, this has to be done, the printer with its own NIC is still its own entity though
BillBrosiusAuthor Commented:
Sharing the printer off a domain member seems to have improved the situation, but it still confuses me as to why it makes a difference.

Thanks guys.
no worries mate, its the way the the machines get published or "installed" in AD, if its an object that AD recognises everything can fly, if not then you start moving out of AD and everything slows down....
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.