Discussion Locked

Unix PS Printing to NT Server Queues

0 helpful
25 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Server OS: NT4 or W2K
Print Driver: HP CLJ4500DN Postscript
Server Name: PS1
Queue Name: PS-Trans
Tray 1: Manual Feed (disabled in driver config)
Tray 2: Transparencies
Tray 3: Letter (disabled in driver config)

Document Default settings inprint queue all point to Tray 2(transparencies), so do all device driver settings. Tray 1 & 3 medias are disabled.

Trying to get Unix clients to use a MS-based server for printing transparencies. They create a remote print queue on their Unix workstation, pointing to Server: PS1 Printer: PS-Trans.

ASCII print jobs come out on transparency media, like they should, but PostScript print jobs come out on plain paper from Tray 3! It appears that the PS file passes through the queue to the default tray on the printer not to the tray selected by the driver. Changing the default tray on the printer itself is not an option.

All NT clients printing to that queue generate Transparencies by default.

Any ideas how to get Unix PS print jobsto come out on transparency media in Tray 2 using the NT server queue?

25 replies

by ann777

The only way I can think of, is by ftp'ing the print output to another Windows' based box and writing a script that takes it into MS Word and outputs to the NT print server.

Sorry, there's not any easier way that I know of. Unix is not as flexible with external devices.

by curious_george

I'm sorry I have still not found an acceptable solution to the problem, the project has been abandonded due to technical merits. Though many answers were intelligent and helpful(while others should have remained silent because they obviously can notread), none solved the problem, therefore I simply can not award my points. Thank you for your contribution though.

by mshavrov

Your guess was correct - PS goes by another way. I'm not sure which Unix system do you use, but what I can say: Unix printing process Text and PostScript files by different way and it can even ignore or change some parameters transmitted to printer queue. In case Unix detect it's text file it sends it to printer queue directly (more or less). In case it detects that it's Postscript file - it retrieves printer information and if it decide that it's not Postscript printer it uses specific filters(conversion utilities) which transforms Postscript data to intermediate format which then is transfered to printer queue. You should check printers definitions on your Unix machines and ether specify that your remote printer is Postscript printer orcheck filters information for Postscript conversion. It looks like after filter it sends data directly to Server but without Queue information (or with incorrect information).

Good luck.

by curious_george

I'm sorry I have still not found an acceptable solution to the problem, the project has been abandonded due to technical merits. Though many answers were intelligent and helpful(while others should have remained silent because they obviously can notread), none solved the problem, therefore I simply can not award my points. Thank you for your contribution though.

by twang

To search a white paper " LPD Server Adds and Prints Control Codes" from Microsoft website. It helps to configure a Win nt/2000 accepts print task from UNIX.

by curious_george

I'm sorry I have still not found an acceptable solution to the problem, the project has been abandonded due to technical merits. Though many answers were intelligent and helpful(while others should have remained silent because they obviously can notread), none solved the problem, therefore I simply can not award my points. Thank you for your contribution though.

by cavedweller

Here is an alternate solution. For several years I have "shared" Hp LaserJet printers with JetDirect interfaces between my SunOs/Solaris and Win-NT print queues. I set up a print queue on a Solaris server and all my Unix machines print through it and another print queue on my NT server. The JetDirect interface does a good job working with both servers.

Also (even if you use a single NT print server), make sure you have the exact ppd (postscript printer description) file installed on your Unix machines. The ppd file maps printer options to postscript commands. To use advanced features such as changing paper types or selecting alternate feed trays you need to have a ppd file written specifically for your printer. Generic ppd files only cover the basic features.

by curious_george

I'm sorry I have still not found an acceptable solution to the problem, the project has been abandonded due to technical merits. Though many answers were intelligent and helpful(while others should have remained silent because they obviously can notread), none solved the problem, therefore I simply can not award my points. Thank you for your contribution though.

by peace monger

Have you considered installing samba on your Windows NT server to handle file and print services? That's a cross platform, public domain solution that allows for different configurations. I wouldn't expect Unix clients to respect a Windows print driver, but with samba, I think you have more options available.

Peace Monger

by curious_george

I'm sorry I have still not found an acceptable solution to the problem, the project has been abandonded due to technical merits. Though many answers were intelligent and helpful(while others should have remained silent because they obviously can notread), none solved the problem, therefore I simply can not award my points. Thank you for your contribution though.

by estebandelatorre

Rather than NT, I would like you to try a "real" printserver like Hp's Jetdirect J170x or a nic card attached to the printer (more expensive..).
You will find very easy to configure and setup mix trays for different platforms, along with some activity report log.
J170x will cost as much as $140.-

Hope you can try it!!

by curious_george

I'm sorry I have still not found an acceptable solution to the problem, the project has been abandonded due to technical merits. Though many answers were intelligent and helpful(while others should have remained silent because they obviously can notread), none solved the problem, therefore I simply can not award my points. Thank you for your contribution though.

by ghislain.levesque

Download & install hp jetdirect printer installer. From that software ( it's free ) you will be able to define different print queue that used different trays for the same printer. All you need to do is define the print queue according to you're specification. It's quite simple to install and use.

Have fun

by curious_george

I'm sorry I have still not found an acceptable solution to the problem, the project has been abandonded due to technical merits. Though many answers were intelligent and helpful(while others should have remained silent because they obviously can notread), none solved the problem, therefore I simply can not award my points. Thank you for your contribution though.

by bhrdwh

I had the same problem, I used the HP Jetdirect software & thigs worked fine ever since. In fact we've been running 5 HP Laserjet printers on a single HP JetDirect Server.

by curious_george

I'm sorry I have still not found an acceptable solution to the problem, the project has been abandonded due to technical merits. Though many answers were intelligent and helpful(while others should have remained silent because they obviously can notread), none solved the problem, therefore I simply can not award my points. Thank you for your contribution though.

by curious_george

This is a simplified version of my problem. The problem extends to multiple printer devices that are not HP and therefore do not use the Jetadmin software. Additionally, there are about 1000 print devices.

by maz1980

Microsoft has included TCP/IP printing service on NT 4.0. To install it, go to Network Properties>Service on control panel then click "Add". On the UNIX client, set the lpr to the NT IP address and printer name. Read the manual of lpr to get more options

by curious_george

I'm sorry I have still not found an acceptable solution to the problem, the project has been abandonded due to technical merits. Though many answers were intelligent and helpful(while others should have remained silent because they obviously can notread), none solved the problem, therefore I simply can not award my points. Thank you for your contribution though.

by curious_george

For those of you that keep suggesting that I install TCP/IP print services, get a clue, Unix system couldn't even be communicating as I have describe they are, if the service were not already in place and functional.

by brianoc

Hi George,

I know this one is closed but did amyone suggest that you edit the /usr/spool/lp/interface/xxxx file so that U pass the control sequences that you want to the printer ??

Just a thought & will save you buggering about !!

Use lp -o(Whatever option U require) to select the sequences detailed in the above file ..

Cheers,

Brian

by curious_george

I'm sorry I have still not found an acceptable solution to the problem, the project has been abandonded due to technical merits. Though many answers were intelligent and helpful(while others should have remained silent because they obviously can notread), none solved the problem, therefore I simply can not award my points. Thank you for your contribution though.

by maxwell edison

The a2ps utility converts ASCII to two-column PostScript by default, and encloses the text in boxes with headers indicating date, time, filename and page number. You also get a line saying "Printed by username from node". You can override the defaults; see the man pages.

a2ps is useful if the printer can only accept PostScript. You can use it to produce different output formats (e.g., "2-up", where two pages of your file are shrunk to fit on a single sheet). It provides options to add items like line numbers, user, file, and system information to the output. The command syntax is:

% a2ps [global options] files [positional options] files

where global options apply to all files being printed, and positional options are applied only to the files found in the remainder of the command line (with the exception of -H as noted in the man page which only applies to the next file).

Here is an example where we pipe the output of a2ps to flpr (-p indicates portrait mode):

% a2ps-p file1 | flpr -q wh10w_lw

------------

See these links for the full description and links for download the utilities:

http://www.fnal.gov/docs/UNIX/unix_at_fermilab/htmldoc/rev1997/uatf-59.html

http://www.fnal.gov/cd/main/printing.html

(REMOVE SPACES from the pasted URLs.)

Good luck,

Maxwell

by curious_george

I'm sorry I have still not found an acceptable solution to the problem, the project has been abandonded due to technical merits. Though many answers were intelligent and helpful(while others should have remained silent because they obviously can notread), none solved the problem, therefore I simply can not award my points. Thank you for your contribution though.

This discussion is closed to new replies.