[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 18:00:22 -0700
Evan,

> I think port 388 on 129.82.225.8 needs to be opened using iptables (the
> IT guys have the root password). netstat shows 129.82.225.8 is listening
> on port 388 when the LDM is running but no other machine can telnet to
> 129.82.225.8 on port 388.

I've seen this many times before: firewall rules causing packets to or
from port 388 to be thrown into the bitbucket.

Good luck.

Regards,
Steve Emmerson

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