topic Re: Remote Printer Problem. in Operating System - HP-UX

Remote Printer Problem.

sekar parthasarathy — Fri, 07 Dec 2001 17:13:46 GMT

Hi,

we map the Remote printer Lexmark thru
Wan to one of HP Server (K580), That
Printer is attached to NT-Servers in the
other location. When we spool from the
HP server, no header and its prints
like stairsteps. Is there any config
require in NT-Server ?

Thanks in Advance

sekar.

Re: Remote Printer Problem.

Craig Rants — Fri, 07 Dec 2001 17:20:26 GMT

I generally say these errors occur because of CR+LF problems. Here is a url which may be of interest. The problem you have is addressed at the bottom of the url.

Good Luck,
C

Re: Remote Printer Problem.

S.K. Chan — Fri, 07 Dec 2001 17:21:12 GMT

Did you try lp command with -oBSD1 option ?
You need to setup the printer on the UNIX side with bsd printing and install LPDSVC on the NT box.

Re: Remote Printer Problem.

D. Jackson_1 — Fri, 07 Dec 2001 17:22:16 GMT

It sounds to me like a driver issue. What kind of printer is it?? Get the correct driver and you should be good to go.

Good Luck!

Re: Remote Printer Problem.

Craig Rants — Fri, 07 Dec 2001 17:24:09 GMT

Ok dumby, paste the url

http://groups.google.com/groups?q=HPUX+printer+return+after+line+feed&hl=en&rnum=3&selm=9odbdh%24cmr%242%40web1.cup.hp.com

Re: Remote Printer Problem.

Rita C Workman — Sat, 08 Dec 2001 21:39:13 GMT

I keep reading your post and trying to make sure I understand exactly what your doing...I feel I may not. But...your PC is attached to an NT Server. OK. Is your Lexmark printer attached to your NT server a network printer? Does it have an IP address? If it does...than just set up Jetadmin on your HP box, set up your Lexmark Network printer IP in your hosts file and use TCPIP as your protocol to send your print job. You can set the printer up as a remote printer with SAM...and with that you should be able to route it to the IP of the printer.
I do this all over the state I live in...HP to NT...IBM Mainframe to Xerox Printers. Crossing networks (WAN/LAN), & systems by simply utilizing TCPIP to route jobs to the printer(IP) I want.

But like I said..maybe I'm reading your post wrong.

So I hope this helps,
Rita

Re: Remote Printer Problem.

Bill Hassell — Sun, 09 Dec 2001 04:04:26 GMT

This is a very common problem (stairstep output) for remote printing. HP-UX uses SysV spooling which defines that the server must perform -o options, not the originator. Since NT knows nothing about the options, the requisite ASCII file conversion is not performed. NT simply sends the job to the printer (and HP-UX ASCII files have nothing but line-feed characters between lines).

This is why JetDirect printing is much preferred...HP-UX will preformat the priunt job, then send to job direct to the printer. And rather than sending it twice over the network (once to server, then again to printer), HP-UX communicates directly with the printer.

If you have no choice but to use NT servers, you'll need to create an lp wrapper which will preformat the jobs so they are printer-ready.

Re: Remote Printer Problem.

Frank Slootweg — Thu, 13 Dec 2001 15:01:37 GMT

Bill wrote:

> If you have no choice but to use NT servers,
> you'll need to create an lp wrapper which
> will preformat the jobs so they are printer-
> ready.

If your primary problem is the stairstep problem, you can feed the data through ux2dos(1) before sending it to lp(1), i.e.

ux2dos /dirname/filename | lp ...

If that is not feasible, you can put ux2dos in a *copy* of the rmodel script, i.e. my_rmodel, and remove/re-add the printer, specifying the new model script. You will need some expertise is shell programming to do this.