Sponsored Content
Operating Systems SCO Sco-Unix IP Printer no longer working Post 302156142 by Netwrkengeer on Monday 7th of January 2008 11:25:04 AM
Old 01-07-2008
Sco-Unix IP Printer no longer working

I have a client running Sco-Unix 5.
They have many IP Printers setup.
One of the IP Printers is "LPJ", it has been functional for 3 weeks and then the switch died and hung up the queue. We reset the switch and restarted the jobs and they printed.
The switch went down again and we replaced the switch and restarted the jobs and nothing printed.
The printer is functional, can be pinged and can be printed from windows.
The Unix print manager is recieving the print requests and I can transfer the "LPJ" jobs to another queue and they will print fine.
The /etc/hosts file is correct
The printer is printing to /dev/null
The model is correct.
I have attempted to print the hosts file from the terminal and the job hangs until I transfer it to another queue.

So what am I missing here? What do I need to change or check to get this printer to print again.
 

9 More Discussions You Might Find Interesting

1. SCO

Telnet connection to Sco Unixware from Windows 2000 taking longer !!!

Telnet connection to SCO Unixware server taking longer to return the Login prompt !!! Thanx in advance for any suggestions or help in this regard . Cheers KBiswas (9 Replies)
Discussion started by: kbiswas
9 Replies

2. UNIX for Dummies Questions & Answers

Printer + Unix (SCO)

Hello, I'm a real noob with Unix. I have to make an installation of a printer, EPSON LQ 2080 (impact printer) on local port ltp, on a Unix SCO 5.7. So....where can I find the driver, and how can I install it on a sco ? Sorry for my english, i'm frenchy ;) Thank you ! (1 Reply)
Discussion started by: kok
1 Replies

3. UNIX for Advanced & Expert Users

SCO Unix printer waiting for auto-retry

Running SCO 5.0.5 with all the updates available on a Compaq 800 and just ran into this problem of the printer that is hooked up to /dev/lp0 &or /dev/lp. The printer has been working fine for 5 plus years and still works on another machine. I've uninstalled & re-installed the parallel port and... (0 Replies)
Discussion started by: cfaiman
0 Replies

4. UNIX for Advanced & Expert Users

Configure SCO Unix to print on windows base XP printer

Hi, I have done this year ago, and now I need to do it again, but did not remember how I do it. I have a slip printer on a windows xp workstation and i need to print from SCO unix application to that printer. I try to create a remote printer but the only option available is unix, the other to... (0 Replies)
Discussion started by: comsiconsa
0 Replies

5. Forum Support Area for Unregistered Users & Account Problems

my account is no longer working

my account mhm4 is no longer working (9 Replies)
Discussion started by: mhm4
9 Replies

6. UNIX for Dummies Questions & Answers

rm /var/db/.AppleSetupDone no longer working for mac OS X 10.6??!? HELP!!!!

My roommate forgot his admin password on his MacBook air.. He doesn't have the external SuperDrive, so we have no way of using the simple method of using the install disks and resetting the password.. The worst part is, he did this same thing about a year ago lol At the time, we booted... (0 Replies)
Discussion started by: PhiGam
0 Replies

7. SCO

SCO UNIX ftp - weird kind of working

hi, i am working on sco unix 5.07, i have 10 individual servers networked locally in which sco os is installed. one of them is not transferring the file to other servers but accepting all files. means Server (A) can accept the file through FTP from any server but not transferring FTP its own... (9 Replies)
Discussion started by: aafflatoon
9 Replies

8. UNIX for Dummies Questions & Answers

Script is not longer working in the crontab

This is the crontab it is supossed to be running everyday but it didnt 5 0 * * * /export/app/CO/opge/scr/Informe_parametros_colombia.ksh >/dev/null 2>&1 Inside the above script connects to a database and extract data to a flat file, manually i run the script at about 2 a.m. and Works OK,... (6 Replies)
Discussion started by: alexcol
6 Replies

9. UNIX for Dummies Questions & Answers

vnc No Longer Working Correctly

Hello All, Yesterday, all day, I was using x11vnc and vncviewer to connect to a server. But today for some reason it is not working. I don't remember changing any settings or anything like that, but because it stopped working correctly I guess something has...? I'm issuing the exact same... (0 Replies)
Discussion started by: mrm5102
0 Replies
lpc(1B) 					     SunOS/BSD Compatibility Package Commands						   lpc(1B)

NAME
lpc - line printer control program SYNOPSIS
/usr/ucb/lpc [ command [ parameter...]] DESCRIPTION
The lpc utility controls the operation of local printers. Use lpc to perform the following functions: o start or stop a printer, o disable or enable a printer's spooling queue, o rearrange the order of jobs in a print queue, or o display the status of a printer print queue and printer daemon. lpc can be run from the command line or interactively. Specifying lpc with the optional command and parameter arguments causes lpc to interpret the first argument as an lpc command, and all other arguments as parameters to that command. Specifying lpc without arguments causes it to run interactively, prompting the user for lpc commands with lpc>. By redirecting the standard input, lpc can read commands from a file. USAGE
lpc commands may be typed in their entirety or abbreviated to an unambiguous substring. Some lpc commands are available to all users; oth- ers are available only to super-users. All users may execute the following lpc commands: ? [command ...] | help [command ...] Displays a short description of command. command is an lpc command. If command is not specified, displays a list of lpc commands. exit | quit Exits from lpc. status [all | printer ...] Displays the status of print daemons and print queues. all specifies that this command is performed on all locally attached printers. printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for infor- mation regarding naming conventions for atomic names. Only a super-user may execute the following lpc commands: abort [all | printer ...] Terminates an active spooling daemon. Disables printing (by preventing new daemons from being started by lpr(1B)) for printer. all specifies this command is performed on all locally attached printers. printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. clean [all | printer ...] Removes files created in the print spool directory by the print daemon from printer 's print queue. all specifies that this command is performed on all locally attached printers.printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. disable [all | printer ...] Turns off the print queue for printer. Prevents new printer jobs from being entered into the print queue for printerby lpr(1B). all specifies that this command is performed on all locally attached printers. printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. down [all | printer ...] [message] Turns the queue for printer off and disables printing on printer. Inserts message in the printer status file. message does not need to be quoted; multiple arguments to message are treated as arguments are to echo(1). Use down to take a printer down and inform users. all specifies that this command is performed on all locally attached printers. printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. enable [all | printer ...] Enables lpr(1B) to add new jobs in the spool queue. all specifies that this command is performed on all locally attached printers. printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for infor- mation regarding naming conventions for atomic names. restart [all | printer ...] Attempts to start a new printer daemon. restart is useful when a print daemon dies unexpectedly and leaves jobs in the print queue. all specifies that this command is performed on all locally attached printers. printer indicates that this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. start [all | printer ...] Enables printing. Starts a spooling daemon for the printer. all specifies that this command is performed on all locally attached printers. printer indicates the command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. stop [all | printer ...] Stops a spooling daemon after the current job is complete. Disables printing at that time. all specifies that this command is performed on all locally attached printers. printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. topq printer [request-ID ...] [user ...] Moves request-ID or print jobs belonging to user on printer to the beginning of the print queue. Specify user as a user's login name. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. up [all | printer ...] Turns the queue for printer on and enables printing on printer. Deletes the message in the printer status file (inserted by down). Use up to undo the effects of down. all specifies that this command is performed on all locally attached printers. printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf( 4) for information regarding naming conventions for atomic names. EXIT STATUS
The following exit values are returned: 0 Successful completion. non-zero An error occurred. FILES
/var/spool/lp/* LP print queue. /var/spool/lp/system/pstatus Printer status information file. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWscplp | +-----------------------------+-----------------------------+ SEE ALSO
echo(1), lpq(1B), lpr(1B), lprm(1B), lpstat(1), lpsched(1M), lpshut(1M), svcadm(1M), printers.conf(4), attributes(5) DIAGNOSTICS
Use the svcs(1) utility to check if svc:/application/print/server is running. If it is not running, use svcadm enable svc:/applica- tion/print/server to start lpsched. See svcadm(1M). Ambiguous command Indicates that the lpc command or abbreviation matches more than one command. ?Invalid command Indicates that the lpc command or abbreviation is not recognized. ?Privileged command Indicates that the lpc command or abbreviation can be executed only by a super-user. lpc: printer: unknown printer to the print service Indicates that printer does not exist in the LP database. Check that printer was correctly specified. Use lpstat -p or the status command (see lpstat(1) or USAGE) to check the status of printers. lpc: error on opening queue to spooler Indicates that the connection to lpsched failed. Usually means that the printer server has died or is hung. Use /usr/lib/lp/lpsched to check if the printer spooler daemon is running. lpc: Can't send message to LP print service lpc: Can't receive message from LP print service Indicates that the LP print service stopped. Contact the LP administrator. lpc: Received unexpected message from LP print service Indicates a problem with the software. Contact the LP administrator. SunOS 5.10 5 Aug 2004 lpc(1B)
All times are GMT -4. The time now is 12:04 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy