20040401: one of the Suominet systems LDM's not using 388

Teresa,

The ~ldm/bin/rpc.ldmd program must be installed setuid root
in order to connect to port 388. Verify that the rpc.ldmd
on the machine in question is owned by root and had mode 4755, ie:
> ls -l rpc.ldmd
-rwsr-xr-x    1 root     ustaff     350484 Jul 23  2003 rpc.ldmd

If not, then as the administration user, do:
chown root rpc.ldmd
and
chmod 4755 rpc.ldmd

Steve Chiswell
Unidata User SUpport



>From: Teresa Van Hove <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200404020139.i321daCT028689

>Hi UNIDATA support,
>
>We have a situation where one of the SUOMINET cpu's was moved to a 
>new ip# and ever since LDM is not going through.  They have port 388 
>, and port 111 open for us; but it looks like their local LDM is not 
>using port 388, it using port 1067 (and so I think our UCAR firewall 
>is blocking their response?)  -see the snippet below from their sys 
>admin running ldmping to this Suominet CPU from an outside network 
>in Australia.
>
>Our ldmpings
>give:
>bash$ ldmping 134.190.6.4
>Apr 02 01:35:41      State    Elapsed Port   Remote_Host 
>rpc_stat
>Apr 02 01:35:53      NAMED  12.138525    0   134.190.6.4  can't 
>contact portmapper: RPC: Timed out
>
>
>So my question is what steps should be taken to get this LDM
>onto, or back onto, port 388.  The standard SUOMINET ldm vs, 
>ldm-5.1.2 is what is installed on this CPU.  I'd prefer to keep
>it the same as the rest of the Suomi network but I can upgrade if it 
>thats going to be necessary.
>
>thanks,
>Teresa
>
>
>> When you do an ldmping, the ldmping program connects to the portmapper socke
> t
>>> (port 111 TCP/UDP) on 130.194.6.4 - then the portmapper tells the ldmping
>>> program what port the rpc service 'ldmd' is listening on.
>>> 
>>> Hence when I do an ldmping from my external internet connection, right now 
> it
>>> says --
>>> 
>>> # ldmping 130.194.6.4
>>> Apr 01 22:40:20      State    Elapsed Port   Remote_Host           rpc_stat
>>> Apr 01 22:40:20 RESPONDING   0.161440 1067   130.194.6.4
>>> 
>>> Now, when you look at your message you are actually getting from ldmping
>>> it is saying "Can't contact portmapper". Which means it can't actually find
>>> out whatever port the ldm service is running on.
>
>
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publically available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.