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

20050210: FTP of netcdf 3.6

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: 20050210: FTP of netcdf 3.6
  • Date: Thu, 10 Feb 2005 07:59:34 -0700
>From: "Bunts, Phillip" <address@hidden>
>Organization: ?
>Keywords: 200502101417.j1AEHdv2020286 netCDF FTP

Hi Flipp,

>i have been unable to get the
>ftp://ftp.unidata.ucar.edu/pub/netcdf/netcdf.tar.gz tarball, do you know
>of a mirror anywhere else? or if the ftp server will be back up any time
>soon?

I just verified that the FTP site is up and working normally by FTPing
the netCDF 3.6.0 distribution from a machine at Texas A&M University
(where I have a login account).

If you are going through the web interface (which fires off an FTP)
and you still have problems, please try the FTP site directly:

machine: ftp.unidata.ucar.edu
user:    anonymous
pass:    address@hidden
directory: pub/netcdf
file:    netcdf-3.6.0.tar.gz

If this doesn't work for you it most likely means that you are trying
to FTP to a directory on your machine in which you do not have write
permission and/or DNS for your machine does not support forward and
reverse name lookup.  We check for the forward/reverse name lookup
to help keep down DoS attacks on our FTP site.  My experience is that
many users machines do not have the DNS support we need, but they
are able to FTP to some other machine in their organization.

>thanks.

No worries.  Please let us know if your FTP attempts fail.

Cheers,

Tom Yoksas
--
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.