Michael, > Some additional info...if I run ldmping, eventually the connection responds > but after several time-outs. > > address@hidden etc]$ ldmping ldm-11.crh.noaa.gov > Apr 14 18:05:12 INFO: State Elapsed Port Remote_Host > rpc_stat > Apr 14 18:05:12 INFO: Resolving ldm-11.crh.noaa.gov to 220.127.116.11 took > 0.000395 seconds > Apr 14 18:05:22 ERROR: H_CLNTED 10.000252 388 ldm-11.crh.noaa.gov > select: RPC: Timed out > Apr 14 18:05:57 ERROR: H_CLNTED 10.000015 388 ldm-11.crh.noaa.gov > select: RPC: Timed out > Apr 14 18:06:32 ERROR: H_CLNTED 10.000142 388 ldm-11.crh.noaa.gov > select: RPC: Timed out > Apr 14 18:06:57 INFO: RESPONDING 0.000164 388 ldm-11.crh.noaa.gov > Apr 14 18:07:22 INFO: RESPONDING 0.000175 388 ldm-11.crh.noaa.gov Very odd problem. I suspect a networking problem (e.g., DNS server, firewall IP rules). It looks like your TCP stack is set-up for a 10 second timeout. That seems a little short (30 seconds is more reasonable). Can you ping(1) ldm-11 from webdata-1? How long does it take? Please send me the output from the command "ldmping localhost" on the system on which it doesn't work. Give the output two minutes to accumulation. Regards, Steve Emmerson Ticket Details =================== Ticket ID: LXP-916564 Department: Support LDM Priority: Normal Status: Closed
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly 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.