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.
Hi João, re: > Thanks for the response, No worries. re: try telnet 128.104.109.190 112 to test the connection to the ADDE server > It seems you are on to something. > > [mcidas@localhost ~]$ telnet 128.104.109.190 112 > Trying 128.104.109.190... > telnet: connect to address 128.104.109.190: Connection timed out Hmm... this is pretty weird. What does 'ping' have to say: ping 128.104.109.190 re: > Things are slightly complicated here, I will have to ask permission to use > the telnet protocol on the 112 port. It is pretty unusual for outbound requests to be blocked... incoming yes, outgoing rare (but the U.S. military does this a lot). re: > Thanks! No worries. Be aware that all current ADDE servers listen on port 112, so unblocking outbound requests to port 112 will be important if you want to access data from remote servers. Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: VZA-525318 Department: Support McIDAS Priority: Normal Status: Closed