[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20031016: LDM 6.0.14 connection to portmap on RedHat 9

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20031016: LDM 6.0.14 connection to portmap on RedHat 9
  • Date: Fri, 17 Oct 2003 10:58:08 -0600
Rita,

>Date: Thu, 16 Oct 2003 16:25:24 -0500
>From: Rita Edwards <address@hidden>
>Organization: UCAR/Unidata
>To: Steve Emmerson <address@hidden>
>Subject: Re: 20031016: LDM 6.0.14 connection to portmap on RedHat 9

The above message contained the following:

> However, the upgraded system flash is not able to get through
> the firewall.  With the firewall guys monitoring the firewall,
> Carl's machine flash attempted a connection to branch.

To the LDM or to the portmapper?

> The
> firewall reported that after the initial connection, flash sent
> branch a fin packet (closing the connection), and then
> reattempted to connnect to branch using a higher level port.

To the LDM or to the portmapper?

> This connection is viewed as a new connection on a higher
> level port number and is not allowed.

Does rpcinfo(1) show that Branch's LDM is registered on port 388, e.g.,

    $ rpcinfo -p motherlode.ucar.edu
       program vers proto   port  service
        100000    4   tcp    111  rpcbind
        100000    3   tcp    111  rpcbind
        100000    2   tcp    111  rpcbind
        100000    4   udp    111  rpcbind
        100000    3   udp    111  rpcbind
        100000    2   udp    111  rpcbind
        300029    6   tcp    388  ldmd
        300029    5   tcp    388  ldmd

Regards,
Steve Emmerson