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.
Erick Lorenz wrote: > > Anne: > > I will perform the tests on the syslog you suggested tomorrow. > > For what its worth I discovered that ATM23.ucdavis.edu was deleted from our > campus' name server. > I couldn't ping it if it wasn't in my own host table. A request for > reregistering ATM23 has been sent. I will see if that fixes the problem > although it is sort of moot now that James has configured typhoon with both > forms of the address. > > Thanks > > Erick > > +--------------------------------------------------------------------------+ > | Erick Lorenz, Programmer/Analyst Voice: 530-752-8297 | > | Atmospheric Science FAX: 530-752-1552 | > | Land, Air & Water Resources | > | University of California, Davis e-mail: address@hidden | > +--------------------------------------------------------------------------+ Hi Erick, I'll be interested to hear the outcome of your syslog tests. The name server problem could well be the cause of your connection problem. There are tradeoffs to relying on the name server, as you have seen. Anne -- *************************************************** Anne Wilson UCAR Unidata Program address@hidden P.O. Box 3000 Boulder, CO 80307 ---------------------------------------------------- Unidata WWW server http://www.unidata.ucar.edu/ ****************************************************