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.
Jacob, I am sure you have done all of these things, but just to step through some more obvious items: 1) are you sure the downstream.hostname equates to ##.##.##.##? In other words, if they are on separate subnets, is the downstream being NAT'd to a router or switch interface IP that is different than the local IP? 2) if you replace ##.##.##.## with downstream.hostname, does that change the success/failure of the attempt? 3) do you have success using pqing to test the connectivity? Finally, if you do a traceroute from your upstream vs. your downstream, do they show the same path? Stonie +----------------------------------------------------------------+ * Stonie Cooper, PhD UCAR Unidata Program * * Software Engineer III P.O. Box 3000 * * address@hidden Boulder, CO 80307 * * Unidata WWW Service http://www.unidata.ucar.edu/ * +----------------------------------------------------------------+ Ticket Details =================== Ticket ID: VVD-531462 Department: Support LDM Priority: Normal Status: Open =================== NOTE: All email exchanges with NSF 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.