[Info-vax] LPD problems

[etmsreec at yahoo.co.uk]

On 14 Apr, 14:02, 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.
>
> Since I started this thread we established communications with the new
> printer via its parallel port, so figuring this out is now not so
> urgent.  So, I don't think I am going to get fast response from the
> contractor that administers the Windows server.
>
> I still want to use LDP since future printers might not have a
> parallel port, but its not so urgent.
>
>
>
> > > I put the TCPIP version in my original message [...]
>
> >    So you say, but "V5.4-15" and "V5.4 - ECO 4" look different
> > to me, and the latter one tells me more.  It probably doesn't
> > matter here, but note that you're a few ECOs behind.  Around
> > here, for example:
>
> > alp $ tcpip show version
>
> >   HP TCP/IP Services for OpenVMS Alpha Version V5.4 - ECO 7
> >   on a COMPAQ Professional Workstation XP1000 running OpenVMS V7.3-2
>
> Thanks, you just made me realize that the VMS UPDATE patch does not
> include TCPIP.  I should have known that.- Hide quoted text -
>
> - Show quoted text -

FWIW, I think you've stumbled upon the reason VMS guys like using
reverse telnet printing rather than LPD - it's the devil's own job to
debug LPD printing!

Steve