[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[CONDUIT #JNG-511712]: Access to CONDUIT Datastream Failing
- Subject: [CONDUIT #JNG-511712]: Access to CONDUIT Datastream Failing
- Date: Fri, 17 Jun 2011 12:07:24 -0600
Hi Randy,
re:
> Is there a specific protocol that the CONDUIT data is fed through.
Yes, the protocol used by the LDM. The LDM on your machine will make a
request to its upstream feed site on the upstream feed site's port 388.
The port used locally will be randomly chosen, but it will always be
greater than 1024.
re:
> Also, do you know if NSF is on the internet 2 and if so what their IP address
> is?
Yes, the CONDUIT toplevel IDD node at NSF is on I2. Its name and IP address
are:
idd.cise-nsf.gov <-> 192.12.209.62
As I noted in a previous email, the problem is likely that your machine running
the LDM that is trying to request data from idd.cise-nsf.gov does not have
both forward and reverse DNS. I asked Martha/you in a previous email to
send us the fully qualified name and IP address of your machine. If reverse
DNS (IP -> name) does not exist for your machine, we can hardwire a name <-> IP
address pair in the /etc/hosts file on idd.cise-nsf.gov. We do _not_ want to
do this as it is "brittle", but we can do it to get you going.
re:
> Our network team is asking these questions.
They can lookup the IP address of the machine knowing its name using a tool
like 'nslookup'.
Cheers,
Tom
--
****************************************************************************
Unidata User Support UCAR Unidata Program
(303) 497-8642 P.O. Box 3000
address@hidden Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage http://www.unidata.ucar.edu
****************************************************************************
Ticket Details
===================
Ticket ID: JNG-511712
Department: Support CONDUIT
Priority: Normal
Status: Closed