• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Okay, guys, need help testing my server again.

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
loads fast for me russ. Good job on it 🙂


I tried loading it down with a constant flash of refreshes, but it took it like a real server 😛
 
Okay, here's how it lays out, and maybe one of you server gurus can steer me in the right direction.

The first address that is loading just fine, 207.108.218.138 is going to my Linksys DSL router and is being port forwarded to the internal (LAN) address of one of the NICs in the server. It loads every time with no problems. I have the default virtual server in Apache mapped to the /tacube directory.

The second address, 207.108.218.137 is bypassing the DSL router. I'll try to illustrate this:

Cisco 675 to switch. Patch cable from switch to Linksys DSL router to serve all the systems on the network. Then patch cable from the switch to the second NIC in the server. This NIC is assigned 207.108.218.137 - the one that only works about half the time.

For 207.108.218.137, I have a virtual server setup using the identical settings as the default server that loads the other IP address lickity-split.

All hardware tests out fine; switch, cables, NICs.

Any ideas?

Thanks, guys. I appreciate the help. This puppy has been driving me nuts.

Russ, NCNE
 
Here's a tracert:

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

D:\>tracert 207.108.218.137

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

1 30 ms 20 ms 20 ms 208.223.8.65
2 30 ms 20 ms 10 ms 500.serial5-1-1.gw2.hou1.alter.net [157.130.138.
33]
3 20 ms 30 ms 30 ms 114.atm2-0.xr1.hou4.alter.net [146.188.240.242]

4 50 ms 20 ms 30 ms 193.at-1-0-0.tr1.hou7.alter.net [152.63.99.138]

5 100 ms 110 ms 90 ms 132.atm7-0.tr1.sea1.alter.net [146.188.140.34]
6 90 ms 90 ms 90 ms 199.atm7-0.xr1.sea1.alter.net [146.188.200.101]

7 101 ms 140 ms 90 ms 195.atm4-0.gw8.sea1.alter.net [152.63.105.217]
8 141 ms 90 ms 110 ms uswbel-oc3-1-gw.customer.alter.net [157.130.178.
94]
9 100 ms 101 ms 120 ms gig0-0-0.sttl-agw1.sttl.uswest.net [206.81.192.2
48]
10 90 ms 101 ms 90 ms 103.fa0-0-0.sttl-6400-gw5.sttl.uswest.net [207.2
24.249.101]
11 120 ms 131 ms 120 ms 207.108.218.142
12 130 ms 130 ms 120 ms 207-108-218-137.customers.uswest.net [207.108.21
8.137]

Trace complete.

And it finally pinged through:

D:\>ping 207.108.218.137

Pinging 207.108.218.137 with 32 bytes of data:

Reply from 207.108.218.137: bytes=32 time=120ms TTL=244
Reply from 207.108.218.137: bytes=32 time=110ms TTL=244
Reply from 207.108.218.137: bytes=32 time=110ms TTL=244
Reply from 207.108.218.137: bytes=32 time=120ms TTL=244

Ping statistics for 207.108.218.137:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 110ms, Maximum = 120ms, Average = 115ms

 
Gadzooks, just went Golden while in the service of the Borg...😀

Edit: How appropriate, another typo.
 
Doesn't work for me. I get a DNS error. Maybe you'd be interested in a tracert that failed:

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

1 <10 ms <10 ms <10 ms res37-128-supa.resnet.Colorado.EDU [128.138.37.253]
2 1 ms 1 ms 1 ms tcom-res.Colorado.EDU [128.138.81.153]
3 1 ms <10 ms 1 ms hut-tcom.Colorado.EDU [128.138.81.201]
4 1 ms 1 ms 1 ms cuatm-hut.Colorado.EDU [128.138.81.2]
5 2 ms 2 ms 3 ms 204.131.62.18
6 2 ms 2 ms 2 ms acr2-serial2-2-0-0.Denverden.cw.net [208.172.161.205]
7 47 ms 47 ms 46 ms acr2-loopback.Seattlesel.cw.net [208.172.82.62]
8 47 ms 47 ms 47 ms ngcore2.Seattle.cw.net [204.70.9.130]
9 47 ms 47 ms 47 ms bordercore3.Seattle.cw.net [166.48.212.1]
10 47 ms 47 ms 48 ms u-s-west-interact.Seattle.cw.net [166.48.213.250]
11 48 ms 47 ms 48 ms gig0-0-0.sttl-agw2.sttl.uswest.net [206.81.192.249]
12 51 ms 50 ms 49 ms 103.fa0-0-0.sttl-6400-gw5.sttl.uswest.net [207.224.249.101]
13 78 ms 67 ms 69 ms 207.108.218.142
14 * * * Request timed out.

Edit: inopportune line breaks
 
Ken_g6,

A DNS error actually makes sense. They just put my IP addresses in to the root server system today - that was another lengthy battle all by itself.🙁 It may not have yet propogated everywhere.

Russ, NCNE
 
Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\>ping 207.108.218.137

Pinging 207.108.218.137 with 32 bytes of data:

Reply from 207.108.218.137: bytes=32 time=80ms TTL=239
Reply from 207.108.218.137: bytes=32 time=60ms TTL=239
Reply from 207.108.218.137: bytes=32 time=71ms TTL=239
Reply from 207.108.218.137: bytes=32 time=70ms TTL=239

Ping statistics for 207.108.218.137:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 60ms, Maximum = 80ms, Average = 70ms


@home from Southern California... Nice pings 🙂
 
Loads sweet and fast in the Southern Hemisphere:
C:\WINDOWS>ping 207.108.218.137

Pinging 207.108.218.137 with 32 bytes of data:

Reply from 207.108.218.137: bytes=32 time=488ms TTL=233
Reply from 207.108.218.137: bytes=32 time=455ms TTL=233
Reply from 207.108.218.137: bytes=32 time=479ms TTL=233
Reply from 207.108.218.137: bytes=32 time=454ms TTL=233

Ping statistics for 207.108.218.137:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 454ms, Maximum = 488ms, Average = 469ms


Trans Pacific line is congested at the moment, so those pings are good.



 
I can't ping it :

S:\gbonnard>ping 207.108.218.137

Envoi d'une requ&ecirc;te 'ping' sur 207.108.218.137 avec 32 octets de donn&eacute;es :

D&eacute;lai d'attente de la demande d&eacute;pass&eacute;.
D&eacute;lai d'attente de la demande d&eacute;pass&eacute;.
D&eacute;lai d'attente de la demande d&eacute;pass&eacute;.
D&eacute;lai d'attente de la demande d&eacute;pass&eacute;.

Statistiques Ping pour 207.108.218.137:
Paquets : envoy&eacute;s = 4, re&ccedil;us = 0, perdus = 4 (perte 100%),
Dur&eacute;e approximative des boucles en millisecondes :
minimum = 0ms, maximum = 0ms, moyenne = 0ms
 
Works like a charm to ping it from here (Norway, double E1's)

<< H:\>ping 207.108.218.137

Pinger 207.108.218.137 med 32 byte data:

Svar fra 207.108.218.137: byte=32 tid=250ms TTL=230
Svar fra 207.108.218.137: byte=32 tid=221ms TTL=230
Svar fra 207.108.218.137: byte=32 tid=220ms TTL=230
Svar fra 207.108.218.137: byte=32 tid=221ms TTL=230

Ping-statistikker for 207.108.218.137:
Pakker: sendt = 4, mottatt = 4, tapt = 0 (0% tap),
Gjennomsnittlig tid for tur-retur i millisekunder:
minimum = 220ms, maksimum = 250ms, gjennomsnittlig = 228ms >>

With love and respect your fellow TA member

Two-Face
 
Hi Russ,

I can't fault it. I've tried a PC with Explorer/Netscape and Mac Explorer/Netscape and it's fine. Really quick. I wish I could get my site to load that fast. 🙂)
 
PING 207.108.218.137 (207.108.218.137): 56 data bytes
64 bytes from 207.108.218.137: icmp_seq=0 ttl=237 time=110.898 ms
64 bytes from 207.108.218.137: icmp_seq=1 ttl=237 time=100.920 ms
64 bytes from 207.108.218.137: icmp_seq=2 ttl=237 time=101.220 ms
64 bytes from 207.108.218.137: icmp_seq=3 ttl=237 time=102.181 ms
64 bytes from 207.108.218.137: icmp_seq=4 ttl=237 time=102.804 ms
64 bytes from 207.108.218.137: icmp_seq=5 ttl=237 time=103.245 ms
64 bytes from 207.108.218.137: icmp_seq=6 ttl=237 time=102.474 ms
64 bytes from 207.108.218.137: icmp_seq=7 ttl=237 time=104.534 ms
64 bytes from 207.108.218.137: icmp_seq=8 ttl=237 time=102.384 ms
64 bytes from 207.108.218.137: icmp_seq=9 ttl=237 time=101.148 ms

--- 207.108.218.137 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 100.920/103.180/110.898 ms

1 Stealth (192.168.1.1) 1 ms 1 ms 1 ms
2 cr1-hfc1.chsnt1.pa.home.com (24.3.104.1) 24 ms 19 ms 20 ms
3 r1-ge5-0-1000bt.rdc2.pa.home.net (24.2.5.1) 8 ms 7 ms 7 ms
4 10.103.84.1 (10.103.84.1) 7 ms 8 ms 5 ms
5 c1-pos4-0.phlapa1.home.net (24.7.74.57) 11 ms 9 ms 7 ms
6 c1-pos10-0.cmdnnj1.home.net (24.7.65.225) 8 ms 7 ms 6 ms
7 c1-pos1-0.washdc1.home.net (24.7.65.85) 12 ms 9 ms 13 ms
8 ATM2-0.BR3.DCA8.ALTER.NET (137.39.52.37) 32 ms 27 ms 27 ms
9 0.so-4-1-0.XR1.DCA8.ALTER.NET (152.63.36.6) 28 ms 27 ms 27 ms
10 0.so-3-0-0.TR1.DCA8.ALTER.NET (152.63.144.49) 26 ms 26 ms 26 ms
11 115.ATM7-0.TR1.SEA1.ALTER.NET (146.188.138.142) 78 ms 79 ms 79 ms
12 199.ATM6-0.XR1.SEA1.ALTER.NET (146.188.200.97) 91 ms 84 ms 81 ms
13 195.ATM7-0.GW8.SEA1.ALTER.NET (152.63.105.225) 82 ms 82 ms 82 ms
14 uswbel-oc3-1-gw.customer.alter.net (157.130.178.94) 82 ms 79 ms 80 ms
15 gig6-0-0.sttl-agw1.sttl.uswest.net (206.81.192.216) 88 ms 82 ms 79 ms
16 103.fa0-0-0.sttl-6400-gw5.sttl.uswest.net (207.224.249.101) 97 ms 82 ms 81 ms
17 207.108.218.142 (207.108.218.142) 99 ms 99 ms 121 ms
18 207-108-218-137.customers.uswest.net (207.108.218.137) 103 ms 98 ms 102 ms
 
It works for me now. 🙂 Even in Lynx, though it could look better there.
 
Trying it from Denver, Load times out. Same IP as listed above except the last oct being 138.

--LANMAN
 
Doesn't appear to work for me, upstate NY w/ Road Runner. Using IE 5.01, I get a can't find server. I did a pathping in Win2k, it is dying after 207.108.218.142. However, I then did a traceroute from the staff machine for the ISP I work for, and I can trace it fine. I then go into lynx however on the staff box and try to load up the page and it tells me that it can't retrieve the website. Heres all the info:


from the staff box

[staff]:10:58am:~% traceroute 207.108.218.138
traceroute to 207.108.218.138 (207.108.218.138), 30 hops max, 40 byte packets
1 core-1-staff.albany.thebiz.net (216.238.1.125) 0.336 ms 0.301 ms 0.803 m
2 border-1.albany.thebiz.net (216.238.0.2) 0.303 ms 0.482 ms 0.278 ms
3 pos11-0-0-155M.ar1.NYC2.gblx.net (206.132.247.189) 164.346 ms 111.855 ms 42.414 ms
4 pos2-0-155M.cr1.NYC2.gblx.net (206.132.249.181) 8.881 ms 8.619 ms 8.911 ms
5 pos1-2-622M.cr2.CHI1.gblx.net (206.132.118.89) 37.939 ms 37.454 ms 37.528 ms
6 ATM1-0.BR2.CHI2.ALTER.NET (137.39.52.29) 38.149 ms 38.454 ms 38.216 ms
7 156.at-5-0-0.XR2.CHI2.ALTER.NET (152.63.67.246) 38.529 ms 38.791 ms 38.737 ms
8 0.so-3-0-0.TR2.CHI2.ALTER.NET (152.63.15.134) 56.116 ms 56.41 ms 56.409 ms
9 126.ATM6-0.TR2.SEA1.ALTER.NET (146.188.140.62) 92.015 ms 92.13 ms 92.898 ms
10 198.ATM7-0.XR2.SEA1.ALTER.NET (146.188.200.117) 91.941 ms 92.186 ms 92.032 ms
11 194.ATM6-0.GW8.SEA1.ALTER.NET (152.63.105.229) 93.379 ms 92.631 ms 92.572 ms
12 uswbel-oc3-1-gw.customer.alter.net (157.130.178.94) 93.575 ms 93.248 ms 93.499 ms
13 gig0-0-0.sttl-agw2.sttl.uswest.net (206.81.192.249) 93.958 ms 94.851 ms 94.681 ms
14 103.fa0-0-0.sttl-6400-gw5.sttl.uswest.net (207.224.249.101) 93.38 ms 95.035 ms 93.857 ms
15 207.108.218.142 (207.108.218.142) 112.704 ms 110.683 ms 110.576 ms
16 207-108-218-138.customers.uswest.net (207.108.218.138) 114.251 ms 251.865 ms 232.282 ms



pathping from my box

C:\>pathping 207.108.218.138

Tracing route to 207-108-218-138.customers.uswest.net [207.108.218.138]
over a maximum of 30 hops:
0 eric [24.92.xx.xx]
1 10.92.40.1
2 router-32-125.nycap.rr.com [24.29.32.125]
3 srp3-0.albyny1-brt1.rr.com [24.218.189.126]
4 pos1-0.bstnma2-brt2.rr.com [24.218.190.14]
5 srp2-0.wobnma1-brt1.rr.com [24.218.189.174]
6 pos0-1.vinnva1-brt3.rr.com [24.218.188.229]
7 br1.tco1.alter.net [192.41.177.248]
8 br1.tco1.alter.net [192.41.177.248]
9 111.at-3-0-0.XR2.TCO1.ALTER.NET [146.188.160.70]
10 192.at-2-1-0.TR2.DCA6.ALTER.NET [152.63.34.42]
11 .121.ATM6-0.TR2.SEA1.ALTER.NET [146.188.140.78]
12 198.ATM7-0.XR2.SEA1.ALTER.NET [146.188.200.117]
13 194.ATM6-0.GW8.SEA1.ALTER.NET [152.63.105.229]
14 uswbel-oc3-1-gw.customer.alter.net [157.130.178.94]
15 gig0-0-0.sttl-agw1.sttl.uswest.net [206.81.192.248]
16 103.fa0-0-0.sttl-6400-gw5.sttl.uswest.net [207.224.249.101]
17 207.108.218.142
18 ...
Computing statistics for 450 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 eric [24.92.xx.xx]
0/ 100 = 0% |
1 12ms 0/ 100 = 0% 0/ 100 = 0% 10.92.40.1
0/ 100 = 0% |
2 12ms 0/ 100 = 0% 0/ 100 = 0% router-32-125.nycap.rr.com [24.29.32.125]
0/ 100 = 0% |
3 12ms 0/ 100 = 0% 0/ 100 = 0% srp3-0.albyny1-brt1.rr.com [24.218.189.126]
0/ 100 = 0% |
4 17ms 0/ 100 = 0% 0/ 100 = 0% pos1-0.bstnma2-brt2.rr.com [24.218.190.14]
0/ 100 = 0% |
5 15ms 0/ 100 = 0% 0/ 100 = 0% srp2-0.wobnma1-brt1.rr.com [24.218.189.174]
0/ 100 = 0% |
6 41ms 0/ 100 = 0% 0/ 100 = 0% pos0-1.vinnva1-brt3.rr.com [24.218.188.229]
3/ 100 = 3% |
7 46ms 3/ 100 = 3% 0/ 100 = 0% br1.tco1.alter.net [192.41.177.248]
1/ 100 = 1% |
8 49ms 5/ 100 = 5% 1/ 100 = 1% br1.tco1.alter.net [192.41.177.248]
0/ 100 = 0% |
9 67ms 11/ 100 = 11% 7/ 100 = 7% 111.at-3-0-0.XR2.TCO1.ALTER.NET [146.188.160.70]
0/ 100 = 0% |
10 70ms 7/ 100 = 7% 3/ 100 = 3% 192.at-2-1-0.TR2.DCA6.ALTER.NET [152.63.34.42]
0/ 100 = 0% |
11 247ms 16/ 100 = 16% 12/ 100 = 12% 121.ATM6-0.TR2.SEA1.ALTER.NET [146.188.140.78]
0/ 100 = 0% |
12 129ms 6/ 100 = 6% 2/ 100 = 2% 198.ATM7-0.XR2.SEA1.ALTER.NET [146.188.200.117]
0/ 100 = 0% |
13 137ms 6/ 100 = 6% 2/ 100 = 2% 194.ATM6-0.GW8.SEA1.ALTER.NET [152.63.105.229]
0/ 100 = 0% |
14 133ms 5/ 100 = 5% 1/ 100 = 1% uswbel-oc3-1-gw.customer.alter.net [157.130.178.94]
0/ 100 = 0% |
15 135ms 7/ 100 = 7% 3/ 100 = 3% gig0-0-0.sttl-agw1.sttl.uswest.net [206.81.192.248]
0/ 100 = 0% |
16 141ms 7/ 100 = 7% 3/ 100 = 3% 103.fa0-0-0.sttl-6400-gw5.sttl.uswest.net [207.224.249.101]
0/ 100 = 0% |
17 157ms 4/ 100 = 4% 0/ 100 = 0% 207.108.218.142
96/ 100 = 96% |
18 --- 100/ 100 =100% 0/ 100 = 0% eric [0.0.0.0]

Trace complete.


Here is what lynx gives me off of the staff box:

Alert!: Unable to connect to remote host.


lynx: Can't access startfile http://207.108.218.138/

hope this all helps.🙂
 
Got some more info. Oddly enough, I telneted to another box located in our data center in Hartford, Ct (the staff box above is in our Albany, NY data center). From this box I am able traceroute, and I can also view the page in lynx, it loads extremely quick.

Here is the trace from this box:

traceroute to 207.108.218.138 (207.108.218.138) from xxx 40 hops max, 40 byte packets
1 mfd-01.rt.connix.net (198.69.10.1) 0.679 ms 0.619 ms 0.599 ms
2 901.Hssi5-0-0.GW1.HAR1.ALTER.NET (137.39.148.21) 3.610 ms 1.703 ms 7.976 ms
3 154.ATM2-0.XR1.NYC1.ALTER.NET (152.63.23.82) 5.324 ms 4.888 ms 4.237 ms
4 195.at-2-0-0.TR1.NYC9.ALTER.NET (152.63.21.66) 6.484 ms 4.463 ms 5.956 ms
5 125.at-5-0-0.TR1.POR3.ALTER.NET (152.63.6.34) 83.273 ms 86.508 ms 82.830 ms
6 197.ATM6-0.XR1.SEA1.ALTER.NET (152.63.104.249) 86.341 ms 87.283 ms 87.222 ms
7 195.ATM4-0.GW8.SEA1.ALTER.NET (152.63.105.217) 88.871 ms 87.141 ms 87.399 ms
8 uswbel-oc3-1-gw.customer.alter.net (157.130.178.94) 81.582 ms 80.855 ms 81.012 ms
9 gig0-0-0.sttl-agw1.sttl.uswest.net (206.81.192.248) 88.175 ms 87.947 ms 89.339 ms
10 103.fa0-0-0.sttl-6400-gw5.sttl.uswest.net (207.224.249.101) 97.378 ms 83.338 ms 82.202 ms
11 207.108.218.142 (207.108.218.142) 99.595 ms 101.752 ms 101.110 ms
12 207-108-218-138.customers.uswest.net (207.108.218.138) 115.814 ms 113.067 ms 109.489 ms
 
You guys are great!😀 Very valuable information.

The way it's acting, it looks like 138 is loading the majority of the time, and may just be a propogation issue (I hope). I'll see how that's doing in a day or two.

The other, 137, appears to be something more complicated. You guys get about the same results on that one that I've been experiencing. It's 50/50 at best.🙁 Since this one bypasses the Linksys router in to the switch to the server, it could be something in the settings in the Cisco 675. I'll take a look at that.

Back to more studying.🙂

Russ, NCNE
 
Some info for the 207.108.218.137 IP address:

from our staff box in our albany, ny data center:

[staff]:3:27pm:~% ping -c 30 207.108.218.137
PING 207.108.218.137 (207.108.218.137): 56 data bytes
64 bytes from 207.108.218.137: icmp_seq=0 ttl=242 time=102.4 ms
...
--- 207.108.218.137 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max = 101.6/103.2/110.8 ms


From my box on road runner in albany, ny:

C:\>ping -t -l 64 207.108.218.137

Pinging 207.108.218.137 with 64 bytes of data:

Reply from 207.108.218.137: bytes=64 time=180ms TTL=238
Request timed out.
...
Ping statistics for 207.108.218.137:
Packets: Sent = 27, Received = 22, Lost = 5 (18% loss),
Approximate round trip times in milli-seconds:
Minimum = 160ms, Maximum = 190ms, Average = 139ms


from another box in our hartford, ct data center:

: > ping -c 30 207.108.218.137
PING 207.108.218.137 (207.108.218.137): 56 data bytes
64 bytes from 207.108.218.138: icmp_seq=0 ttl=244 time=110.51 ms
...
--- 207.108.218.137 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max = 106.041/110.633/144.711 ms
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top