Re: netgear PS110 printserver usage for 2nd printer??

[Peter Teuben <teuben @ astro . umd . edu>]

Problem Solved! Executive summary:

My original printcap entry was right, the windows software just needed to
correctly write the new setup in it's firmware. it's all due to my never
fully understanding the dark sides of windows (re)configurations...


Ok, for sake of history and completeness, here's the scoop on that print
server and how I solved it. Thanks to all for the suggestions. Thanks to
an unscientific approach I don't know who was right, probably Stephan,
Maxwell and Przemek :-)

I tried a lot, including booting the PC, the server, lpd daemons on linux,
trying various physical and logical names, but nothing worked. In the end
I decided to remove all the Netgear software from the WinPC (you need an
administration program on it to set things like IP and such), ad reinstall
with both printers attached. That seemed to have done the trick, although
at one stage Windows now refused to print from the 2nd printer (and linux
would now do both :-), but a removal of that driver on the PC and
rebooting + adding the driver seemed to fix that. In the end, as expected,
I can now talk to both printers from both Windows and Linux.

My problem was that I added a machine later, and never properly got
that new setup writting in the firmware of the printserver.

- peter


On Tue, 18 Jul 2000, Maxwell Spangler wrote:

> On Tue, 18 Jul 2000, Peter Teuben wrote:
> 
> > Back in January I believe it was I had a conversation with somebody
> > on this list about printservers. Like him, I decided to buy the 
> > Netgear PS110 printserver, it's been very useful!
> 
> Stephane Greene and I have those, among others.
> 
> >  This printserver has to be initialized (e.g. IP and such) using windows,
> > but works fine from within linux. The PS110 can handle two printers, but
> > now that I have finally hooked up this second printer, all my output still
> > winds up on #1....
> > 
> > Here's the relevant section from the /etc/printcap file:
> > 
> > ps2:\
> > 	:sd=/var/spool/lpd/lp:\
> > 	:mx#0:\
> > 	:sh:\
> > 	:rm=192.168.1.101:\
> > 	:rp=P2:
> > 
> > Somebody on comp.os.linux.hardware suggested I change P2 (physical-2)
> > by L2 (logical-2), but that didn't seem to change the situation.
> > 
> > My setup works fine in windows, i can talk to both printers, so the
> > basic wiring and such seems to be ok. I also talked to netgear
> > support, but they claimed they were working on the unix document,
> > but had not finished it.
> > 
> > So, who got this working again, and if so, what did I do wrong?
> 
> This is the right approach.  The PS110 print server box itself has one ip
> address and the rp= parameter that names a printer is used as part of the lpr
> protocol to determine which port will be used for printing.
> 
> Try changing P2 to L2 and see if that works?  Here's my printcap from a SCO
> system in a remote office that prints to both ports on a PS110 box.  Note that
> port one has been renamed "np1" on the PS110 using the Windows configuration
> program.  The second port hasn't been modified, and accessing it with "L2"
> seems to work.. 
> 
> # Remote Line Printer (BSD format)
> np1:\
>   :lp=:rm=netprint1.g.com:rp=np1:sd=/usr/spool/lpd/np1:
> np2:\
>   :lp=:rm=netprint1.g.com:rp=L2:sd=/usr/spool/lpd/np2:
> lp:\
>   :lp=:rm=wx.g.com:rp=lp:sd=/usr/spool/lpd/lp:
> 
> Remember, that's SCO Unix /etc/printcap, not linux.
> 
> -------------------------------------------------------------------------------
> Maxwell Spangler                         "Don't take the penguin too seriously.
> Program Writer                       It's supposed to be kind of goofy and fun,
> Greenbelt, Maryland, U.S.A.                      that's the whole point" - l.t.
>