- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: remote printing to Windows 2000
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2003 09:30 AM
07-16-2003 09:30 AM
remote printing to Windows 2000
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
#
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2003 11:46 AM
07-16-2003 11:46 AM
Re: remote printing to Windows 2000
Chris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2003 01:38 PM
07-16-2003 01:38 PM
Re: remote printing to Windows 2000
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2003 01:49 PM
07-16-2003 01:49 PM
Re: remote printing to Windows 2000
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2003 01:52 PM
07-16-2003 01:52 PM
Re: remote printing to Windows 2000
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2003 09:12 AM
07-17-2003 09:12 AM
Re: remote printing to Windows 2000
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.