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.
Art, I think the problem is on your end, around your psc.vbns router. I would contact your network folks asap. I did a ping and a traceroute, plus your traceroutes confirms the same situation. RObb... (thelma:ldm) 109 % ping navier.meteo.psu.edu PING navier.meteo.psu.edu (128.118.28.2): 56 data bytes ----navier.meteo.psu.edu PING Statistics---- 39 packets transmitted, 0 packets received, 100.0% packet loss (thelma:ldm) 110 % traceroute navier.meteo.psu.edu traceroute to navier.meteo.psu.edu (128.118.28.2), 30 hops max, 40 byte packets 1 vbnsr-dmzfnet (192.52.106.10) 5 ms 4 ms 2 ms 2 cs-atm6-0-501.dnj.vbns.net (204.147.130.205) 3 ms 4 ms 3 ms 3 jn1-at1-0-0-0.dnj.vbns.net (204.147.136.82) 4 ms (ttl=252!) 3 ms (ttl=252!) 3 ms (ttl=252!) 4 cs-atm0-0-14.psc.vbns.net (204.147.131.173) 43 ms * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * (thelma:ldm) 111 % On Wed, 29 Dec 1999, Unidata Support wrote: > >To: address@hidden > >From: address@hidden (Arthur A. Person) > >Subject: network access problems > >Organization: . > >Keywords: 199912291719.KAA11801 > > Hi... > I lost connectivity from navier.meteo.psu.edu to thelma.ucar.edu > back on the 22nd around 21Z. When I ping thelma I get: > > ICMP Time exceeded in transit from ns-ga006.psc.vbns.net (204.147.130.1) > for icmp from navier (128.118.28.2) to thelma.ucar.edu (192.52.106.21) > > When I do a traceroute, I get: > > traceroute to thelma.ucar.edu (192.52.106.21), 30 hops max, 40 byte packets > 1 128.118.28.1 (128.118.28.1) 1.085 ms 0.999 ms 0.586 ms > 2 172.28.20.1 (172.28.20.1) 1.244 ms 1.120 ms 1.050 ms > 3 Telecom2-ATM5-0-0.1.gw.psu.edu (128.118.44.5) 2.558 ms 1.304 ms 1.245 > ms > 4 198.32.224.47 (198.32.224.47) 7.115 ms 5.687 ms 7.897 ms > 5 ns-ga006.psc.vbns.net (204.147.130.1) 6.009 ms 6.275 ms 5.884 ms > 6 cs-atm0-0-7.psc.vbns.net (204.147.130.2) 6.395 ms 6.116 ms 5.985 ms > 7 ns-ga006.psc.vbns.net (204.147.130.1) 6.239 ms 6.349 ms 6.198 ms > 8 cs-atm0-0-7.psc.vbns.net (204.147.130.2) 6.567 ms 6.780 ms 6.475 ms > 9 ns-ga006.psc.vbns.net (204.147.130.1) 6.575 ms 7.789 ms 6.745 ms > 10 cs-atm0-0-7.psc.vbns.net (204.147.130.2) 7.343 ms 6.941 ms 6.651 ms > 11 ns-ga006.psc.vbns.net (204.147.130.1) 7.074 ms 7.328 ms 7.166 ms > 12 cs-atm0-0-7.psc.vbns.net (204.147.130.2) 7.178 ms 7.325 ms 7.404 ms > 13 ns-ga006.psc.vbns.net (204.147.130.1) 6.987 ms 7.426 ms 7.554 ms > 14 cs-atm0-0-7.psc.vbns.net (204.147.130.2) 7.684 ms 7.628 ms 8.115 ms > 15 ns-ga006.psc.vbns.net (204.147.130.1) 7.895 ms 8.064 ms 8.751 ms > 16 cs-atm0-0-7.psc.vbns.net (204.147.130.2) 8.856 ms 7.974 ms 7.939 ms > 17 ns-ga006.psc.vbns.net (204.147.130.1) 8.423 ms 8.752 ms 8.335 ms > 18 cs-atm0-0-7.psc.vbns.net (204.147.130.2) 9.899 ms 8.623 ms 8.585 ms > 19 ns-ga006.psc.vbns.net (204.147.130.1) 8.715 ms 9.683 ms 9.622 ms > 20 cs-atm0-0-7.psc.vbns.net (204.147.130.2) 11.155 ms 8.734 ms 9.074 ms > 21 ns-ga006.psc.vbns.net (204.147.130.1) 9.531 ms 9.878 ms 9.364 ms > 22 cs-atm0-0-7.psc.vbns.net (204.147.130.2) 12.615 ms 9.041 ms 9.272 ms > 23 ns-ga006.psc.vbns.net (204.147.130.1) 9.727 ms 9.910 ms 9.879 ms > 24 cs-atm0-0-7.psc.vbns.net (204.147.130.2) 9.962 ms 10.073 ms 10.068 ms > 25 ns-ga006.psc.vbns.net (204.147.130.1) 10.235 ms 9.847 ms 10.202 ms > 26 cs-atm0-0-7.psc.vbns.net (204.147.130.2) 12.519 ms 10.464 ms 10.963 ms > 27 ns-ga006.psc.vbns.net (204.147.130.1) 11.243 ms 10.410 ms 10.670 ms > 28 cs-atm0-0-7.psc.vbns.net (204.147.130.2) 10.926 ms 10.726 ms 10.576 ms > 29 ns-ga006.psc.vbns.net (204.147.130.1) 10.799 ms 11.315 ms 10.464 ms > 30 cs-atm0-0-7.psc.vbns.net (204.147.130.2) 11.240 ms 11.127 ms 11.055 ms > > To temporarily remedy the problem, I switched to iita.rap.ucar.edu for > a feed. This worked fine until about 10Z the 25th when data stopped. > iita pings fine, but in the ldm logs, it gave an access denied, as though > someone had pulled the plug (unless the ldm had quit). As a third resort > I pointed the navier ldm to dusk.ssec.wisc.edu which worked and remains > there now. If I do a ping/traceroute from another system, e.g. > stokes.meteo.psu.edu, it seems normal, so it's as though something > specific has happened to the navier address regarding connectivity. > > Any ideas? > > Thanks. > > Art. > > > Arthur A. Person > Research Assistant, System Administrator > Penn State Department of Meteorology > email: address@hidden, phone: 814-863-1563 > =============================================================================== Robb Kambic Unidata Program Center Software Engineer III Univ. Corp for Atmospheric Research address@hidden WWW: http://www.unidata.ucar.edu/ ===============================================================================