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

Network Printer/Copier unable to print but can ping

Win2K network with 4 xp pro workstations,network printer/coper that all stations can connect and print to without failure.  One station connects to the server, network printer/copier, etc. with no problems.  When a print job is sent from this station, it spools, ques and disappears from the que as if it has been sent successfully.  No errors.  But nothing ever prints!

All other users print fine.  I have checked all configurations and they are all the same.  Checked AD to assure that rights were all the same, and they are.  All users have same rights within the same container.

To make things even more infuriating, this workstation can ping the printer IP successfully.  The station can ping the printer, see the printer (have reinstalled, have reconfigured port, checked port settings), connect to the network, see all other stations and the server, etc.

What on earth do I try next???  Many thanks in advance!

Bonnye
0
Bonnyeliz
Asked:
Bonnyeliz
  • 4
  • 4
1 Solution
 
Jay_Jay70Commented:
Hi Bonnyeliz,

if nothing is erroring then i would tend to lean towards a problem with the printer.... can you print a test page from the server where the printer is installed?
0
 
LazarusCommented:
Delete the Driver from the Client that has the problem Then delete the spool that belongs to it on that same computer. Reboot, Re-install the Drivers and you should be ok. It looks like you have a corrpt Spoller on your client.
0
 
BonnyelizAuthor Commented:
Hmm... unable to print a test page from the server as well.
0
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 
BonnyelizAuthor Commented:
I did remove and reload the driver from the problem workstation.  I even tried loading the printer as local with the appropriate IP port.  I'll try deleting the spooler.  Keep the suggestions coming, and Thanks!
0
 
Jay_Jay70Commented:
did the test page appear to go through fine in windows

if it didnt even print that then i would completely remove the printer from the network and reinstall it, if there is no life in the thing then maybe call the manufacturer as it may be dead
0
 
BonnyelizAuthor Commented:
Unbelievable!  The problem was an access code requirement from the copier/printer.  User was unaware of the requirement until we walked through how another user prints successfully.  All is well!  Thanks for the efforts and suggestions - all of you!
0
 
Jay_Jay70Commented:
great :)
0
 
BonnyelizAuthor Commented:
I think the points are warranted given that the problem WAS in fact, with the printer itself requiring an access code.  Another trial from an uneducated user.  Ah well, keeps me in business!

Thanks for all efforts!
0
 
Jay_Jay70Commented:
thankyou :)
0

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

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