Hello
I have some urgent work to do needing Novell's website. A traceroute looks like that:
5 62-2-74-177.static.cablecom.ch (62.2.74.177) 6.714 ms 4.109 ms 4.693 ms 6 * * * 7 * * * 8 ch-gva01a-ra1-so-0-0-0.aorta.net (213.46.171.1) 16.105 ms 18.989 ms 18.040 ms 9 fr-par02a-rd1-pos-1-0.aorta.net (213.46.160.25) 40.928 ms 35.799 ms 35.768 ms 10 us-was02a-rd1-pos-1-0.aorta.net (213.46.160.106) 119.989 ms 122.670 ms 116.672 ms 11 us-was02a-ri1-ge-0-0-0-0.aorta.net (213.46.190.190) 131.806 ms 122.311 ms 115.893 ms 12 4.79.168.201 (4.79.168.201) 110.311 ms 109.805 ms 109.514 ms 13 att-level3-oc192.Washington1.Level3.net (4.68.127.154) 111.181 ms att-level3-oc192.Washington1.Level3.net (209.244.219.142) 139.298 ms att-level3-oc192.Washington1.Level3.net (4.68.127.154) 111.104 ms 14 tbr1-p014001.wswdc.ip.att.net (12.123.8.98) 184.822 ms 184.428 ms 229.119 ms 15 tbr1-cl4.sl9mo.ip.att.net (12.122.10.30) 189.862 ms 187.768 ms 201.821 ms 16 tbr1-cl1886.dvmco.ip.att.net (12.122.10.221) 256.620 ms 253.457 ms 184.966 ms 17 gar1-p360.slkut.ip.att.net (12.122.2.237) 182.611 ms 183.261 ms 182.628 ms 18 12.127.106.34 (12.127.106.34) 186.215 ms 184.805 ms 186.362 ms 19 192.94.118.253 (192.94.118.253) 187.123 ms 186.472 ms 183.902 ms [...] 56 192.94.118.253 (192.94.118.253) 189.795 ms 193.477 ms 189.856 ms 57 192.94.118.253 (192.94.118.253) 188.096 ms 189.535 ms 192.687 ms 58 192.94.118.253 (192.94.118.253) 204.426 ms 196.524 ms 194.274 ms 59 192.94.118.253 (192.94.118.253) 189.640 ms 190.107 ms 191.890 ms 60 192.94.118.253 (192.94.118.253) 190.288 ms 193.465 ms 190.228 ms 61 192.94.118.253 (192.94.118.253) 193.451 ms 189.614 ms 190.231 ms 62 192.94.118.253 (192.94.118.253) 190.349 ms 189.512 ms 190.270 ms 63 192.94.118.253 (192.94.118.253) 190.314 ms 189.552 ms 189.553 ms 64 192.94.118.253 (192.94.118.253) 191.027 ms 191.566 ms 200.842 ms
Line 19 to 64 are identical. How on earth can this be done? Wrong netmask maybe?
192.94.118.253 is already at Novell - therefore it's probably slightly OT, in here. But still... maybe somebody from Novell is reading this and is able to help.
Regards Peter
Peter Guhl wrote:
Hello
I have some urgent work to do needing Novell's website. A traceroute looks like that:
www.novell.com works fine from here. (Since when is Novell into mobile stuff?)
5 62-2-74-177.static.cablecom.ch (62.2.74.177) 6.714 ms 4.109 ms 4.693 ms 6 * * * 7 * * *
[..]
Nice firewall-rules breaking ICMP here already....
19 192.94.118.253 (192.94.118.253) 187.123 ms 186.472 ms 183.902 ms [...] Line 19 to 64 are identical. How on earth can this be done? Wrong netmask maybe?
Nopes, just a nice firewall.
192.94.118.253 is already at Novell - therefore it's probably slightly OT, in here. But still... maybe somebody from Novell is reading this and is able to help.
man tcpdump or wireshark your connection to find out more details.
Also in general, problems with websites are better tested by doing a telnet to port 80 of the box and typing a HTTP query...
Greets, Jeroen
On the Thu, Oct 26, 2006 at 07:54:18PM +0100, Jeroen Massar blubbered:
Hi.
5 62-2-74-177.static.cablecom.ch (62.2.74.177) 6.714 ms 4.109 ms 4.693 ms 6 * * * 7 * * *
[..]
Nice firewall-rules breaking ICMP here already....
Braindead and useless. Use tcptraceroute in such cases.
19 192.94.118.253 (192.94.118.253) 187.123 ms 186.472 ms 183.902 ms [...] Line 19 to 64 are identical. How on earth can this be done? Wrong netmask maybe?
Nopes, just a nice firewall.
192.94.118.253 is already at Novell - therefore it's probably slightly OT, in here. But still... maybe somebody from Novell is reading this and is able to help.
man tcpdump or wireshark your connection to find out more details.
Also in general, problems with websites are better tested by doing a telnet to port 80 of the box and typing a HTTP query...
ACK. That way you see if it's unreachable or just a server overload. That and tcptraceroute. =:-)
CU, Venty
-
Jeroen Massar -
Martin Ebnoether -
Peter Guhl