[Info-vax] LPD problems

[jbriggs444 at gmail.com]

On Apr 13, 5:00 pm, "Richard B. Gilbert" <rgilber... at comcast.net>
wrote:
> jbriggs... at gmail.com wrote:
> > On Apr 13, 1:31 pm, tadamsmar <tadams... at yahoo.com> wrote:
> >> The versions are:
>
> >> DEC AXPVMS OPENVMS V7.3-2            Platform    Installed
> >> DEC AXPVMS TCPIP V5.4-15             Full LP     Installed
>
> >> I have not used LPD before.
>
> >> I am trying to print via a Microsoft server.
>
> >> I have been told the server address and queue name.  The Microsoft
> >> server is administered by another group
>
> >> I enabled and started LPD/LPR via TCPIP$CONFIG
>
> >> I set up the queue on VMS using  TCPIP$LPRSETUP
>
> >> when I try to print, I get:
>
> >> LPD Retrying failed job: LOGIN Number: 464 User: SYSTEM Status:
> >> %SYSTEM-F-REJECT
> >> , connect to network object rejected
>
> >> I can ping the address of the server.
>
> >> Any ideas on how to troubleshoot this?
>
> > $ telnet <serverip> 515
>
> > If it says "connection refused" then the Windows server isn't
> > listening.  You can either print directly to the printer's JetDirect
> > card (or equivalent) or install and configure LPR/LPD on the Windows
> > server.
>
> I think "connection refused" translates as "Hell no! Go away!"

"Connection refused" means "I sent a TCP SYN to the server IP address
and got back a TCP RST"

This situation almost always means that the server at the specified IP
address has no service listening on the TCP port number in question.

It can also mean that there is a firewall in the way that is
configured to reject connections by sending a spoofed RST back to the
client instead of simply dropping the traffic on the floor.

Either way, "Hell no! Go away!" is an apt phrase.

>
> If the printer is connected to the network you should be able to talk to
>   the printer using TCP/IP.

We are now told that the network is partitioned by one or more dual-
homed gateways with IP forwarding disabled.  If the client attempted
to connect directly to the printer in such an environment I would
expect "connect failed" or "connection timed out" or similar.