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.
>Organization: ? >Keywords: 199505111444.AA18905 netCDF mirror site Hi Jens, > Is there a mirror for the actual netcdf stuff, maybe in europe? The > connection to your ftp-site is extremly slow and I haven't been able > to get ncbrowse.pro (~70kB), not to mention the library. I've tried > a -c5093@ this morning without success. No sorry, I don't know of any mirror site. Yours is the first report I have seen of a slow FTP connection to our site. We have a high-bandwidth connection to the Internet. I suspect you are seeing symptoms of a temporary problem and that you will have better luck trying it at some other time. I just tried to ping to another host in Deutschland with a netCDF user on our mailing list and it indicates fairly high packet loss: % ping -s kirk.es.go.dlr.de PING kirk.es.go.dlr.de: 56 data bytes 64 bytes from kirk.es.go.dlr.de (129.247.79.2): icmp_seq=1. time=1558. ms 64 bytes from kirk.es.go.dlr.de (129.247.79.2): icmp_seq=2. time=1153. ms 64 bytes from kirk.es.go.dlr.de (129.247.79.2): icmp_seq=5. time=1042. ms 64 bytes from kirk.es.go.dlr.de (129.247.79.2): icmp_seq=8. time=753. ms 64 bytes from kirk.es.go.dlr.de (129.247.79.2): icmp_seq=9. time=1013. ms 64 bytes from kirk.es.go.dlr.de (129.247.79.2): icmp_seq=11. time=736. ms 64 bytes from kirk.es.go.dlr.de (129.247.79.2): icmp_seq=26. time=2309. ms 64 bytes from kirk.es.go.dlr.de (129.247.79.2): icmp_seq=29. time=2003. ms 64 bytes from kirk.es.go.dlr.de (129.247.79.2): icmp_seq=31. time=1902. ms 64 bytes from kirk.es.go.dlr.de (129.247.79.2): icmp_seq=32. time=2913. ms ----kirk.es.go.dlr.de PING Statistics---- 36 packets transmitted, 10 packets received, 72% packet loss round-trip (ms) min/avg/max = 736/1538/2913 A "traceroute" shows me the problem is not local, but a problem in routing packets somewhere "out there", perhaps the routing hop in the Atlantic link. ______________________________________________________________________________ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu