Hi Scott, We have you as aqua.nsstc.uah.edu..and I believe that to be correct. Do you still have an "ALLOW" line for Neil's machine: coriolis.met.tamu.edu Have there been any changes to your LDM recently that could explain Neil's denial? Please cc me on future correspondence. Thanks, -Jeff ____________________________ _____________________ Jeff Weber address@hidden Unidata Support PH:303-497-8676 NWS-COMET Case Study Library FX:303-497-8690 University Corp for Atmospheric Research 3300 Mitchell Ln http://www.unidata.ucar.edu/staff/jweber Boulder,Co 80307-3000 ________________________________________ ______________________ On Fri, 9 Feb 2001, Unidata Support wrote: > > > Jeff, > > The stats arriving here from uah are from aqua.nsstc.uah.edu > and the machine accepts an ldmping from us. > It appears they have changed their subnet name. > Neil has tried the new name and gets rejected. > > Chiz > > ------- Forwarded Message > > >To: address@hidden > >From: "Neil R. Smith" <address@hidden> > >Subject: IP for aqua.atmos.uah.edu? > >Organization: UCAR/Unidata > >Keywords: 200102091927.f19JRwL08622 > > Hi folks, > aqua.atmos.uah.edu is suppose to be our failover. I noticed recent > occasions logged for our ldm that both primary and failover had > failed. Well, I then noticed that I cannot get a name/IP resolution > for aqua. Why, I don't know. But if aqua.atmos is still a valid > ldm upstream server for us, then maybe I can put its IP in our hosts > file and/or refer to it by IP in our ldmd.aqua.atmos.uah.edu failover > conf. file. > > I don't see aqua.atmos.uah.edu listed in the current FOS topology > as being an IDD site (only as failover for several of us) whereas > there is an aqua.nsstc.uah.edu. I tried that site in our ldmd.conf > and got access denied. Any ideas on this? > > Thanks, -Neil > -- > Neil R. Smith, Comp. Sys. Mngr. address@hidden > Dept. Atmospheric Sci., Texas A&M Univ. 979/845-6272 FAX:979/862-4466 > > > ------- End of Forwarded Message > >
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.