NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
you sneaky dev you! I missed that change. Sent from my iPhoneOn Sep 28, 2009, at 5:08 PM, Steve Emmerson <steve@xxxxxxxxxxxxxxxx> wrote:
Tyler Allison wrote:Personally, I'd rather see it assume 388 and fall back to portmapper/rpcbind in the event of 388 failure, but that's just me :)That's the way the LDM actually works.Accessing the portmapper (port 111) is only an issue if and when accessto port 388 is blocked for some reason (e.g., a firewall rule). Regards, Steve Emmerson LDM Developer _______________________________________________ ldm-users mailing list ldm-users@xxxxxxxxxxxxxxxx For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/
ldm-users archives: