Dan, > Double-checked the paths, but saw the same thing. > > address@hidden ~]$ whoami > ldm_test > address@hidden ~]$ which ldmping > /usr/local/ldm_test/bin/ldmping > > address@hidden ~]$ /usr/local/ldm_test/bin/ldmping -i0 > Jan 31 20:45:56 INFO: State Elapsed Port Remote_Host > rpc_stat > Jan 31 20:45:56 INFO: Resolving localhost to 127.0.0.1 took 0.000355 seconds > address@hidden ~]$ > address@hidden ~]$ /usr/local/ldm_test/bin/ldmping -i0 188.8.131.52 > Jan 31 20:46:11 INFO: State Elapsed Port Remote_Host > rpc_stat > Jan 31 20:46:11 INFO: RESPONDING 0.001313 388 184.108.40.206 Actually, you didn't see the same thing. Only the "ldm" user's ldmping(1) utility indicated that it connected to an LDM server. > Now for both the ldm user and the ldm_test user they are set to the same IP > 220.127.116.11. So that when the ldmping is running it passed that IP. Is > that a problem? Having the same IP address isn't a problem because of the different port numbers. > Thanks > Dan Regards, Steve Emmerson Ticket Details =================== Ticket ID: NUP-437021 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.