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.
Tom, > The config file has a "request", "allow" and "accept" setup for this > connection as we need to send files both directions. The ACCEPT entry would only be necessary if the remote site sends your LDM data-products "out-of-the-blue". The rtstats(1) program does this, as does ldmsend(1) and pqsend(1). > I'm not really sure which way the initial contact is, but I think is from > inside to out. > > ldmping results in the error: "RPC: Unable to receive; errno = Connection > reset by peer" An ldmping(1) failure to the remote LDM likely indicates that it doesn't doesn't have an ALLOW entry for your LDM in its configuration-file. What's the output from the command "notifyme -h <remote_LDM>", where "<remote_LDM>" is either the IP address of the remote LDM or its fully-qualified hostname. Regards, Steve Emmerson Ticket Details =================== Ticket ID: YYO-509858 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.