[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #ILT-461435]: No LDM access after hardware change

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.

  • Subject: [LDM #ILT-461435]: No LDM access after hardware change
  • Date: Sat, 21 Feb 2009 10:08:28 -0700
Evan,

> I am actually able to "ping" 129.82.225.8 from another LDM machine
> set-up WITHIN the network but I still get the same errors listed below
> when I "ldmping" the same machine (even from within the network?).
> 
> I contacted the IT support department over here at Colorado State
> University Engineering, but they aren't knowledgeable at all about the
> LDM. Any other ideas??? This problem makes no sense!

Does netstat(1) show that an LDM server is listening on port 388
on host 129.82.225.8 (e.g., "netstat -n --inet --tcp --all | grep 388")?

Can you telnet(1) to port 388 on host 129.82.225.8 from another
system (e.g., "telnet 129.82.225.8 388")?

> Best regards,
> Evan

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: ILT-461435
Department: Support LDM
Priority: Normal
Status: Closed