[Info-vax] LPD problems

[jbriggs444 at gmail.com]

On Apr 14, 9:02 am, Tom Adams <tadams... at yahoo.com> wrote:
> On Apr 13, 5:22 pm, Steven Schweda <sms.antin... at gmail.com> wrote:
> > Tom Adams wrote:
> > > On Apr 13, 4:04 pm, Jan-Erik Söderholm <jan-erik.soderh... at telia.com>
> > > wrote:
> > > > Tom Adams wrote:
> > > > >> They tell me that LPD is enabled on the Windows server.
>
> > > > > Correction, they told me the printer was enabled for LPD.
>
> > > > Then print to the *printer*, not to the Windows server...
> > > > Which one was you trying to print to ?
>
> >    Yeah.  What he said.
>
> > > The VMS systems are on a laboratory lan that is isolated from just
> > > about everthing, so I typically need to go thru a limited number of
> > > server addresses.
>
> >    Generally speaking, the LPR system needs to be talk to the
> > LPD system if you expect to use it for printing, whether the
> > LPD system is the printer or some other computer.
>
> >    I don't know what "go thru a limited number of server
> > addresses" means in a situation like this.
>
> Now you got me curious how this isolation works. I think its a
> computer with two ethernet cards that does not automatically pass on
> network traffic, but I should ask. We can ftp stuff from the alpha to
> a server and then ftp it out to the other lan.  VMS gets time via ntp
> from a server, but I think the time is set by a microsoft service
> because the time does not behave exactly like a time orginating from
> an ntp original source server.

Your description is very plausible.  One or more "dual-homed" Windows
machines plugged into both the lab network and the main network.  As
long as "IP forwarding" is turned off on the Windows boxes, this will
work well as an isolation technique.

Given that scenario, loading and configuring the LPD _server_
component on the Windows side is the obvious way to go.  Instructions
for doing that appear elsewhere in this thread.