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.
Steve Emmerson wrote: > > Robert, > > >Date: Tue, 12 Aug 2003 13:02:22 -0500 > >From: Robert Leche <address@hidden> > >Organization: SRCC > >To: Unidata Support <address@hidden>, > >To: ldm-users <address@hidden> > >Subject: Problems connecting behind a firewall version 6 > > The above message contained the following: > > > We ran into a problem with our LDM system: Hurricane.srcc.lsu.edu. > > It could also be that there used to be a mapping from 204.196.102.99 > to an ALLOW-ed hostname in the system configuration file "/etc/hosts". > If this entry was removed, then you would see the behavior you've > encountered. > > You might try adding such a mapping if one doesn't exist. > > Regards, > Steve Emmerson Hi Bob, FWIW, I think that you can test these possibilities simply by running nslookup or some variant thereof. It's my experience that if nslookup works then the LDM will resolve addresses properly. Anne -- *************************************************** Anne Wilson UCAR Unidata Program address@hidden P.O. Box 3000 Boulder, CO 80307 ---------------------------------------------------- Unidata WWW server http://www.unidata.ucar.edu/ ****************************************************