Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

won´t print my documents

Status
Not open for further replies.

Nostradamus

Technical User
May 3, 2000
419
SE
communication works fine and the printer itself is online and printing windows-jobs like a little devil.
when printing from unix, the jobs lays on top of each other. The printer deamon itself is working properly (it´s spooling correctly to other printers in other locations).
it doesn´t matter which computer you print from, when you print to that specific printer the jobs won´t get through.
I´ve tried restarting the printer services with lpshut and lpsched. It didn´t help.

should I try installing the printer again?
what can be causing this?
[sig]<p>Nostradamus<br><a href=mailto: > </a><br><a href= > </a><br> [/sig]
 
Mr Nostradamus, try looking into the future to see if your problem get's resolved.
Only joking.

Is the printer the same as the working ones, is it configured the same, does it print localy, does it print from other systems on the network? [sig]<p>Ged Jones<br><a href=mailto:gedejones@hotmail.com>gedejones@hotmail.com</a><br><a href= > </a><br>Top man[/sig]
 
Have you ever read the book &quot;my life in plaster?&quot;
just kidding. my prophecies can´t be used for personal gain :)
the printers are generally the same. some different brands. it is configured the same (as far as I can see). We only have unix and windows as systems. from win9x and NT it works like a charm.

The printer doesn´t have any printer server connected to it. It uses an internal NIC. if that has anything to do with it.

the users (doctors, who print patient-related material) are getting more and more desperat. [sig]<p>Nostradamus<br><a href=mailto: > </a><br><a href= > </a><br> [/sig]
 
Have you seen the following thread?
SCO and Windows Printing thread58-29363 [sig]<p>Ged Jones<br><a href=mailto:gedejones@hotmail.com>gedejones@hotmail.com</a><br><a href= > </a><br>Top man[/sig]
 
Is this a network printer? If so, is it connected to a network print server, does it have it's own print server, or is it maybe connected to a NT or Novell server?

If it is a network printer, can you ping it from the SCO server? Is the printer on the same network as the SCO server? What are the IP addresses and netmasks of the server and the printer/print server?

Just a few questions to keep you busy 8) [sig]<p> Andy Bold<br><a href=mailto: > </a><br><a href= > </a><br>"I've probably made most of the mistakes already, so hopefully you won't have to..." Me, most days.[/sig]
 
The printer has an internal NIC. not connected to any server (nt, novell, printer). Communication works fine, since I can ping it by ip-adress and hostname.
netmasks and ip adresses are in order. it just stopped working all the sudden.
the printer is on another network 255.255.255.0 instead of 255.255.252.0 but routing is working properly.

any more help you can give me?

I´ve seen the thread askewged. Not excactly my problem I´m afraid. but thanks anyway.
[sig]<p>Nostradamus<br><a href=mailto: > </a><br><a href= > </a><br> [/sig]
 
When you list jobs to the printer, do they disapear from the print queue or do they stay in the queue?
Also can you print it at all from any other systems on the network and does it test print okay? [sig]<p>Ged Jones<br><a href=mailto:gedejones@hotmail.com>gedejones@hotmail.com</a><br><a href= > </a><br>Top man[/sig]
 
I still don´t know what caused this problem.
I fixed it by removing the printer in scoadmin (lpadmin -x[que]) and reinstall it.
Why did this happen? Can I prevent it somehow?
Thanks for your replies.
[sig]<p>Nostradamus<br><a href=mailto: > </a><br><a href= > </a><br> [/sig]
 
I've seen similar problems before after deleting a print job (using &quot;cancel job-id&quot;) from the print queue for a networked printer. This is related to networked printers that use &quot;lpsystem&quot; and are added using &quot;lpadmin -p<printername> -s<queuename>!<ipname>&quot;.

What seems to happen is that a symbolic link below /usr/spool/lp/lpd that links to a temporary directory gets removed. The name of the symbolic link is the same as the IP name of the server. I think it's a bug in the original System V lp code, as I've seen it happen on SCO OpenServer, SCO UnixWare, and Solaris 2.1.

The only way I found to correct things was to run &quot;lpshut;lpsched&quot; after deleting a print job for a networked printer. It could be that deleting and recreating the printer has the same effect.

Calls to our tech support about this issue started getting a little boring after the 7th or 8th suggestion of a patch to install, so we tend to stick with stopping/restarting lp after running &quot;cancel&quot;...

Hope this helps. [sig]<p> Andy Bold<br><a href=mailto: > </a><br><a href= > </a><br>"I've probably made most of the mistakes already, so hopefully you won't have to..." Me, most days.[/sig]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top