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.
>From: Marcello Magaldi <address@hidden> >Organization: ? >Keywords: 200206131630.g5DGUYJ15649 netCDF FTP Marcello, >I can't download the pre-built netCDF 3.5.0 libraries for Win32 systems. >Also, it is impossible to download the file to do my own source and the >WIN32_README.TXT file via FTP. It's a my problem or yours? I just verified that I can FTP the netCDF 3.5.0 libraries for Win32 systems from a machine that is not located in our domain, so there is no systematic problem on our end. Here is the sequence that I used: ftp ftp.unidata.ucar.edu <user> anonymous <pass> your_full_email_address cd pub/netcdf/contrib/win32 binary get netcdf-3.5.0.win32bin.ZIP quit The transaction messages looked like: ftp> get netcdf-3.5.0.win32bin.ZIP 200 PORT command successful. 150 Opening BINARY mode data connection for netcdf-3.5.0.win32bin.ZIP (349990 bytes). 226 Transfer complete. local: netcdf-3.5.0.win32bin.ZIP remote: netcdf-3.5.0.win32bin.ZIP One thing we do enforce is a forward and reverse name lookup for machines FTPing to our site. If you were trying to FTP from a machine that this can not be done for, you will be denied. For instance, I just checked to see if this was the case for area.ba.cnr.it (the machine your email originated from), and it looks like it may present a problem: %nslookup area.ba.cnr.it Server: laraine.unidata.ucar.edu Address: 128.117.140.62 Non-authoritative answer: Name: area.ba.cnr.it Address: 194.119.200.100 % nslookup 194.119.200.100 Server: laraine.unidata.ucar.edu Address: 128.117.140.62 Name: area.area.ba.cnr.it Address: 194.119.200.100 Notice how the forward lookup (name -> IP) gives the machine IP as 194.119.200.100. When the reverse lookup is done, the name comes back as area.area.ba.cnr.it which is not the same as area.ba.cnr.it. I also looked in our FTP logs and see a machine from ba.cnr.it connecting and successfully downloading the standard netCDF distribution, netcdf.tar.Z: Jun 11 03:21:44 laraine.unidata.ucar.edu ftpd[7254]: ANONYMOUS FTP LOGIN FROM ri cercatori05.isec.ba.cnr.it [194.119.206.34], isecfs21@ Jun 11 03:21:44 laraine.unidata.ucar.edu ftpd[7254]: CWD pub/netcdf Jun 11 03:21:45 laraine.unidata.ucar.edu ftpd[7254]: TYPE Image Jun 11 03:21:45 laraine.unidata.ucar.edu ftpd[7254]: PORT Jun 11 03:21:45 laraine.unidata.ucar.edu ftpd[7254]: RETR netcdf.tar.Z Jun 11 03:22:22 laraine.unidata.ucar.edu ftpd[7254]: QUIT Was this you? I do not, however, see any attempt to download anything from the pub/netcdf/contrib/win32 directory. When did you try your FTP? >Thanks a lot, >Marcello Magaldi Tom Yoksas