topic Re: remote printing to Windows 2000 in Operating System - HP-UX

remote printing to Windows 2000

Walt Christensen — Wed, 16 Jul 2003 16:30:41 GMT

I have a software printer on a windows 2000 server that I need to output to from our HPux 10.20 erp program for faxing and email the output. I installed print services for UNIX on the windows server and edited the hosts file of both servers to resolve the ip addresses both ways. I made sure that the rlpdaemon line in the inetd.config file on the unix server was not commented out and and created a remote printer with the same name as the windows 2000 printer on the unix server.
I can status the print que on the windows 2000 server and see print jobs that are submited through windows operating systems on the unix server. but when I try to submit a job through unix to the remote printer it submits fine and then an lpstat says it is down. the windows server is fine though.
I have to delete the job to renable the printer in unix. as i said the windows server is fine.

I have tried actual laserjet printers and different windows server/printer combinations with this unix server but it still fails the unix printer.
I cannot print from a windows workstation to the unix box with print services for unix installed on the workstation either. I can install the LPR printer pointing to the unix server but when job is submitted on the workstation it says that "error/printer busy". I have validated the case and spelling over and over with no luck.
Please help
below is screen text:

# lpstat reformprn

#

printer queue for reformprn

Windows 2000 LPD Server
Printer \\172.16.1.37\REFORMPRN

Owner Status Jobname Job-Id Size Pages Priority
----------------------------------------------------------------------------

no entries

# lp -dreformprn bdf.txt

request id is reformprn-3439 (1 file)

# lpstat reformprn

reformprn-3439 root priority 0 Jul 11 08:52
bdf.txt 2938 bytes

printer queue for reformprn

Windows 2000 LPD Server
Printer \\172.16.1.37\REFORMPRN

Owner Status Jobname Job-Id Size Pages Priority
----------------------------------------------------------------------------
fmhprod: Warning: reformprn is down

#

**************after I delete the job and reenable the printer****************************

# lpstat reformprn

#

printer queue for reformprn

Windows 2000 LPD Server
Printer \\172.16.1.37\REFORMPRN

Owner Status Jobname Job-Id Size Pages Priority
----------------------------------------------------------------------------

no entries

***************I do a test page ON THE WINDOWS 2000 server TO THE WINDOWS 2000 printer and pause it****************************
**************Goto the unix machine and do Lpstat*************************************************************************************************

# lpstat reformprn

printer queue for reformprn

Windows 2000 LPD Server
Printer \\172.16.1.37\REFORMPRN (Paused)

Owner Status Jobname Job-Id Size Pages Priority
----------------------------------------------------------------------------
administrat Waiting Test Page 3 25912 1 1

no entries
#

Re: remote printing to Windows 2000

Chris Vail — Wed, 16 Jul 2003 18:46:26 GMT

At first stab, check the /etc/hosts on the Unix system and the HOSTS tables on each Win2K machine. Each should have a listing for the other(s). Do this even if your DNS works and is good.

Chris

Re: remote printing to Windows 2000

Walt Christensen — Wed, 16 Jul 2003 20:38:56 GMT

I made sure they had each other entries in their hosts files. It still did not fix it. I also tried setting up another remote printer to a non windows device - directly to the printer and I get the same message.

I did find something strange and that was an OLD install of Easy Spooler on the box, do you think that could cause problems? How do I remove it.

Re: remote printing to Windows 2000

Ron Kinner — Wed, 16 Jul 2003 20:49:44 GMT

Found this on http://www.easyspooler.com/faqa.html#faq3

Can I run the native spooler and EasySpooler at the same time?
A: Yes. But, since EasySpooler does everything the native spooler does, we strongly recommend that you run lpshut and stop the native spooler.

If, however, you have compelling reasons to run both simultaneously, the native spooler must run on port 515. You must, therefore, instruct EasySpooler to listen and connect on another port. Simply set the system parameters ezconnectport and ezlistenport (in lpsd.default) to the port you wish, and re- initialize the despooler.

Ron

Re: remote printing to Windows 2000

Ron Kinner — Wed, 16 Jul 2003 20:52:39 GMT

You need to break the link between lp and llp which were setup when it was installed. The following tells how to create the link. I assume you know how to break a link.:

Pre-Version 6

After upgrading, verify that ez, llp, lps and lpss are in /usr/bin and, as root, enter the following commands:

cd /usr/bin

mv lp lp.orig

ln -s llp lp

The following commands assure that ez, llp, and lps (lpss) have the correct permissions:

chmod 755 /usr/bin/ez

chmod 755 /usr/bin/llp

chmod 755 /usr/bin/lps

Ron

Re: remote printing to Windows 2000

Walt Christensen — Thu, 17 Jul 2003 16:12:56 GMT

I found that easyspooler did not have any links to remove. I also stopped the despooler that is in easyspooler. I made the port changes to the easyspooler lpds.default, started and stopped the despooler. But I am still unable to use rpl or the rlpdaemon. I am still getting the same reponses of the print queue stoping when I submit a print job to the remote printers.

Is there any way to see what service accepts a call to a specific port number? Can I see if the rpldaemon responds to the call to the port.

I have tried to telnet to the port number by typing telnet 172.16.1.37 515 at a windows workstation and it does seem to respond so something is accepting the call to the port number.

Also I have found that there are no entries in /var/spool/lpd no files, logs etc.