independent verification of server status

Good evening,

As some of you may know, for the past few months I have been slowly getting closer toward operating a functional home web server. I ran into some issues with port forwarding recently, but I believe I may have resolved them this evening.

I cannot check whether everything is working for the outside world as all the computers in my home are on the same network; therefore, I am taking to LQ to ask a favor:

Can someone please attempt to access 184.187.181.38/index.html and report back if it is working?

Thanks very much, in advance.

Lawrence (R3nCi), the would-be server admin

It's probably quite obnoxious of me to bump this, but I don't have access to a computer outside my home network at the moment. Can someone check on this for me, please?

Ping is fine but browser keeps getting connections reset.

from my Data Center in San Diego, traceroute bombs at 9th hop

9 68.6.13.3 (68.6.13.3)  43.291 ms  33.157 ms sntbhdrj01-ge022.0.rd.sb.cox.net (68.6.13.1)  54.540 ms

and from here in Depressing Ohio, I get

9  68.6.13.3 (68.6.13.3)  33.168 ms sntbhdrj01-ge022.0.rd.sb.cox.net (68.6.13.1)  54.574 ms 68.6.13.3 (68.6.13.3)  33.294 ms

Browser doesn't render anything at http://184.187.181.38/index.html, nor at https://184.187.181.38/index.html

Cox Communication is pretty active about what they'll allow and so I nmap'd the IP and got this:

nmap 184.187.181.38 -PN

Starting Nmap 6.01 ( http://nmap.org ) at 2012-09-15 19:24 EDT
Nmap scan report for ip184-187-181-38.sb.sd.cox.net (184.187.181.38)
Host is up (0.15s latency).
Not shown: 999 filtered ports
PORT    STATE  SERVICE
443/tcp closed https

Nmap done: 1 IP address (1 host up) scanned in 13.99 seconds

Off-hand, I'd say either Cox has blocked :80 or the service isn't running?

Full traceroute from San Diego...

traceroute to 184.187.181.38 (184.187.181.38), 30 hops max, 40 byte packets
 1  71.19.227.97 (71.19.227.97)  100.775 ms  100.955 ms  101.190 ms
 2  cr1-tuk-g2-1.bb.spectrumnet.us (216.243.26.81)  12.600 ms  12.709 ms  12.773 ms
 3  cr2-sea-B-t8-3.bb.spectrumnet.us (208.76.153.93)  23.328 ms  23.428 ms  23.481 ms
 4  ae0-126.sea21.ip4.tinet.net (216.221.156.41)  0.413 ms  0.473 ms  0.465 ms
 5  xe-5-0-0.lax20.ip4.tinet.net (89.149.182.194)  31.249 ms  31.245 ms xe-9-1-0.lax20.ip4.tinet.net (89.149.181.166)  31.263 ms
 6  cox-communications-gw.ip4.tinet.net (77.67.79.230)  29.562 ms  29.196 ms  29.190 ms
 7  rsmtdsrj02-ae0.0.rd.oc.cox.net (68.1.0.189)  35.026 ms  29.547 ms  29.437 ms
 8  ip68-4-11-97.oc.oc.cox.net (68.4.11.97)  76.129 ms ip68-4-11-133.oc.oc.cox.net (68.4.11.133)  33.531 ms ip68-4-11-97.oc.oc.cox.net (68.4.11.97)  75.982 ms
 9  68.6.13.3 (68.6.13.3)  33.295 ms sntbhdrj01-ge022.0.rd.sb.cox.net (68.6.13.1)  54.481 ms 68.6.13.3 (68.6.13.3)  33.576 ms
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

Full traceroute from Yo, OH:

traceroute to 184.187.181.38 (184.187.181.38), 30 hops max, 40 byte packets
 1  71.19.227.97 (71.19.227.97)  1.082 ms  1.355 ms  1.606 ms
 2  cr1-tuk-g2-1.bb.spectrumnet.us (216.243.26.81)  0.352 ms  0.482 ms  0.483 ms
 3  cr2-sea-B-t8-3.bb.spectrumnet.us (208.76.153.93)  0.590 ms  0.634 ms  0.694 ms
 4  ae0-126.sea21.ip4.tinet.net (216.221.156.41)  0.429 ms  0.419 ms  0.410 ms
 5  xe-8-1-0.lax20.ip4.tinet.net (89.149.181.170)  31.314 ms xe-8-2-0.lax20.ip4.tinet.net (89.149.182.174)  31.305 ms xe-8-1-0.lax20.ip4.tinet.net (89.149.181.170)  31.295 ms
 6  cox-gw.ip4.tinet.net (216.221.157.54)  33.009 ms  32.770 ms cox-communications-gw.ip4.tinet.net (77.67.79.230)  28.892 ms
 7  rsmtdsrj01-ae0.0.rd.oc.cox.net (68.1.0.185)  29.650 ms  29.629 ms rsmtdsrj02-ae0.0.rd.oc.cox.net (68.1.0.189)  29.501 ms
 8  ip68-4-11-99.oc.oc.cox.net (68.4.11.99)  55.210 ms ip68-4-11-97.oc.oc.cox.net (68.4.11.97)  76.035 ms ip68-4-11-99.oc.oc.cox.net (68.4.11.99)  54.897 ms
 9  68.6.13.3 (68.6.13.3)  33.168 ms sntbhdrj01-ge022.0.rd.sb.cox.net (68.6.13.1)  54.574 ms 68.6.13.3 (68.6.13.3)  33.294 ms
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

Hope that Helps!

Originally Posted by Habitual from my Data Center in San Diego, traceroute bombs at 9th hop 9 68.6.13.3 (68.6.13.3) 43.291 ms 33.157 ms sntbhdrj01-ge022.0.rd.sb.cox.net (68.6.13.1) 54.540 ms and from here in Depressing Ohio, I get 9 68.6.13.3 (68.6.13.3) 33.168 ms sntbhdrj01-ge022.0.rd.sb.cox.net (68.6.13.1) 54.574 ms 68.6.13.3 (68.6.13.3) 33.294 ms Browser doesn't render anything at http://184.187.181.38/index.html, nor at https://184.187.181.38/index.html Cox Communication is pretty active about what they'll allow and so I nmap'd the IP and got this: nmap 184.187.181.38 -PN Starting Nmap 6.01 ( http://nmap.org ) at 2012-09-15 19:24 EDT Nmap scan report for ip184-187-181-38.sb.sd.cox.net (184.187.181.38) Host is up (0.15s latency). Not shown: 999 filtered ports PORT STATE SERVICE 443/tcp closed https Nmap done: 1 IP address (1 host up) scanned in 13.99 seconds Off-hand, I'd say either Cox has blocked :80 or the service isn't running? Full traceroute from San Diego... traceroute to 184.187.181.38 (184.187.181.38), 30 hops max, 40 byte packets 1 71.19.227.97 (71.19.227.97) 100.775 ms 100.955 ms 101.190 ms 2 cr1-tuk-g2-1.bb.spectrumnet.us (216.243.26.81) 12.600 ms 12.709 ms 12.773 ms 3 cr2-sea-B-t8-3.bb.spectrumnet.us (208.76.153.93) 23.328 ms 23.428 ms 23.481 ms 4 ae0-126.sea21.ip4.tinet.net (216.221.156.41) 0.413 ms 0.473 ms 0.465 ms 5 xe-5-0-0.lax20.ip4.tinet.net (89.149.182.194) 31.249 ms 31.245 ms xe-9-1-0.lax20.ip4.tinet.net (89.149.181.166) 31.263 ms 6 cox-communications-gw.ip4.tinet.net (77.67.79.230) 29.562 ms 29.196 ms 29.190 ms 7 rsmtdsrj02-ae0.0.rd.oc.cox.net (68.1.0.189) 35.026 ms 29.547 ms 29.437 ms 8 ip68-4-11-97.oc.oc.cox.net (68.4.11.97) 76.129 ms ip68-4-11-133.oc.oc.cox.net (68.4.11.133) 33.531 ms ip68-4-11-97.oc.oc.cox.net (68.4.11.97) 75.982 ms 9 68.6.13.3 (68.6.13.3) 33.295 ms sntbhdrj01-ge022.0.rd.sb.cox.net (68.6.13.1) 54.481 ms 68.6.13.3 (68.6.13.3) 33.576 ms 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * Full traceroute from Yo, OH: traceroute to 184.187.181.38 (184.187.181.38), 30 hops max, 40 byte packets 1 71.19.227.97 (71.19.227.97) 1.082 ms 1.355 ms 1.606 ms 2 cr1-tuk-g2-1.bb.spectrumnet.us (216.243.26.81) 0.352 ms 0.482 ms 0.483 ms 3 cr2-sea-B-t8-3.bb.spectrumnet.us (208.76.153.93) 0.590 ms 0.634 ms 0.694 ms 4 ae0-126.sea21.ip4.tinet.net (216.221.156.41) 0.429 ms 0.419 ms 0.410 ms 5 xe-8-1-0.lax20.ip4.tinet.net (89.149.181.170) 31.314 ms xe-8-2-0.lax20.ip4.tinet.net (89.149.182.174) 31.305 ms xe-8-1-0.lax20.ip4.tinet.net (89.149.181.170) 31.295 ms 6 cox-gw.ip4.tinet.net (216.221.157.54) 33.009 ms 32.770 ms cox-communications-gw.ip4.tinet.net (77.67.79.230) 28.892 ms 7 rsmtdsrj01-ae0.0.rd.oc.cox.net (68.1.0.185) 29.650 ms 29.629 ms rsmtdsrj02-ae0.0.rd.oc.cox.net (68.1.0.189) 29.501 ms 8 ip68-4-11-99.oc.oc.cox.net (68.4.11.99) 55.210 ms ip68-4-11-97.oc.oc.cox.net (68.4.11.97) 76.035 ms ip68-4-11-99.oc.oc.cox.net (68.4.11.99) 54.897 ms 9 68.6.13.3 (68.6.13.3) 33.168 ms sntbhdrj01-ge022.0.rd.sb.cox.net (68.6.13.1) 54.574 ms 68.6.13.3 (68.6.13.3) 33.294 ms 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * Hope that Helps!

Thank you so much for taking the time to run those tests! I'll post this in the LQ Server forum, if you don't mind.

edit: 4781408

You are very welcome.