Printing to network printers

Printing to network printers

[Steve Rainbird]

How can I print to a network printer?

I know if its attached to a server I can say

lpr -d //server/printer file


But what do I do if the printer isn't attached to a server and is just a 
printer on the network?

TIA


-- 
Steve 


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Printing to network printers

[Larry Hall (Cygwin)]

Steve Rainbird wrote:
> How can I print to a network printer?
> 
> I know if its attached to a server I can say
> 
> lpr -d //server/printer file
> 
> 
> But what do I do if the printer isn't attached to a server and is just a 
> printer on the network?

So it's connected to the network with what, some kind of print server?
If so and assuming the print server allows you to descibe the printer as
a samba share, then the //<printer server name>/<printer share name>
syntax may work.  An IP address may be used in place of
<printer server name> too.  If not, you need to configure the printer
through Windows as a network TCP/IP printer and then access it as you
would a local printer.


-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
216 Dalton Rd.                          (508) 893-9889 - FAX
Holliston, MA 01746

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Printing to network printers

[Rick Rankin]

> From: Steve Rainbird
> 

> How can I print to a network printer?
> 
> I know if its attached to a server I can say
> 
> lpr -d //server/printer file
> 
> 
> But what do I do if the printer isn't attached to a server and is just a printer 
> on the network?

You should be able to add the printer through control panel, which will give it a local name. You can then use that name as the argument to -d. It's usually simpler if the name doesn't contain any spaces, but that's not a requirement.

Many network printers also provide a UNC-style name (//server/printer), even though they're not directly connected a server, per se. If you can browse to the printer when you're adding it, you should be able to use that name directly. It all depends on how the provides its networking capability.

I assume you know that lpr is quite stupid, i.e., it just spools the file, assuming that it is already correctly formatted for the target printer. It was originally written to spool a postscript file to a postscript printer. It didn't need to do any formatting.

--Rick


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Printing to network printers

[Steve Rainbird]

"Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com> wrote in message 
news:4947D2A9.3060505@cygwin.com...
> Steve Rainbird wrote:
>> How can I print to a network printer?
>>
>> I know if its attached to a server I can say
>>
>> lpr -d //server/printer file
>>
>>
>> But what do I do if the printer isn't attached to a server and is just a 
>> printer on the network?
>
> So it's connected to the network with what, some kind of print server?
> If so and assuming the print server allows you to descibe the printer as
> a samba share, then the //<printer server name>/<printer share name>
> syntax may work.  An IP address may be used in place of
> <printer server name> too.  If not, you need to configure the printer
> through Windows as a network TCP/IP printer and then access it as you
> would a local printer.
>
>
> -- 
> Larry Hall                              http://www.rfk.com
> RFK Partners, Inc.                      (508) 893-9779 - RFK Office
> 216 Dalton Rd.                          (508) 893-9889 - FAX
> Holliston, MA 01746
>
> _____________________________________________________________________
>
> A: Yes.
> > Q: Are you sure?
> >> A: Because it reverses the logical flow of conversation.
> >>> Q: Why is top posting annoying in email?
>

I have configured the printer in windows and printed the file to it using 
notepad.

In the event viewer it says

Document 13, \cobol\prints\PRINT.BALANCES.20081203083027 owned by 
steve.rainbird was printed on IAS_HP4PBN_A via port IP_10.26.5.11.  Size in 
bytes: 274872; pages printed: 2

When I print the same file using enscript I get

Document 14, stdin owned by steve.rainbird was printed on IAS_HP4PBN_A via 
port IP_10.26.5.11.  Size in bytes: 21499; pages printed: 0

For some reason its not printing anything.



-- 
Steve 



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Printing to network printers

[Steve Rainbird]

"Rick Rankin" <rrankin1424-cygwin@yahoo.com> wrote in message 
news:189950.11753.qm@web65613.mail.ac4.yahoo.com...
>> From: Steve Rainbird
>>
>
>> How can I print to a network printer?
>>
>> I know if its attached to a server I can say
>>
>> lpr -d //server/printer file
>>
>>
>> But what do I do if the printer isn't attached to a server and is just a 
>> printer
>> on the network?
>
> You should be able to add the printer through control panel, which will 
> give it a local name. You can then use that name as the argument to -d. 
> It's usually simpler if the name doesn't contain any spaces, but that's 
> not a requirement.
>
> Many network printers also provide a UNC-style name (//server/printer), 
> even though they're not directly connected a server, per se. If you can 
> browse to the printer when you're adding it, you should be able to use 
> that name directly. It all depends on how the provides its networking 
> capability.
>
> I assume you know that lpr is quite stupid, i.e., it just spools the file, 
> assuming that it is already correctly formatted for the target printer. It 
> was originally written to spool a postscript file to a postscript printer. 
> It didn't need to do any formatting.
>
> --Rick
>
>

I am actually using enscript which I assume uses lpr for its printing?

-- 
Steve 



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Printing to network printers

[Steve Rainbird]

"Steve Rainbird" <steve.rainbird@mssint.com> wrote in message 
news:gi98pb$m01$1@ger.gmane.org...
>
>
> "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com> wrote in message 
> news:4947D2A9.3060505@cygwin.com...
>> Steve Rainbird wrote:
>>> How can I print to a network printer?
>>>
>>> I know if its attached to a server I can say
>>>
>>> lpr -d //server/printer file
>>>
>>>
>>> But what do I do if the printer isn't attached to a server and is just a 
>>> printer on the network?
>>
>> So it's connected to the network with what, some kind of print server?
>> If so and assuming the print server allows you to descibe the printer as
>> a samba share, then the //<printer server name>/<printer share name>
>> syntax may work.  An IP address may be used in place of
>> <printer server name> too.  If not, you need to configure the printer
>> through Windows as a network TCP/IP printer and then access it as you
>> would a local printer.
>>
>>
>> -- 
>> Larry Hall                              http://www.rfk.com
>> RFK Partners, Inc.                      (508) 893-9779 - RFK Office
>> 216 Dalton Rd.                          (508) 893-9889 - FAX
>> Holliston, MA 01746
>>
>> _____________________________________________________________________
>>
>> A: Yes.
>> > Q: Are you sure?
>> >> A: Because it reverses the logical flow of conversation.
>> >>> Q: Why is top posting annoying in email?
>>
>
> I have configured the printer in windows and printed the file to it using 
> notepad.
>
> In the event viewer it says
>
> Document 13, \cobol\prints\PRINT.BALANCES.20081203083027 owned by 
> steve.rainbird was printed on IAS_HP4PBN_A via port IP_10.26.5.11.  Size 
> in bytes: 274872; pages printed: 2
>
> When I print the same file using enscript I get
>
> Document 14, stdin owned by steve.rainbird was printed on IAS_HP4PBN_A via 
> port IP_10.26.5.11.  Size in bytes: 21499; pages printed: 0
>
> For some reason its not printing anything.
>
>
>
> -- 
> Steve
>
>

BTW enscript says

$  enscript -d IAS_HP4PBN_A PRINT.BALANCES.20081203083027
[ 4 pages * 1 copy ] sent to IAS_HP4PBN_A



-- 
Steve 



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Printing to network printers

[Rick Rankin]

> From: Steve Rainbird
> 
> "Rick Rankin" wrote in message 
> news:189950.11753.qm@web65613.mail.ac4.yahoo.com...
> >> From: Steve Rainbird
> >> 
> > 
> >> How can I print to a network printer?
> >> 
> >> I know if its attached to a server I can say
> >> 
> >> lpr -d //server/printer file
> >> 
> >> 
> >> But what do I do if the printer isn't attached to a server and is just a 
> printer
> >> on the network?
> > 
> > You should be able to add the printer through control panel, which will give 
> it a local name. You can then use that name as the argument to -d. It's usually 
> simpler if the name doesn't contain any spaces, but that's not a requirement.
> > 
> > Many network printers also provide a UNC-style name (//server/printer), even 
> though they're not directly connected a server, per se. If you can browse to the 
> printer when you're adding it, you should be able to use that name directly. It 
> all depends on how the provides its networking capability.
> > 
> > I assume you know that lpr is quite stupid, i.e., it just spools the file, 
> assuming that it is already correctly formatted for the target printer. It was 
> originally written to spool a postscript file to a postscript printer. It didn't 
> need to do any formatting.
> > 
> > --Rick
> > 
> > 
> 
> I am actually using enscript which I assume uses lpr for its printing?
> 
> -- Steve 
> 

Well, by default it does. A couple of (hopefully) obvious questions: Is the file you're trying to print (PRINT.BALANCES.20081203083027) a simple ASCII file, and is the printer (IAS_HP4PBN_A) a postscript printer? 

--Rick


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Printing to network printers

[Steve Rainbird]

"Rick Rankin" <rrankin1424-cygwin@yahoo.com> wrote in message 
news:315835.54676.qm@web65606.mail.ac4.yahoo.com...
>
>
>
>
>> From: Steve Rainbird
>>
>> "Rick Rankin" wrote in message
>> news:189950.11753.qm@web65613.mail.ac4.yahoo.com...
>> >> From: Steve Rainbird
>> >>
>> >
>> >> How can I print to a network printer?
>> >>
>> >> I know if its attached to a server I can say
>> >>
>> >> lpr -d //server/printer file
>> >>
>> >>
>> >> But what do I do if the printer isn't attached to a server and is just 
>> >> a
>> printer
>> >> on the network?
>> >
>> > You should be able to add the printer through control panel, which will 
>> > give
>> it a local name. You can then use that name as the argument to -d. It's 
>> usually
>> simpler if the name doesn't contain any spaces, but that's not a 
>> requirement.
>> >
>> > Many network printers also provide a UNC-style name (//server/printer), 
>> > even
>> though they're not directly connected a server, per se. If you can browse 
>> to the
>> printer when you're adding it, you should be able to use that name 
>> directly. It
>> all depends on how the provides its networking capability.
>> >
>> > I assume you know that lpr is quite stupid, i.e., it just spools the 
>> > file,
>> assuming that it is already correctly formatted for the target printer. 
>> It was
>> originally written to spool a postscript file to a postscript printer. It 
>> didn't
>> need to do any formatting.
>> >
>> > --Rick
>> >
>> >
>>
>> I am actually using enscript which I assume uses lpr for its printing?
>>
>> -- Steve
>>
>
> Well, by default it does. A couple of (hopefully) obvious questions: Is 
> the file you're trying to print (PRINT.BALANCES.20081203083027) a simple 
> ASCII file, and is the printer (IAS_HP4PBN_A) a postscript printer?
>
> --Rick
>
>

Rick,

Yes its a simple ascii file.

I think its a postscript printer but even if I use lpr directly it does the 
same thing (or doesn't if you see what I mean).

-- 
Steve 



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Printing to network printers

[Rick Rankin]

> From: Steve Rainbird
> "Rick Rankin" wrote in message 
> > 

[snip]

> > 
> > Well, by default it does. A couple of (hopefully) obvious questions: Is the 
> file you're trying to print (PRINT.BALANCES.20081203083027) a simple ASCII file, 
> and is the printer (IAS_HP4PBN_A) a postscript printer?
> > 
> > --Rick
> > 
> > 
> 
> Rick,
> 
> Yes its a simple ascii file.
> 
> I think its a postscript printer but even if I use lpr directly it does the same 
> thing (or doesn't if you see what I mean).
> 
> -- Steve 
> 

Using lpr directly doesn't really tell you anything. If you're sending a postscript file to a non-postscript printer, I would expect it to do nothing. Likewise, sending a plain ASCII file to a postscript printer would likely print nothing. What a non-postscript printer does with a plain ASCII file depends on the printer and how it's configured, but doing nothing is a distinct possibility.

If you look at the Windows printer queue after using enscript or lpr directly, does a job appear in the queue? If so, it's not an enscript/lpr issue. They're simply not the right tools for the job. In other words, they're not producing a file that is formatted correctly for your printer.

If no print job shows up, then you're probably not specifying the queue correctly to enscript/lpr. Unfortunately, that's a local configuration issue and I'm not sure anyone here can help you with that.

--Rick


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/