Still more server tests.:-)

[Russ]

You guys have been a huge help in trying to get this thing functioning correctly. I printed out the last thread, and it's been great research material.

I think I've got at least one working consistently now, but since I'm on the same network, my ability to test it is limited to using web proxy's. So, once again, I come to the techno-studs of the DC forum.

Can you guys try http://207.108.218.137 and report on whether or not the site is loading for you? A traceroute, if you have time, would also be nice. Don't bother with a ping, though. For some reason, even though traceroute seems fine, pinging doesn't work.

Thanks!

BTW, in case any of you guys find yourself in the same position, trying to get a server setup, this site has some pretty cool tools.

Russ, NCNE

 

[BurntKooshie]

I'm getting a TA cube page, but you're in "68th place"

 

[Russ]

BK,

It's just a local copy that hasn't been updated. Right now, the real tacube.com is hosted until I actually know what I'm doing.

Russ, NCNE

 

[toph99]

loaded fast
what information did you want from the trace route?

 

[divide by zero]

TA Cube page loads fast and fine.

I'm at work and something at the proxy or firewall point is coming back with "destination unreachable" to ANY tracert I do.

 

[Russ]

Chris,

The most important thing I'm looking for from a traceroute is whether or not it times out after 207.108.218.142. This is the gateway, and the last hop before the server at 137. This was happening quite a bit before, and helped me to know what to zero in on.

Russ, NCNE

 

[toph99]

it does time out after 207.108.218.142


13,157.130.178.94,146ms,uswbel-oc3-1-gw.customer.alter.net,----
14,206.81.192.249,153ms,gig0-0-0.sttl-agw2.sttl.uswest.net,----
15,207.224.249.101,139ms,103.fa0-0-0.sttl-6400-gw5.sttl.uswest.net,----
16,207.108.218.142,162ms,207-108-218-142.customers.uswest.net,----
17,----,Timeout,n/a,----
18,----,Timeout,n/a,----
19,----,Timeout,n/a,----
20,----,Timeout,n/a,----
21,----,Timeout,n/a,----
22,----,Timeout,n/a,----
23,----,Timeout,n/a,----
24,----,Timeout,n/a,----
25,----,Timeout,n/a,----
26,----,Timeout,n/a,----
27,----,Timeout,n/a,----
28,----,Timeout,n/a,----
29,----,Timeout,n/a,----

 

[dawks]

NeoTrace Version 2.12a - Shareware (2-1-2000)
Destination: 207.108.218.137

-#--------------Node Name---------------IP Address------Location-----------RT*--High---Low---Avg-Tot---D-Who
10 194.atm6-0.gw8.sea1.alter.net 152.63.105.229 47.592N,122.325W 55 69 55 59 4 0
11 uswbel-oc3-1-gw.customer.alter.net 157.130.178.94 Unknown 68 69 55 64 4 0
12 gig6-0-0.sttl-agw2.sttl.uswest.net 206.81.192.217 47.608N,122.325W 55 69 55 59 4 0
13 103.fa0-0-0.sttl-6400-gw5.sttl.uswest.net 207.224.249.101 47.608N,122.325W 68 69 68 68 4 0
14 207-108-218-142.customers.uswest.net 207.108.218.142 Unknown 82 83 82 82 4 0
15 207-108-218-137.customers.uswest.net 207.108.218.137 Unknown - 0 0 0 7 8
--------------------------------------------------------------------------------------------------------
*All times in milliseconds (ms), D=Dropped packets
------------------------------------------------------------------------------------------------------------
December 1, 2000 18:19:42
NeoTrace Copyright ©1997-1999 NeoWorx inc
http://www.neoworx.com

 

[MooCow]

page loads up fast, but my tracert gets time outs after about the 18th hop

 

[Rendus]

Loads extremely quickly for me. (Seems to be pure HTML and two GIFs, so I don't see why it wouldn't).

 

[micron]

It loads really fast for me. Here are my tracert results:

Tracing route to 207-108-218-137.customers.uswest.net [207.108.218.137]
over a maximum of 30 hops:

1 110 ms 120 ms 108 ms ******.*****.*** [***.***.***.*]
2 103 ms 102 ms 126 ms 207.91.36.13
3 113 ms 107 ms 100 ms 216.170.24.129
4 213 ms 170 ms 132 ms Serial12-1-1.GW2.KCY1.ALTER.NET [157.130.160.109
]
5 152 ms 159 ms 210 ms 110.ATM2-0.XR1.STL1.ALTER.NET [152.63.68.106]
6 2136 ms 134 ms 157 ms 187.at-2-1-0.TR1.SLT4.ALTER.NET [152.63.89.30]
7 2160 ms 189 ms 176 ms 133.at-5-1-0.TR1.POR3.ALTER.NET [152.63.6.109]
8 171 ms 167 ms 179 ms 197.ATM6-0.XR1.SEA1.ALTER.NET [152.63.104.249]
9 163 ms 181 ms 167 ms 195.ATM4-0.GW8.SEA1.ALTER.NET [152.63.105.217]
10 172 ms 180 ms 170 ms uswbel-oc3-1-gw.customer.alter.net [157.130.178.
94]
11 226 ms 191 ms 180 ms gig0-0-0.sttl-agw1.sttl.uswest.net [206.81.192.2
48]
12 191 ms 199 ms 238 ms 103.fa0-0-0.sttl-6400-gw5.sttl.uswest.net [207.2
24.249.101]
13 214 ms 206 ms 212 ms 207-108-218-142.customers.uswest.net[207.108.21
8.142]
14 * * * Request timed out.

HTH, Micron

 

[Choralone]

I'll add my $.02. It's timing out on me right after 207.108.218.142 as well. But the page loads freakin' fast in general.

 

[vss1980]

yes it loads and this is the tracert to you:





1 1 ms <10 ms <10 ms SERVER [192.168.0.1]
2 8 ms 9 ms 9 ms 172.18.151.254
3 10 ms 9 ms 9 ms not-cam1-a-s10.inet.ntl.com [62.254.1.17]
4 13 ms 10 ms 9 ms not-core-a-pos200.inet.ntl.com [62.254.0.137]
5 19 ms 20 ms 19 ms 62.253.187.222
6 21 ms 20 ms 20 ms lng-bb-b-ge130-0.inet.ntl.com [62.253.188.141]
7 96 ms 97 ms 95 ms mae-east-gw1-atm10.inet.ntl.com [194.168.23.58]
8 104 ms 95 ms 104 ms mae-east-gw1-fa000.inet.ntl.com [194.168.118.221
]
9 95 ms 93 ms 94 ms 902.Serial3-1-1.GW1.TCO1.ALTER.NET [157.130.33.5
7]
10 95 ms 96 ms 94 ms 538.at-3-0-0.XR1.TCO1.ALTER.NET [152.63.38.158]

11 94 ms 96 ms 96 ms 193.at-1-1-0.TR1.DCA6.ALTER.NET [152.63.34.22]
12 173 ms 172 ms 173 ms 121.at-5-0-0.TR1.POR3.ALTER.NET [152.63.2.138]
13 177 ms 177 ms 178 ms 197.ATM6-0.XR1.SEA1.ALTER.NET [152.63.104.249]
14 176 ms 178 ms 176 ms 195.ATM7-0.GW8.SEA1.ALTER.NET [152.63.105.225]
15 179 ms 178 ms 178 ms uswbel-oc3-1-gw.customer.alter.net [157.130.178.
94]
16 179 ms 179 ms 178 ms gig6-0-0.sttl-agw1.sttl.uswest.net [206.81.192.2
16]
17 180 ms 180 ms 182 ms 103.fa0-0-0.sttl-6400-gw5.sttl.uswest.net [207.2
24.249.101]
18 199 ms 198 ms 197 ms 207-108-218-142.customers.uswest.net [207.108.21
8.142]
19 * * * Request timed out.

By any chance Russ, you own/run the computer on ip 207.108.218.142 ?

If this is your host gateway to the computer that the web page is stored on, it looks like the request is not being routed through properly. This could be down to some sort of firewall you have in place, but you'll have to figure it out.

 

[imported_CyberWire]

Tracing route to 207-108-218-137.customers.uswest.net [207.108.218.137]
over a maximum of 30 hops:

1 50 ms <10 ms <10 ms 10.83.90.1
2 10 ms 20 ms 10 ms r1-ge4-0.elcjn1.sdca.home.net [24.4.64.65]
3 10 ms 10 ms 30 ms 10.4.126.9
4 10 ms 20 ms 10 ms c1-pos4-0.sndgca1.home.net [24.7.74.101]
5 20 ms 20 ms 10 ms c1-pos1-0.anhmca1.home.net [24.7.64.69]
6 30 ms 20 ms 20 ms 24.7.65.165
7 20 ms 30 ms 50 ms 200.ATM1-0.BR2.SJC1.ALTER.NET [137.39.91.61]
8 60 ms 30 ms 20 ms 154.ATM2-0.XR1.SJC1.ALTER.NET [152.63.51.182]
9 30 ms 30 ms 40 ms 193.at-2-0-0.TR3.SCL1.ALTER.NET [152.63.48.190]

10 50 ms 40 ms 50 ms 107.at-5-1-0.TR1.POR3.ALTER.NET [146.188.140.121
]
11 50 ms 70 ms 40 ms 197.ATM6-0.XR1.SEA1.ALTER.NET [152.63.104.249]
12 40 ms 60 ms 50 ms 195.ATM4-0.GW8.SEA1.ALTER.NET [152.63.105.217]
13 50 ms 50 ms 50 ms uswbel-oc3-1-gw.customer.alter.net [157.130.178.
94]
14 50 ms 41 ms 70 ms gig0-0-0.sttl-agw2.sttl.uswest.net [206.81.192.2
49]
15 80 ms 61 ms 60 ms 103.fa0-0-0.sttl-6400-gw5.sttl.uswest.net [207.2
24.249.101]
16 70 ms 71 ms 70 ms 207-108-218-142.customers.uswest.net [207.108.21
8.142]
17 * * * Request timed out.

 

[Russ]

<< By any chance Russ, you own/run the computer on ip 207.108.218.142 >>



vss1980,

This is the Cisco 675 DSL modem. And, yes, you're right; it is blocking/not forwarding access somehow. But, so far I haven't been able to figure it out. I've spent hours screwing with the configuration in CBOS, and the US West people are useless.

What strikes me as strange, though, is that while it usually will not complete a traceroute to 137, and will NEVER ping, the site still loads.

Russ, NCNE

 

[Ken g6]

Veeery interestink

When I try a ping from my mail server on telnet:

ucsub> ping -s 207.108.218.137
PING 207.108.218.137: 56 data bytes
^C
----207.108.218.137 PING Statistics----
11 packets transmitted, 0 packets received, 100% packet loss

But when I try starting with port 80:

ucsub> ping -s -U -p80 207.108.218.137
PING 207.108.218.137: 56 data bytes
92 bytes from 207-108-218-137.customers.uswest.net (207.108.218.137): udp_port=80. time=75. ms
36 bytes from 207-108-218-137.customers.uswest.net (207.108.218.137): udp_port=81.
36 bytes from 207-108-218-137.customers.uswest.net (207.108.218.137): udp_port=82.
36 bytes from 207-108-218-137.customers.uswest.net (207.108.218.137): udp_port=83.
^C
----207.108.218.137 PING Statistics----
4 packets transmitted, 4 packets received, 0% packet loss
round-trip (ms) min/avg/max = 75/18/75

Edit: Or for that matter, any port with UDP packets (whatever those are.)

ping -s -U -p1 207.108.218.137
PING 207.108.218.137: 56 data bytes
36 bytes from 207-108-218-137.customers.uswest.net (207.108.218.137): udp_port=1.
.
.
.

 

[TwoFace]

Yep Ken_g6 found what I thought it might be... I'd guess your router/switch thing closes all ports except for the ones necessary for webaccess... probably the mail ports are open too, since tracert and ping both use different ports than http there's probably your reason why it won't complete a tracert, but the page loads fast for me too

BTW, here's my tracert:

Tracing route to 207-108-218-137.customers.uswest.net [207.108.218.137]
over a maximum of 30 hops:


<<
1 50 ms 40 ms 50 ms oke1-as58rs2.dax.net [193.216.35.152]
2 51 ms 40 ms 50 ms oke1-core2.fastethernet5-0.dax.net [193.216.35.130]
3 50 ms 50 ms 40 ms bck1-core.pos0-3.swip.net [130.244.192.217]
4 60 ms 50 ms 40 ms gbg3-core.srp6-0.swip.net [130.244.198.65]
5 50 ms 40 ms 70 ms mlm1-core.pos4-0.swip.net [130.244.193.98]
6 50 ms 61 ms 70 ms icm-tl2-11-H6-0-E3.icp.net [198.67.142.129]
7 150 ms 141 ms 130 ms 198.67.142.185
8 130 ms 140 ms 141 ms sl-bb22-pen-5-2.sprintlink.net [144.232.5.169]
9 140 ms 130 ms 140 ms sl-bb21-pen-15-0.sprintlink.net [144.232.16.29]
10 210 ms 201 ms 210 ms sl-bb10-sea-6-2.sprintlink.net [144.232.9.141]
11 201 ms 200 ms 210 ms sl-gw11-sea-7-0.sprintlink.net [144.232.6.126]
12 211 ms 210 ms 210 ms sl-uswestia-2-0-0.sprintlink.net [144.232.236.14]
13 210 ms 200 ms 211 ms gig6-0-0.sttl-agw1.sttl.uswest.net [206.81.192.216]
14 200 ms 201 ms 210 ms 103.fa0-0-0.sttl-6400-gw5.sttl.uswest.net [207.224.249.101]
15 230 ms 230 ms 231 ms 207-108-218-142.customers.uswest.net [207.108.218.142]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete. >>

Hope this helps some!

With love and respect your fellow TA member

Two-Face

 

[Russ]

HMM...so ping and traceroute don't use port 80? I learn something new everyday.

Russ, NCNE

 

[Slahr Dzhe]

Russ-

I am not familiar with that particular router, or the IOS that runs on it, but according to some reference material(and some personal experience), there is no port associated with ICMP messages(ping, traceroute, etc.) I will quote directly from the book(ICRC):


<< ICMP does not use port numbers in its header because all ICMP messages are interpreted by the network software itself; therefore, no port numbers are needed to determine the destination of the message. ICMP does, however, include a type field, and it identifies the ICMP message type echo request. >>


From what I remember from setting up the routers, there is a place in the IOS where you can specify whether or not to allow ICMP messages. If this function is disabled, you will never be able to ping, traceroute, etc. to the server. All other functions of the TCP/IP ports should still work unless specifically disabled or blocked.

SD

 

[Russ]

Slahr Dzhe,

According to the docs, The Cisco 675 incorporates ICMP in to the IP layer and calls it IPCP (Internet Protocol Control Protocol). IPCP is enabled on the router.

Russ, NCNE

 

[Michael]

Loads super fast, no tracert (times out at the last hop, just like the other's posted).

Michael

 

[Viztech]

Russ, if memory serves, the Cisco 675 is meant primarily for residential/light commercial use. The next step up in the line would be recommended for the more severe use that Borg need for Intergalactic communication.

Interestingly, I can ping and tracert to one of my sites that has USWest DSL service, but uses a different ISP that uses ATM routing rather than PPP.

Are you using PPP?

viz

 

[Russ]

Viz,

HeHe, what little traffic I'll be getting with the handful of sites I'm hoping to move to my server shouldn't be a problem for the 675. I know a guy who's hosting 24 sites with one

Yep, we're PPP here in this area.

Russ, NCNE

 

[JoeDaddy]

Just to state the obvious, it does load for me as well and here is the tracert info.


&quot;
Tracing route to 207-108-218-137.customers.uswest.net [207.108.218.137]

over a maximum of 30 hops:



1 18 ms 12 ms 8 ms 10.84.66.1

2 8 ms 8 ms 8 ms bb1-fe1-0-100bt.clmba1.mo.home.net [24.12.195.1]

3 24 ms 19 ms 14 ms c1-se6-4.kscymo1.home.net [24.7.75.213]

4 15 ms 20 ms 15 ms c1-pos4-0.omahne1.home.net [24.7.64.145]

5 15 ms 16 ms 16 ms c1-pos1-0.desmia1.home.net [24.7.64.138]

6 22 ms 22 ms 28 ms c1-pos2-0.chcgil1.home.net [24.7.64.166]

7 31 ms 27 ms 32 ms c1-pos5-0.chcgil1.home.net [24.7.77.169]

8 24 ms 24 ms 24 ms ATM3-0.BR2.CHI2.ALTER.NET [137.39.52.105]

9 24 ms 31 ms 28 ms 156.at-6-0-0.XR2.CHI2.ALTER.NET [152.63.67.254]

10 31 ms 25 ms 23 ms 0.so-3-0-0.TR2.CHI2.ALTER.NET [152.63.15.134]

11 85 ms 83 ms 91 ms 126.ATM6-0.TR2.SEA1.ALTER.NET [146.188.140.62]

12 74 ms 77 ms 84 ms 198.ATM6-0.XR2.SEA1.ALTER.NET [146.188.200.113]

13 77 ms 78 ms 74 ms 194.ATM5-0.GW8.SEA1.ALTER.NET [152.63.105.221]

14 86 ms 77 ms 78 ms uswbel-oc3-1-gw.customer.alter.net [157.130.178.94]

15 84 ms 89 ms 89 ms gig6-0-0.sttl-agw1.sttl.uswest.net [206.81.192.216]

16 80 ms 84 ms 79 ms 103.fa0-0-0.sttl-6400-gw5.sttl.uswest.net [207.224.249.101]

17 100 ms 144 ms 98 ms 207-108-218-142.customers.uswest.net [207.108.218.142]

18 * * * Request timed out.

19 * * * Request timed out.

 

[Viztech]

Hehe, Yeah our web guy was pulling a fast one and started hosting about 10 websites- Plus his domain DNS server on this same box, in addition to outgoing traffic by 6 machines. There is a limitation to the number of connections supported by the 675, so that became a problem.

Just an FYI

viz