[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Request for assistance for halo.sci.ccny.cuny.edu
- Subject: Request for assistance for halo.sci.ccny.cuny.edu
- Date: Tue, 06 Aug 2002 17:06:42 -0600
Dear Bob,
I got your email address from Kwan-yin Kong who works for Professor
Hindman at CCNY. I am trying to help Kwan debug a problem with his LDM
software on halo.sci.ccny.cuny.edu. The symptom is that the LDM is
unable to connect outside the local network.
I can ping the remote site to which halo is trying to connect,
striker.atmos.albany.edu. I would like to try a traceroute from halo to
the outside, but halo apparently does not have traceroute installed. In
a traceroute to halo from here (in Boulder) I get this:
/local/ldm% traceroute halo.sci.ccny.cuny.edu
traceroute to halo.sci.ccny.cuny.edu (134.74.52.189), 30 hops max, 40
byte packets
1 flra-n140 (128.117.140.252) 0.451 ms 0.287 ms 0.266 ms
2 gin-n243-80.ucar.edu (128.117.243.81) 0.503 ms 1.313 ms 0.633 ms
3 frgp-gw-1.ucar.edu (128.117.243.34) 1.553 ms 1.613 ms 1.881 ms
4 ucar.edu.ip.att.net (12.124.158.13) 1.544 ms 1.918 ms 2.777 ms
5 gbr1-p60.dvmco.ip.att.net (12.123.36.138) 2.280 ms 1.654 ms 1.358
ms
6 gbr4-p70.dvmco.ip.att.net (12.122.5.21) 2.117 ms 2.641 ms 2.442
ms
7 gbr4-p80.dlstx.ip.att.net (12.122.2.101) 22.258 ms 22.214 ms
23.772 ms
8 gbr3-p60.dlstx.ip.att.net (12.122.1.137) 23.423 ms 22.280 ms
22.587 ms
9 gbr4-p40.attga.ip.att.net (12.122.3.38) 35.924 ms 38.660 ms
37.211 ms
10 gbr4-p10.wswdc.ip.att.net (12.122.2.162) 51.867 ms 50.795 ms
51.075 ms
11 gbr3-p60.wswdc.ip.att.net (12.122.1.129) 50.960 ms 51.033 ms
50.838 ms
12 gbr3-p20.n54ny.ip.att.net (12.122.3.53) 56.778 ms 56.819 ms
56.811 ms
13 gbr1-p100.n54ny.ip.att.net (12.122.1.150) 55.335 ms 55.198 ms
54.953 ms
14 gar1-p360.n54ny.ip.att.net (12.123.1.129) 55.422 ms 55.501 ms
56.049 ms
15 12.125.51.210 (12.125.51.210) 56.903 ms 56.888 ms 57.614 ms
16 at-cpe-cuny.appliedtheory.net (169.130.253.130) 56.726 ms 56.798
ms 56.806 ms
17 128.228.179.52 (128.228.179.52) 57.657 ms 58.177 ms 57.614 ms
18 128.228.179.17 (128.228.179.17) 59.523 ms 58.141 ms 58.169 ms
19 128.228.91.38 (128.228.91.38) 59.296 ms 59.252 ms 60.533 ms
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
I was wondering if perhaps there was a firewall blocking traffic on port
388, but I understand from Xiaodong Yan that port 388 is open in both
directions. However, the last hops on the traceroute indicate either a
firewall or an extremely slow connection. Do you know which it would
be? And, I can't resolve the IP addresses to any name, although I'm
guessing that they are part of the CUNY network.
Then I wondered if perhaps the IP address on halo has changed. Would
you know if that was the case?
Also, today I came across a very interesting situation. The
telecommunications people on a particular campus had installed software
to throttle file sharing. (It was called Packeteer/Packetshaper.)
Turns out that this software caused the LDM to relay at extremely slow
speeds, or not relay at all. Are you using any such software?
Or, do you have any other ideas regarding why halo's LDM can't connect
to the outside?
Thanks very much for your time!
Sincerely,
Anne Wilson
--
***************************************************
Anne Wilson UCAR Unidata Program
address@hidden P.O. Box 3000
Boulder, CO 80307
----------------------------------------------------
Unidata WWW server http://www.unidata.ucar.edu/
****************************************************