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.
Mike, ping doesn't require a DNS lookup, so it will work. ldmping requires a connection to the LDM which does a forward and reverse DNS lookup for authentication -- so DNS is what's causing this problem too. mike On Mar 10, 8:18am, Mike Voss wrote: > Subject: Re: 20030309: thelma > Steve, > Thanks for the reply. I agree there is some DNS problem, which we haven't > resolved. I was out of town and not in a good trouble shooting enviroment. > However, some things I don't understand, eg, I can ping thelma, but not > ldmping it... while I can do both for say typhoon at UCLA...? Anyhow, I'm > sure it's our problem, but these clues were throwing me off. > > ---- > rossby:~/etc>ping thelma.ucar.edu > thelma.ucar.edu is alive > rossby:~/etc>ldmping thelma.ucar.edu > Mar 10 16:10:08 State Elapsed Port Remote_Host > rpc_stat > Mar 10 16:10:18 SVC_UNAVAIL 9.991735 0 thelma.ucar.edu > h_clnt_create(thelma.ucar.edu): Timed out while creating connection > ^C > rossby:~/etc>ldmping typhoon.atmos.ucla.edu > Mar 10 16:14:15 State Elapsed Port Remote_Host > rpc_stat > Mar 10 16:14:16 RESPONDING 0.509260 388 typhoon.atmos.ucla.edu > ^C > rossby:~/etc>ldmping thelma.ucar.edu > Mar 10 16:14:24 State Elapsed Port Remote_Host > rpc_stat > ^C > rossby:~/etc> > > thanks, > -Mike