network printer static IP

[Haines Brown]

I have a HP LJ1320 printer working with Squeeze, but now want another
machine to access the printer via a wireless router (D-Link
DSL-2640B). The directions often assume the person runs a desktop
environment, has access to a network manager or control panel or that
the local printer already has an IP address.

Simply, how do I manually assign a static IP address to my printer?

Haines Brown

[Lew Pitcher]

On Wednesday 15 February 2012 14:56, in alt.os.linux.debian,

First off, identify where the printer gets it's IP address from now.

Then, change that component, so as to assign a static IP address instead.

For more detail, give us more detail about the setup. Specifically, where
does the printer get it's IP address from now, and what alternatives have
you available?

FWIW, my HP J468o Wifi-enabled printer obtains it's static IP address from
my LAN's DHCP server. The wifi router is configured as a "pass through",
and does not assign IP addresses itself. This required that I change the
default configuration of my wifi router, and install, configure, and run a
DHCP server on my server system. This may not be the best solution for you.

--
Lew Pitcher

[J G Miller]

On Wednesday, February 15th, 2012, at 14:56:30h -0500,
Haines Brown asked:

> HP LJ1320

This appears to have an embedded web server.

<http://h20000.www2.hp.COM/bizsupport/TechSupport/Document.jsp?locale=en_US&taskId=115&prodSeriesId=410622&prodTypeId=18972&objectID=c00239102>

Point your browser at the web server on the printer
using its current dynamically assigned IP address.

Go to the setup configuration page, enter the administrator
user name and password, change the IP type from dynamic/via DHCP
to static and then assign an appropriate static IP address and
netmask and maybe gateway address.

[Haines Brown]

J G Miller <mil...@yoyo.ORG> writes:

> On Wednesday, February 15th, 2012, at 14:56:30h -0500,
> Haines Brown asked:
>
>> HP LJ1320
>
> This appears to have an embedded web server.

> Point your browser at the web server on the printer using its current
> dynamically assigned IP address.

> Go to the setup configuration page, enter the administrator user name
> and password, change the IP type from dynamic/via DHCP to static and
> then assign an appropriate static IP address and netmask and maybe
> gateway address.

Directions seem to say that by pressing the go button on the printer 5
secs, the HP LJ will print out a configuration file that will indicate
the printer's IP address and status. The configuration file I get in
this way says nothing about TCP/IP or network status. Since I don't know
my printer's DHCP address I can't open its configuration interface in a
browswer.

HP says that the Jetdirect print server for its printers has default
address 192.0.0.192 or 169.254.x.x. The first just times out; I don't
know what to do with the latter. There is a Jetdirect Printer installer
utilty, but apparently not for my printer model. HP Jetadmin software to
set up a static address is apparently Windows only.

HP does provide directions for using telnet to set a static IP address
for a printer, but they are sketchy. Before I can use telnet, I have to
create a route. But I'm too ignorant to fathom the syntax. For example,
if I want to add the static address 192.168.1.100 for the printer to my
LAN, it would be with something like this:

# route add -net 192.168.1.0 192.168.1.100 netmask 255.255.255.0

but I suppose I would also have to append an interface file for the
printer, or maybe not. I can't find information on route add that refers
to adding a printer.

Once my LAN knows the route to the printer, maybe then I can open the
Jetdirect print server in my browser to configure the printer. Otherwise
it seems I can telnet to the printer to use its configuration utility:

# telnet 192.168.1.100

Then perhaps type:

SET LOCAL_ECHO
open 192.168.1.100
Enter
Enter
?

to get a list of commands to configure the printer's print server,
although I'm not sure at this point if this telnet syntax is correct,
what commands I'll find in this way, or what I'm supposed to be doing
with them.

Haines Brown

[J G Miller]

On Thursday, February 16th, 2012, at 12:20:06h -0500, Haines Brown wrote:

> Since I don't know my printer's DHCP address

You mean your printer's IP address [assigned by DHCP].

With your printer powered up and on line on your LAN,
do you not see the IP address of the printer with

arp -a

> HP says that the Jetdirect print server for its printers has default
> address 192.0.0.192 or 169.254.x.x.

But it all depends on your local network. Is your printer currently
connected to your router with an ethernet or WiFi connection?

[Haines Brown]

J G Miller <mil...@yoyo.ORG> writes:

> On Thursday, February 16th, 2012, at 12:20:06h -0500, Haines Brown wrote:
>
>> Since I don't know my printer's DHCP address
>
> You mean your printer's IP address [assigned by DHCP].

Yes

> With your printer powered up and on line on your LAN,
> do you not see the IP address of the printer with
>
> arp -a

No. # arp -a simply returns the IP address of my router.

>> HP says that the Jetdirect print server for its printers has default
>> address 192.0.0.192 or 169.254.x.x.
>
> But it all depends on your local network.

Yes, that makes sense.

> Is your printer currently connected to your router with an ethernet or
> WiFi connection?

Printer connected to LAN by Ethernet. # ifconfig only reports lo and
eth0 (a computer connected by cable). I have a machine using wifi to
access this router, but it is not yet interfaced with the LAN.

Haines

[Haines Brown]

Dave <noone$$@llondel.org> writes:

> Haines Brown wrote:
>
>> Simply, how do I manually assign a static IP address to my printer?

> Do you have access to the DHCP server configuration? If so, it can sometimes
> be easier to tell the DHCP server to assign a fixed IP address to the
> printer MAC address. That way the printer configuration stays unchanged but
> will always pick up the same IP address.

I find that in my router's DHCP server LAN set up I can disable DHCP,
but I don't want to do that. I want the DHCP to assign addresses to
hosts on the LAN, but want a static address for the printer. I find that
under LAN setup on the router, I can enter the IP address of the
management station permitted to access the local management services,
but does not sound relevant. Under DHCP leases, no reference to a
printer.

To get the printer's MAC address is another issue. I guess I can use
snmp, but don't I need the IP address of the printer first? Are you saying
that with a router having DHCP services, one should be able to associate
an address such as 192.168.1.100 to the printer's MAC address? Once
there is a IP address, the MAC address is displayed for it in my DHCP
sever.

Haines Brown

[John F. Morse]

What does the owner's or user's manual say?

--
John

When a person has -- whether they knew it or not -- already
rejected the Truth, by what means do they discern a lie?

[J G Miller]

On Thursday, February 16th, 2012, at 15:02:30h -0500, Haines Brown wrote:

> No. # arp -a simply returns the IP address of my router.

That is rather odd since arp -a should not only return
the IP address of your router but also the machine on
which you are running the command.

So have you ever actually printed anything from a machine
on the LAN to the printer via ethernet or WiFi?

Who installed the printer and setup its network
connections?

> Printer connected to LAN by Ethernet.

If you can send print jobs to it from the LAN it
must have an IP address valid for the LAN.

Usually going into the router administration web page you can
find a page telling you about connected devices and what the
router's DHCP server has assigned an IP address to it.

> # ifconfig only reports lo and eth0 (a computer connected by cable).

That is all that what one would expect from ifconfig
(unless you also had wlan0 because the host also had WiFi).

[John F. Morse]

J G Miller wrote:
> On Thursday, February 16th, 2012, at 15:02:30h -0500, Haines Brown wrote:
>
>
>> No. # arp -a simply returns the IP address of my router.
>>
>
> That is rather odd since arp -a should not only return
> the IP address of your router but also the machine on
> which you are running the command.
>

Gotta use sudo on Debian (unless root was given a password at
installation time or later).

Ubuntu doesn't require sudo at all.

[J G Miller]

On Thursday, February 16th, 2012, at 16:16:08h -0600, John F. Morse explained:

> J G Miller wrote:
>> On Thursday, February 16th, 2012, at 15:02:30h -0500, Haines Brown wrote:
>>
>>
>>> No. # arp -a simply returns the IP address of my router.
>>>
>>
>> That is rather odd since arp -a should not only return
>> the IP address of your router but also the machine on
>> which you are running the command.
>>
>
>
> Gotta use sudo on Debian (unless root was given a password at
> installation time or later).
>
> Ubuntu doesn't require sudo at all.

Maybe, but my original statement was just "plain wrong".

arp -a does not return the IP address of the machine on which
your are running the command.

So it looks to me as if either the printer is not connected to the LAN,
or switched on or has an active network connection.

[unruh]

On 2012-02-16, John F. Morse <jo...@example.invalid> wrote:
> J G Miller wrote:
>> On Thursday, February 16th, 2012, at 15:02:30h -0500, Haines Brown wrote:
>>
>>
>>> No. # arp -a simply returns the IP address of my router.
>>>
>>
>> That is rather odd since arp -a should not only return
>> the IP address of your router but also the machine on
>> which you are running the command.
>>
>
>
> Gotta use sudo on Debian (unless root was given a password at
> installation time or later).
>
> Ubuntu doesn't require sudo at all.
>
>

arp -s does not require root, and also does not return the own machine
ethernet since it knows itself and does not send traffic to itself over
the net. Furthermore, the printer will not have an entry in the arp
tables unless it has communicated with the computer.

[Thad Floryan]

On 2/16/2012 1:17 PM, Haines Brown wrote:
> [...]

> To get the printer's MAC address is another issue. I guess I can use
> snmp, but don't I need the IP address of the printer first? Are you saying
> that with a router having DHCP services, one should be able to associate
> an address such as 192.168.1.100 to the printer's MAC address?

> [...]

That is correct. Though most of the systems here:

<http://thadlabs.com/PIX/Thad_desk.jpg>

I also have their entries in my DHCP server (a SheevaPlug running
Ubuntu; my GuruPlug runs Debian) so the physical box assumes the
same IP when I boot, say, a Live-CD/-DVD.

The dhcpd.conf file entries are simple; here's a sampling of some
for my LAN:

[...]
host ubuntu-dock {
hardware ethernet 00:B0:D0:57:66:39;
fixed-address 172.20.20.56;
}
host ubuntu {
hardware ethernet 00:06:5B:D5:0D:25;
fixed-address 172.20.20.56;
}
[...]
# HP2015db with networking
host TL2015 {
hardware ethernet 00:1B:78:19:71:44;
fixed-address 172.20.20.90;
}
[...]
# HP4050 LaserJet with networking
host TL4050 {
hardware ethernet 00:01:E6:AE:57:91;
fixed-address 172.20.20.99;
}
[...]

[Thad Floryan]

On 2/16/2012 5:07 PM, Thad Floryan wrote:
> [...]
> That is correct. Though most of the systems here:
>
> <http://thadlabs.com/PIX/Thad_desk.jpg>
>
> I also have their entries in my DHCP server (a SheevaPlug running

> [...]

Oops, I wasn't watching the screen due to an interruption.

The above should read:

... Though most of the systems here:
[...]
have a fixed IP address, I also have their entries in my DHCP

:-)

[Chris Davies]

J G Miller <mil...@yoyo.org> wrote:
> That is rather odd since arp -a should not only return
> the IP address of your router but also the machine on
> which you are running the command.

My squeeze returns only non-local devices with which my local host
has communicated (recently).

Chris

[Chris Davies]

Haines Brown <hai...@historicalmaterialism.info> wrote:
> Since I don't know my printer's DHCP address I can't open its
> configuration interface in a browswer.

Run the following as root, and it will give you the devices on your
local network that are running a web server. Since your printer includes
a web server you should be able to see it listed:

aptitude install nmap
NET=`netstat -rn | awk '$4~/G/{print $2}' | cut -d. -f1-3`.0
nmap -oG - -p 80 $NET/24 | grep /open/


I've used aptitude but you're welcome to use your preferred package
installer. The NET= line is there to derive your local /24 network
(e.g. 192.168.1.0). If you know it, simply substitute into the nmap
command.

Chris

[Haines Brown]

J G Miller <mil...@yoyo.ORG> writes:

> On Thursday, February 16th, 2012, at 15:02:30h -0500, Haines Brown wrote:

I skip dialog re. # arp -a, other than to mention it that it only sees
my router on the network:

# arp -a
router (192.168.1.1) at 00:1e:58:07:68:84 [ether] on eth0

> So have you ever actually printed anything from a machine
> on the LAN to the printer via ethernet or WiFi?
>
> Who installed the printer and setup its network
> connections?

Ah, the light is beginning to shine! At this point, there is only one
machine on the LAN, and I print with it all the time. However, the
printer is connected by USB, not by ethernet CAT5; there's no ethernet
jack on the printer.

I suspect I need to add a Jetdirect print server to my LJ1320 printer, I
contacted HP and they pointed me to the HP Jetdirect 300x Print Server
for Fast Ethernet. It's compatible with RedHat 7 and SUSE 8, and so I
suppose it will work with my Debian squeeze. It has a DB-25 parallel
connector for the printer and a RJ-45 to connect to my router hub. My
printer is DB-36, so I suppose that all I need is a suitable cable to do
the pin conversion.

Am I off base here?

Haines

[Haines Brown]

Chris,

Since my printer is USB connected, I suppose the nmap return will not be
informative. But here it is anyway:

# nmap NET=`netstat -rn | awk '$4~/G/{print $2}' | cut -d. -f1-3` .0
Starting Nmap 5.00 ( http://nmap.org ) at 2012-02-17 08:55 EST
Failed to resolve given hostname/IP: NET=192.168.1.
Note that you can't use '/mask' AND '1-4,7,100-' style IP ranges
Invalid target host specification: .0
QUITTING!

# nmap 192.168.1.1
Starting Nmap 5.00 ( http://nmap.org ) at 2012-02-17 09:53 EST
Interesting ports on router (192.168.1.1):
Not shown: 991 closed ports
PORT STATE SERVICE
22/tcp open ssh
23/tcp open telnet
80/tcp open http
1863/tcp open msnp
1864/tcp open paradym-31
4443/tcp open pharos
5190/tcp open aol
5431/tcp open park-agent
5566/tcp open unknown
MAC Address: 00:1E:58:07:68:84 (D-Link)

# arp -a
router (192.168.1.1) at 00:1e:58:07:68:84 [ether] on eth0

Haines

[J G Miller]

On Friday, Februaty 17th, 2012, 09:55:36h -0500, Haines Brown wrote:

> Since my printer is USB connected

If the printer is USB connected and not ethernet connected
to the LAN, how do you ever hope to see it as a "host" on
the LAN with a network utility or for it to be assigned an
IP address by your router DHCP server?

[J G Miller]

On Friday, February 17th, 2012, at 09:50:25h -0500, Haines Brown wrote:

> However, the printer is connected by USB, not by ethernet CAT5

So you are never going to see the printer on the LAN.

> there's no ethernet jack on the printer.

And presumably it has no WiFi network capability either.

In other words, it is *NOT* a network printer.

Why did you lead everybody to think that it was with your
subject "network printer".

If the printer has no ethernet jack or WiFi capability it
cannot be assigned an IP address.

> I suspect I need to add a Jetdirect print server to my LJ1320 printer

Are you talking about software or hardware print server?

If software, then you are referring to Windoze software which
is not needed because you have CUPS to do that job on GNU/Linux.

If you are talking about a hardware device, then yes, that will
make the printer an independent network device on your LAN
and the print server will need an IP address and you will
no longer connect your printer via a USB cable to a dedicated
machine.

You should have bought a network capable model in the first place.

Remember when you submit a print job, the user does not (under
spooling print systems such as lpd or CUPS) send the print job
directly to the printer hardware device but to the print *QUEUE*
which is a daemon running either on the PC and this print queue
then turns the print job into a language that the printer can
understand (either Postscript or some sort of PCL) and that
transformed data then gets sent on to the actual hardware device.

PLEASE remember if you want help, you MUST describe in detail
how you have things setup and not just assume everybody knows
what you are doing and the state of your equipment.

[terryc]

Haines Brown wrote:

> I suspect I need to add a Jetdirect print server to my LJ1320 printer, I
> contacted HP and they pointed me to the HP Jetdirect 300x Print Server
> for Fast Ethernet. It's compatible with RedHat 7 and SUSE 8, and so I
> suppose it will work with my Debian squeeze. It has a DB-25 parallel
> connector for the printer and a RJ-45 to connect to my router hub. My
> printer is DB-36, so I suppose that all I need is a suitable cable to do
> the pin conversion.
>
> Am I off base here?

Nope, but if you have the $$$, I'd recommend an Axis printer server over
a HP or any other brand.

The only other way is to have the PC it is conected to share it on the
network. AFAIK, now next to impossible with Debian/Linux.

[J G Miller]

On Saturday, February 18th, 2012, at 02:28:38h +1100, Terry C opined:

> The only other way is to have the PC it is conected to share it on the
> network. AFAIK, now next to impossible with Debian/Linux.

Why so? Just go on to the CUPS administration page and make it
a shareable printer. For Windoze machines, it may be necessary
to set up SAMBA and have it advertised there as a shared printer.

[Chris Davies]

Haines Brown <hai...@historicalmaterialism.info> wrote:
> Since my printer is USB connected, I suppose the nmap return will not be
> informative

Absolutely pointless.

> # nmap NET=`netstat -rn | awk '$4~/G/{print $2}' | cut -d. -f1-3` .0

You've also managed to mangle the three lines I posted into one incorrect
one. But since your "network printer" isn't a network printer it's
irrelevant.

Chris

[Haines Brown]

J G Miller <mil...@yoyo.ORG> writes:

> On Friday, February 17th, 2012, at 09:50:25h -0500, Haines Brown wrote:
>
>> However, the printer is connected by USB, not by ethernet CAT5
>
> So you are never going to see the printer on the LAN.
>
>> there's no ethernet jack on the printer.
>
> And presumably it has no WiFi network capability either.
>
> In other words, it is *NOT* a network printer.
>
> Why did you lead everybody to think that it was with your
> subject "network printer".

Simple answer: my profound ignorance. I just didn't know there were
ordinary printers vs network printers. I never had any reason to
stumble on that bit of information.

>> I suspect I need to add a Jetdirect print server to my LJ1320 printer
>
> Are you talking about software or hardware print server?

Yes, hardware. Specifically a box called HP Jetdirect 300x Print Server
for Fast Ethernet. This is a lot cheaper than buying an network printer.

Haines

[Haines Brown]

terryc <newsnine...@woa.com.au> writes:

> Haines Brown wrote:
>
>> I suspect I need to add a Jetdirect print server to my LJ1320 printer, I
>> contacted HP and they pointed me to the HP Jetdirect 300x Print Server
>> for Fast Ethernet.

> Nope, but if you have the $$$, I'd recommend an Axis printer server
> over a HP or any other brand.

I see there is an Axis Network 5600+ print server and an Axis 5400+
print server, both cheaper than the HP Jetdirect 300x Print server.
The 5400+ has a 36-pin Centronics connector, which is what is on my
printer, and it is a bit cheaper. Is there any linux compatibility
issues with such print servers?

Haines Brown

[J G Miller]

On Friday, February 17th, 2012, at 17:51:19h -0500, Haines Brown wrote:

> Simple answer: my profound ignorance.

Okay, I had thought because you were a long time Debian
user and had some knowledge of networking that you understood
the difference.

> I just didn't know there were ordinary printers vs network printers.

A non-networked printer only allows a connection via either a printer
parallel cable or a USB (serial) cable to a computer.

A networked printer comes with an ethernet port and/or WiFi.

> Yes, hardware. Specifically a box called HP Jetdirect 300x Print Server
> for Fast Ethernet. This is a lot cheaper than buying an network printer.

I find it difficult to believe that the cost of a networked printer
is more expensive than the cost of a non-networked printer plus print server.

Anyways, if you are prepared to have the PC powered up that the printer is
connected to, when you want to print from other PCs, there is no need
to buy a print server. CUPS allows print queue sharing from other PCs
and if not possible directly, it can be done via SAMBA printer sharing
for Windoze PCs.

<http://tldp.ORG/HOWTO/Debian-and-Windows-Shared-Printing/sharing_with_windows.html>

<http://www.debian-administration.ORG/articles/425>

[terryc]

Haines Brown wrote:

>> Nope, but if you have the $$$, I'd recommend an Axis printer server
>> over a HP or any other brand.
>
> I see there is an Axis Network 5600+ print server and an Axis 5400+
> print server, both cheaper than the HP Jetdirect 300x Print server.
> The 5400+ has a 36-pin Centronics connector, which is what is on my
> printer, and it is a bit cheaper. Is there any linux compatibility
> issues with such print servers?

I have used the 5600 for about 15(?) years and it has been rock solid
for me. The only reason I recently put it aside it was that the
replacement inkjet only had a USB port, the other four printers all have
internal NICs and I couldn't find a source of Axis print servers in
Australia. Configuration can be done by http, ftp and telnet.

[terryc]

J G Miller wrote:
> On Saturday, February 18th, 2012, at 02:28:38h +1100, Terry C opined:
>
>> The only other way is to have the PC it is conected to share it on the
>> network. AFAIK, now next to impossible with Debian/Linux.
>
> Why so? Just go on to the CUPS administration page and make it
> a shareable printer.

I'm still on lprng, where it was supposedly possible as well.
I'll take your comment under consideration. CUPs has too much bloatware
assosicated with it for my liking.

[Rikishi42]

On 2012-02-17, Haines Brown <hai...@HistoricalMaterialism.info> wrote:
> Ah, the light is beginning to shine! At this point, there is only one
> machine on the LAN, and I print with it all the time. However, the
> printer is connected by USB, not by ethernet CAT5; there's no ethernet
> jack on the printer.

Some routers have an USB you can connect a printer to.

In that case, your computer(s) would print to the router's address, probably
using 'lp' as device/queue name.

> I suspect I need to add a Jetdirect print server to my LJ1320 printer, I
> contacted HP and they pointed me to the HP Jetdirect 300x Print Server
> for Fast Ethernet. It's compatible with RedHat 7 and SUSE 8, and so I
> suppose it will work with my Debian squeeze. It has a DB-25 parallel
> connector for the printer and a RJ-45 to connect to my router hub. My
> printer is DB-36, so I suppose that all I need is a suitable cable to do
> the pin conversion.

A jetdirect print server is a solution if you can't have the above one.
No support needed, those things are supposed to act as a generic LPR print
queue. Just connect it to the network and fix it's address:
- go to the web interface of your router
- look up the JetDirect in the DHCP table of assigned IP's
- take note of it's MAC and use it to assign a fixed address
End of story.

And when buying a print server, be suspicious of any model that needs to be
compatible with your OS. Let your DHCP assign an IP, use the IP, end of
story.


--
When in doubt, use brute force.
-- Ken Thompson

[J G Miller]

On Saturday, February 18th, 2012, at 10:54:47h +1100, Terry C wrote:

> I'm still on lprng, where it was supposedly possible as well.

Yes you just need to install SAMBA and configure a shareable printer
if you require access from Windoze PCs.

> CUPs has too much bloatware assosicated with it for my liking.

If lprng provides you will everything you need, then there is
no need to switch to CUPS.

[terryc]

J G Miller wrote:
> On Saturday, February 18th, 2012, at 10:54:47h +1100, Terry C wrote:
>
>> I'm still on lprng, where it was supposedly possible as well.
>
> Yes you just need to install SAMBA and configure a shareable printer
> if you require access from Windoze PCs.

Naah, I've gone for the print server boxen for a few decades now. so
much easier and safer.

>
>> CUPs has too much bloatware assosicated with it for my liking.
>
> If lprng provides you will everything you need, then there is
> no need to switch to CUPS.

That was partly why I stayed with it. the other was te fact tat I could
see absolutely no benefit in doing the MS like "driver" fan dango.

[Günther Schwarz]

J G Miller wrote:

> On Saturday, February 18th, 2012, at 10:54:47h +1100, Terry C wrote:
>
>> I'm still on lprng, where it was supposedly possible as well.
>
> Yes you just need to install SAMBA and configure a shareable printer if
> you require access from Windoze PCs.

Just for printing from a small number of Windows hosts there is no need
for the hazzle of setting up a samba server. Windows does speak ipp as
well. So defining an ipp target to the print server and queue will do the
job without the overhead of the smb protocol. As I do prefer CUPS over
lprng, I'm not certain about the status of ipp support on lprng.

Günther

[J G Miller]

On Saturday, February 18th, 2012, at 08:41:07h +0000, Günther Schwarz wrote:

> I'm not certain about the status of ipp support on lprng.

As far as I am aware lprng does not include IPP support,
although it can be added as a patch.

<http://jointlab.upol.CZ/~michale/projects/lprng-ipp/>

This was why I suggested that using SAMBA/CIFS was probably
necessary for sharing lprng printer queues with Windoze hosts.

[Günther Schwarz]

J G Miller wrote:

> On Saturday, February 18th, 2012, at 08:41:07h +0000, Günther Schwarz
> wrote:
>
>> I'm not certain about the status of ipp support on lprng.
>
> As far as I am aware lprng does not include IPP support, although it can
> be added as a patch.

Thanks for the hint.

> This was why I suggested that using SAMBA/CIFS was probably necessary
> for sharing lprng printer queues with Windoze hosts.

Which than replaces the modest overhead that comes with CUPS as compared
to other printing system with the significant one of a samba server :-)

Günther

[Rikishi42]

On 2012-02-18, J G Miller <mil...@yoyo.ORG> wrote:
> On Saturday, February 18th, 2012, at 08:41:07h +0000, Günther Schwarz wrote:
>
>> I'm not certain about the status of ipp support on lprng.
>
> As far as I am aware lprng does not include IPP support,
> although it can be added as a patch.

As a Windows print queue can also set to print to an LPR port, instead of
IPP that is not really an issue either.

> This was why I suggested that using SAMBA/CIFS was probably
> necessary for sharing lprng printer queues with Windoze hosts.

Nope, no need for that.

[Rikishi42]

On 2012-02-17, J G Miller <mil...@yoyo.ORG> wrote:
> A non-networked printer only allows a connection via either a printer
> parallel cable or a USB (serial) cable to a computer.

Or serial. Dont forget good ol' RS-232. :-)