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

20040518: LDM problem: Denying connection from localhost.loca l domain

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: 20040518: LDM problem: Denying connection from localhost.loca l domain
  • Date: Tue, 18 May 2004 11:48:22 -0600
Rodney,

>Date: Tue, 18 May 2004 10:38:26 -0700
>From: "Jacques, Rodney" <address@hidden>
>Organization: US NAVY/NAVPACMETOCCEN
>To: "'Steve Emmerson'" <address@hidden>
>Subject: RE: 20040518: LDM problem: Denying connection from localhost.loca l 
>domain 
> Keywords: 200405121919.i4CJJRtK023189

The above message contained the following:

> Oops. I forgot that Notepad has problems with character returns. I was under
> the impression that the file was not readable.

I was joking.  Viewing it wasn't a problem.

> I did as you requested. Same answer.
> 
> Access denied by remote server (notifyme)
> 
> Denying connection from granite.npmoc-sd.navy.mil (ldmping)

So, neither an ldmping(1) nor a notifyme(1) executing on Granite was
able to connect to the LDM server running on Granite: both resulted in
"access denied" log messages from the LDM server -- even though the LDM
configuration-file on Granite has ALLOW entries for

    ^localhost

and

    ^granite\.npmoc-sd\.navy\.mil 

And the LDM server was restarted.

Is this correct?  If so, then it's very strange.

You'd better send me the current LDM configuration-file.

Regards,
Steve Emmerson