Re: Networking a printer through a router

On Wed, 6 Jul 2005 21:02:00 UTC, pacgeo@xxxxxxxxx wrote:

> Before I start down the wrong path, could you advise me on a couple of
> items.
>
> 1. What is the LPD server? Would that be the address of my router? I
> assume when the help file describes this as the destination printer or
> print server, the router would be considered the printe server?

No. The router is just the router. It is entirely transparent to this.
The only place it shows up is as the object of the default route in
your TCPIP notebook. Thereafter you can treat it as a straight piece
of wire. The LPD server is the computer which hosts the LPD printer...
the printer which is shared on the network. The LPD server may be a
computer or just a little print server ( or internal card) which goes
between your Cat-5 cable and your printer. Some (like the DLink 101)
are the size of a pack of cards and plug directly into the Centronics
parallel cable socket on the printer.

You normally use a browser to give the thing an address somewhere in
the range which your router is set to... ie 192.168.1.101 if your
router is set to 192.168.1.1. If it is a full computer then it is set
in the TCPIP notebook.

Next, on the client computer(s), you need lpd and lprportd set to
autostart in the TCPIP notebook. Note that lpd can be started by inetd
but lprportd cannot.
The SPLR software is slightly different but not greatly.

Next you need to create a printer instance (NetPrinter) so you can
route program output to the printer.
Using the local printer template, create a printer, but on the ports
page, select /pipe/lpd0 as the output port. Right click on that port
icon and select Properties.
You fill in the IP address for the LPD server (192.168.1.100 as above)
and the port name for the LPD printer. For my Dlink it is
PS-578D0B-P1.

If you run DOS or Win programs which do not understand pipes, you
create a local printer which outputs on LPT2 and then (right click on
the LPT2 port icon) redirect the output to /pipe/lpd0. The DOS program
thinks it is talking to hardware, while the OS takes care of sending
output to the print server.

Now when you print from client machine you just select the correct
printer instance.

If you do this for a printer connected to a networked computer, you
should be careful to have both computers use the same printer driver
version. The 'name of the printer' for a printer connected to a
networked computer is the share name...ie whatever name you would use
in a 'net use' command.

Geoff




.

Relevant Pages

  • Re: Port Forwarding through router to print server
    ... I am running a Windows XP SP2 HOME wired network of desktop machines ... attached an iogear GPS21U single port USB print server to the network ... I have gone into the router and enabled port forwarding to the IP ...
    (microsoft.public.windowsxp.print_fax)
  • Re: parallel adapter
    ... via a router, add a pocket print server to the printer, ethernet cable from print server to port on router, and then set up the printer as a tcp/ip printer on the laptop. ... For some reason we had a bunch of them in the lab at a company I worked at back in the 1990's, as we used them for some sort of development we were doing. ...
    (comp.sys.laptops)
  • Re: Set up IPP Printer
    ... Add new port ... The utility is unable to detect the print server on the ... computers plugged into router 2. ... is there some firewall seting in the routers that I need so ...
    (microsoft.public.windowsxp.general)
  • Re: USB to ethernet cable
    ... Have a home network consisting of a PC connected by cable to my router, and a laptop that connects wirelessly. ... I have read about an adapter cable that may allow me to connect these devices to my router so they can be visible across the network. ... You need a Print Server for each printer, like HP Jetdirect, and some sort of box with an OS for the external HDD. ... DLink do a "pocket" print server that sits directly on the parallel port on the printer. ...
    (microsoft.public.windowsxp.network_web)
  • Re: OS X printing to FreeBSD server using apsfilter. . .
    ... and I realize I'm stuck with CUPS on the Mac. ... > CUPS server...Just on a different port. ... you need to tell CUPS it's printing to a LPD server on the ... > a section just for Mac OSX here: ...
    (comp.unix.bsd.freebsd.misc)
Loading