• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3767
  • Last Modified:

Test Page failed to Print

I have a strange printing situation.  I have one computer that has been working just fine with network printers until yesterday.  Every time they try to print a test page, they get Test Page failed to Print, would you like to use the troubleshooter.  

Of course this provides no assistance.  So, I went to the server first and check to make sure the spooler was running and it was.  No jobs were in the queue.  Then I asked the other people who use these printers if they are working.  They all are doing fine.  So, this machine has a local printer which works just great!  Thus the local spooler is working.

I thought it could be a profile issue, so I logged onto the computer installed the network printer and same problem.

The server is an NT 4.0 SP6a installed, all clients are XP PRO with SP2 and all updates applied.

I can fix the problem in 10 to 15 minutes.  All files are stored on the server and I can shoot down an image of the machine, setup email and they are ready to go which is what I'm just about ready to do.

But before this happens, just wanted to see if anyone else has run across this situation before.

  • 2
1 Solution
Hi dgore1,

only time i have seen anything like it is when permissions on the printer itself went skewiff, ie, the user no longer has permissions on the printer itself


or of course the firewall blocks traffic, can you ping the printer?
You never know; try a different patch cable and/or check the pins within the keystone jacks. Check on the nic card itself.
dgore1Author Commented:
Jay Jay70 got the closest to the real problem but I awarded the points since that got me looking into something I should have known:

The problem:  NT 4.0 printer drivers with new printers and XP Pro workstations.  I have come across this time and time again.  Sometimes, the NT 4.0 server will not load the correct printer drivers.  To do this, you must first install the drivers on the local XP machine.  Set this up as a Standard TCP\IP printer, just as if this was a print server.  Then you access the NT 4.0 server, point the new print driver that you have begun to create on the server to \\workstationname\printerlocation to load the true XP driver up to the NT 4.0 server....works every time.

What threw me here was they were working and suddenly stopped.  The permissions for only this machine, weird, and the drivers were corrupt.

Thanks to all and hopefully, we will go to 2003 soon since that solves all the problems in our case.


Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now