Re: [ldm-users] question about UDP 111

• To: Mike Barth <Michael.F.Barth@xxxxxxxx>
• Subject: Re: [ldm-users] question about UDP 111
• From: Chris MacDermaid <Chris.MacDermaid@xxxxxxxx>
• Date: Fri, 23 Apr 2010 19:01:23 -0600

Mike,

Port 111 is the sunrpc port. This is also know as the portmapper because
it provides a mapping between available services and their ports.

Port 111 isn't needed for LDM. From what I understand, a LDM client
first tries to connect to port 388. If that fails the client then tries
to connect using the portmapper service on port 111. In your case, it
appears the connection on port 388 is failing for some reason.

For the LDM servers we run in the Central Facility at GSD, port 111 is
blocked at our firewall. Blocking port 111 hasn't caused us any problems
so far. Having port 111 open is a well-known security risk.

Chris MacDermaid



On 4/23/10 2:58 PM, Mike Barth wrote:
> Hi,
> 
> I'm having problems successfully connecting to an ldm server behind
> a firewall.  We can't ldmping in either direction as well.  Their
> firewall admin says:
> 
> "I see traffic on 388 successful, but I am seeing a UDP 111 attempt.
> We have setup TCP 111, which I believe we should be using.  Is there a
> way to configure that application to use TCP 111 instead of UDP 111?"
> 
> Does ldm do UDP 111 attempts?  If so (I don't know what this means anyway),
> is there a way to configure it to use TCP 111 instead?
> 
> Thanks,
> 
> Mike
> 
> _______________________________________________
> ldm-users mailing list
> ldm-users@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe,  visit:
> http://www.unidata.ucar.edu/mailing_lists/

• Follow-Ups:
  • Re: [ldm-users] question about UDP 111
    • From: Peter Laws

• References:
  • [ldm-users] question about UDP 111
    • From: Mike Barth