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.
>From: address@hidden >Organization: Western Michigan >Keywords: 200007181435.e6IEZAT22632 McIDAS-X -XCD LDM ldm-mcidas intall Leonard, >Try it now. I have the inetd.conf stuff in place. I had to change the >protection on some files and directories in the mcidas account but it >looks like it's nominally working. But we don't have the expertise to >test it. The first thing I always do to test whether or not a remote ADDE server installation is working is test access to the ports it will use: 500 (uncompressed transfers) and 503 (compressed transfers): telnet s418.lab2.cc.wmich.edu 500 Trying... This does not connect like it should, so something is still not done. (Note: the port is not used for telnet; it is just easy to see if services on the port are allowed using telnet). Non-functionality is confirmed by me attempting to do an ADDE function to s418 from a machine here in Unidata and that failing also. A couple of things might be going on: o did you send a HUP to inetd after making the mods to /etc/inetd.conf o I notice that there is a space between 'mcservsh' and '-H' in /etc/inetd.conf on s418. On our machines this is a tab. o since I do not know much about NIS, I can't tell if the services for ports 500 and 503 have been defined. On non-NIS systems, /etc/services will have the following entries: mcserv 500/tcp # McIDAS ADDE port mccompress 503/tcp # McIDAS ADDE compression port Your system does not. I have to believe that this might be the problem. Tom