I just signed up for a virtual host a couple of days ago, they give me an IP address. I can access that IP address from a computer at my workplace,
but not from my machine at home that is on the RoadRunner cable modem. What could be wrong?

The hosting company says to contact ISP. I posted a message on the ISP support group, but I haven't gotten any responses. Please help.

Here is the traceroute:

C:\>tracert 66.232.17.22

Tracing route to 66.232.17.22 over a maximum of 30 hops

1 * * * Request timed out.
2 <10 ms 15 ms 16 ms 10.70.128.1
3 <10 ms 15 ms 16 ms GSRB-POS0-2.san.rr.com [24.25.192.214]
4 <10 ms 16 ms <10 ms 24-25-194-5.san.rr.com [24.25.194.5]
5 <10 ms 16 ms 31 ms pop1-las-P7-0.atdn.net [66.185.137.137]
6 <10 ms <10 ms 15 ms bb2-las-P0-0.atdn.net [66.185.137.133]
7 16 ms 15 ms 16 ms bb2-sun-P5-0.atdn.net [66.185.152.46]
8 16 ms 16 ms 31 ms bb2-sje-P0-2.atdn.net [66.185.153.49]
9 16 ms 15 ms 16 ms pop1-sje-P6-0.atdn.net [66.185.138.102]
10 16 ms 16 ms 31 ms pos8-0.cr7.sjc2.us.mfnx.net [209.249.119.117]
11 47 ms 63 ms 62 ms pos2-0.mpr1.dfw2.us.mfnx.net [208.184.232.81]
12 47 ms 62 ms 63 ms so-3-0-0.cr2.dfw2.us.mfnx.net [216.200.127.217]
13 78 ms 78 ms 78 ms so-2-1-0.cr2.atl2.us.mfnx.net [216.200.127.225]
14 78 ms 63 ms 78 ms pos2-0.er1.atl4.us.mfnx.net [208.184.232.18]
15 94 ms 78 ms 78 ms above-gw.atl4.cogentco.com [64.124.51.162]
16 78 ms 78 ms 94 ms p15-0.core01.jax01.atlas.cogentco.com [66.28.4.137]
17 78 ms 94 ms 94 ms p15-0.core01.mia01.atlas.cogentco.com [66.28.4.66]
18 78 ms 94 ms 94 ms g50.ba01.b002802-1.mia01.atlas.cogentco.com [66.28.6.46]
19 79 ms 93 ms 94 ms miamfllrh07-custbr-fastduck.ip.epik.net [216.22.64.62]
20 78 ms 110 ms 94 ms beach.ip-pop.com [66.28.76.18]
21 109 ms 94 ms 93 ms 66.232.5.6
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.

Your request is dying one hop before it reaches the destination. So probably either a router or firewall. I got to it just fine from here. Maybe your subnet is blocked for whatever reason. The problem is definately in their network somewhere though.

-Dan

I can ping and trace to the router no problem:

============================================
C:\>tracert 66.232.17.1

Tracing route to 66.232.17.1 over a maximum of 30 hops

1 125 ms 125 ms 687 ms 10.70.128.1
2 <10 ms 16 ms <10 ms 10.70.128.1
3 <10 ms 16 ms 16 ms GSRB-POS0-2.san.rr.com [24.25.192.214]
4 <10 ms 16 ms <10 ms 24-25-194-5.san.rr.com [24.25.194.5]
5 47 ms <10 ms <10 ms pop1-las-P7-0.atdn.net [66.185.137.137]
6 <10 ms 15 ms 16 ms bb2-las-P0-0.atdn.net [66.185.137.133]
7 16 ms 15 ms 16 ms bb2-sun-P5-0.atdn.net [66.185.152.46]
8 16 ms 15 ms 31 ms bb2-sje-P0-2.atdn.net [66.185.153.49]
9 15 ms 16 ms 31 ms pop1-sje-P6-0.atdn.net [66.185.138.102]
10 16 ms 15 ms 32 ms pos8-0.cr7.sjc2.us.mfnx.net [209.249.119.117]
11 47 ms 63 ms 62 ms pos2-0.mpr1.dfw2.us.mfnx.net [208.184.232.81]
12 47 ms 63 ms 62 ms so-3-0-0.cr2.dfw2.us.mfnx.net [216.200.127.217]
13 79 ms 78 ms 78 ms so-2-1-0.cr2.atl2.us.mfnx.net [216.200.127.225]
14 63 ms 78 ms 62 ms pos2-0.er1.atl4.us.mfnx.net [208.184.232.18]
15 78 ms 78 ms 78 ms above-gw.atl4.cogentco.com [64.124.51.162]
16 78 ms 94 ms 78 ms p15-0.core01.jax01.atlas.cogentco.com [66.28.4.137]
17 78 ms 94 ms 93 ms p15-0.core01.mia01.atlas.cogentco.com [66.28.4.66]
18 78 ms 94 ms 94 ms g49.ba01.b002802-1.mia01.atlas.cogentco.com [66.28.6.42]
19 78 ms 94 ms 93 ms miamfllrh07-custbr-fastduck.ip.epik.net [216.22.64.62]
20 78 ms 94 ms 94 ms beach.ip-pop.com [66.28.76.18]
21 94 ms 94 ms 93 ms 66.232.17.1

Trace complete.
============================================

The traceroute to 66.232.17.22 works fine from a number of servers listed at traceroute.org. It just doesn't work from my computer. :bawling:

C:\>tracert 66.232.17.22

Tracing route to 66.232.17.22 over a maximum of 30 hops

1 <10 ms 16 ms 16 ms 10.70.128.1
2 <10 ms 16 ms 15 ms 10.70.128.1
3 <10 ms 16 ms <10 ms GSRB-POS0-2.san.rr.com [24.25.192.214]
4 <10 ms 16 ms <10 ms 24-25-194-5.san.rr.com [24.25.194.5]
5 15 ms 16 ms 16 ms pop1-las-P7-0.atdn.net [66.185.137.137]
6 <10 ms 16 ms 15 ms bb2-las-P0-0.atdn.net [66.185.137.133]
7 16 ms 15 ms 16 ms bb2-sun-P5-0.atdn.net [66.185.152.46]
8 16 ms 16 ms 31 ms bb2-sje-P0-2.atdn.net [66.185.153.49]
9 16 ms 16 ms 31 ms pop1-sje-P6-0.atdn.net [66.185.138.102]
10 16 ms 15 ms 32 ms pos8-0.cr7.sjc2.us.mfnx.net [209.249.119.117]
11 47 ms 63 ms 62 ms pos2-0.mpr1.dfw2.us.mfnx.net [208.184.232.81]
12 47 ms 63 ms 62 ms so-3-0-0.cr2.dfw2.us.mfnx.net [216.200.127.217]
13 79 ms 78 ms 78 ms so-2-1-0.cr2.atl2.us.mfnx.net [216.200.127.225]
14 78 ms 79 ms 78 ms pos2-0.er1.atl4.us.mfnx.net [208.184.232.18]
15 63 ms 78 ms 63 ms above-gw.atl4.cogentco.com [64.124.51.162]
16 78 ms 78 ms 94 ms p15-0.core01.jax01.atlas.cogentco.com [66.28.4.137]
17 78 ms 94 ms 94 ms p15-0.core01.mia01.atlas.cogentco.com [66.28.4.66]
18 78 ms 94 ms 93 ms g50.ba01.b002802-1.mia01.atlas.cogentco.com [66.28.6.46]
19 78 ms 94 ms 94 ms miamfllrh07-custbr-fastduck.ip.epik.net [216.22.64.62]
20 78 ms 94 ms 93 ms beach.ip-pop.com [66.28.76.18]
21 78 ms 94 ms 94 ms 66.232.5.6
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.

My guess is that 66.232.5.6 is a firewall, and your IP or subnet is blocked. 66.232.17.1 is not the router that you go through to get to 66.232.17.22. Contact your hosting provider, it is not on your ISP's end .

-Dan

serve-you, thank you for helping!

Which provider should I contact? The hosting or ISP?

The hosting provider tells me I should contact ISP. I am trying to contact ISP, but so far I got no luck (I can access all the other Internet sites that I tried no problem).

Are there any specific configuration settings that I can ask my provider to check?

Sorry I edited the post right after I hit submit. Ask your host what 66.232.5.6 is. If it's a firewall, then tell them to make sure that your subnet is not being blocked. If that's not the case, then I guess they'll just have to do their job and figure out the problem :)

-Dan

When I try to telnet to 66.232.5.6 I get this:


************************************************************

Packet Engines PowerRail 1000

Version 2.7.0r14 - 18 Jan, 2000

Copyright(c) 1997-1999 Packet Engines, Inc.
Spokane, Washington, USA
All rights reserved.
System MAC Address: 00:e0:b1:30:6c:16

************************************************************
Current Time: Apr 19, 2002 00:40
Remote login from 66.75.31.174

login:


Is this a router?

I think it's a switch. But on a quick search I can't find any info on it, cuz alcatel bought packet engines, and it looks like that was discontinued.

-Dan

If you haven't figured out the answer to this one yet, it would probably be helpful if you logged into the server and do a traceroute from the server back to your home IP address (or get someone who has access to the server to do it). I've seen cases where the return path for packets is sent off into nowhere, resulting in being unable to connect.

Here is my home IP address:
66.75.31.174

Can anyone see anything wrong with it?

Like I said, post a traceroute from the server back to your home computer's IP address.

I am currently at work behind a firewall, and I am very limited at what I can do. I can access CPanel though, but when I try to use the traceroute utility, I get this:

Traceroute is disabled on this system, ask your system admin to chmod 4755 /usr/sbin/traceroute.

Actually I have never been able to traceroute to my home machine from anywhere. So I assume, I wouldn't be able to traceroute from the virtual server ether.

Here is the traceroute from San Diego Super Computer Center:

SDSC Traceroute Output
FROM www.sdsc.edu TO 66.75.31.174 at Fri Apr 19 08:30:39 PDT 2002.

traceroute: Warning: Multiple interfaces found; using 198.202.76.58 @ hme0
traceroute to 66.75.31.174 (66.75.31.174), 30 hops max, 40 byte packets
1 thing-i.sdsc.edu (198.202.76.40) 1.047 ms 0.523 ms 1.265 ms
2 medusa.sdsc.edu (198.202.75.10) 1.722 ms 1.830 ms 0.996 ms
3 sd-nap.px.xo.com (198.17.46.118) 42.807 ms 27.995 ms 2.341 ms
4 a3-0d1.dist1.sdg-ca.us.xo.net (209.31.222.149) 5.368 ms 4.358 ms 3.779 ms
5 a14-0d169.tran1.lax-ca.us.xo.net (206.111.14.237) 8.121 ms 9.069 ms 15.655 ms
6 ge5-3-1.RAR1.LA-CA.us.xo.net (64.220.0.94) 8.666 ms 11.425 ms 9.860 ms
7 p6-0-0.RAR2.SanJose-CA.us.xo.net (65.106.0.18) 15.258 ms 17.715 ms 20.783 ms
8 ge0-0.edge1.scl-ca.us.xo.net (64.220.0.70) 18.543 ms 20.108 ms 21.683 ms
9 pop1-sun-P6-1.atdn.net (66.185.140.189) 18.663 ms 20.027 ms 17.654 ms
10 bb2-sun-P0-0.atdn.net (66.185.140.165) 18.899 ms 21.083 ms 52.585 ms
11 bb2-las-P7-0.atdn.net (66.185.152.45) 26.389 ms 28.382 ms 25.078 ms
12 pop1-las-P1-0.atdn.net (66.185.137.134) 27.878 ms 25.588 ms 27.428 ms
13 rr-san-diego.atdn.net (66.185.137.138) 28.216 ms 28.850 ms 28.563 ms
14 24-25-194-4.san.rr.com (24.25.194.4) 28.996 ms 28.405 ms 32.072 ms
15 ubr13-POS2-0.san.rr.com (24.25.192.213) 34.221 ms * 32.071 ms
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

I think you're missing the point. Packets from one place to another don't necessarily take the same path to and from. Data going from your computer to a different webserver might go through AT&T's network on the way there, and go through Qwest or anyone else on the way back. Doing a traceroute from your home computer only shows the route that it's using to get to the destination, and NOT the return route. Doing a traceroute from the webserver back to your home computer should show the return route. I had this exact problem happen awhile back, where the forward traceroute got all the way to the last hop through UUNET's network and died. Doing a traceroute in the other direction basically had the packets routing through CW.NET's network, and one of CW.NET's routers didn't know where they needed to go, so they just died at CW.NET's router.

billyjoe, how did you fix that problem then?

Just contact your host, and have them do a traceroute FROM YOUR SERVER, to your home IP. Make sure that they do it from your server, as you may be able to get other places on their network.

-Dan

Here's an example of asymetrical routing. Here's a traceroute from 12.217.28.127 to 205.243.76.245
and a traceroute back from 205.243.76.245 to 12.217.28.127. Notice how the packets take AT&T's and UUNET's network in one direction, and Sprint and AT&T in the other.



traceroute 205.243.76.245

traceroute to 205.243.76.245 (205.243.76.245), 30 hops max, 38 byte packets
1 10.17.24.1 (10.17.24.1) 15.516 ms 8.177 ms 7.662 ms
2 12.215.14.97 (12.215.14.97) 8.021 ms 8.840 ms 10.179 ms
3 12.215.4.70 (12.215.4.70) 19.662 ms 20.363 ms 19.606 ms
4 gbr1-a90s9.sl9mo.ip.att.net (12.123.24.94) 20.252 ms 19.927 ms 21.829 ms
5 tbr2-p013502.sl9mo.ip.att.net (12.122.11.113) 25.834 ms 19.493 ms 19.828
ms
6 tbr2-p013601.cgcil.ip.att.net (12.122.11.61) 26.171 ms 56.981 ms 35.555 m
s
7 ggr1-p3100.cgcil.ip.att.net (12.122.11.210) 20.604 ms 20.924 ms 20.205 ms
8 POS5-1.BR5.CHI2.ALTER.NET (204.255.168.57) 25.012 ms 36.134 ms 24.802 ms
9 0.so-6-0-0.XL2.CHI2.ALTER.NET (152.63.68.194) 21.505 ms 21.354 ms 21.705
ms
10 0.so-7-0-0.XR2.CHI2.ALTER.NET (152.63.67.134) 22.931 ms 20.661 ms 23.745
ms
11 292.at-5-0-0.XR2.CHI4.ALTER.NET (152.63.65.6) 24.770 ms 22.492 ms 24.458
ms
12 194.ATM7-0.GW2.CHI1.ALTER.NET (152.63.68.221) 27.576 ms 38.515 ms 27.174
ms
13 revealed2-gw.customer.ALTER.NET (157.130.102.86) 65.277 ms 54.634 ms 56.9
21 ms
14 h2o.jsnetworth.com (205.243.76.245) 54.724 ms 55.333 ms 58.565 ms




/usr/sbin/traceroute 12.217.28.127
traceroute to 12.217.28.127 (12.217.28.127), 30 hops max, 38 byte packets
1 revealed-gw.revealed.net (205.243.76.1) 0.795 ms 0.829 ms 6.517 ms
2 sl-gw30-chi-1-0-0-TS13.sprintlink.net (160.81.110.49) 16.371 ms 26.680 ms
11.132 ms
3 144.232.26.241 (144.232.26.241) 11.296 ms 10.624 ms 10.193 ms
4 sl-bb23-fw-10-3.sprintlink.net (144.232.9.26) 164.695 ms 54.344 ms 200.697 ms
5 sprint-gw.dlstx.ip.att.net (192.205.32.53) 38.713 ms 56.497 ms 46.824 ms
6 gbr4-p50.dlstx.ip.att.net (12.123.16.246) 54.560 ms 63.274 ms 42.126 ms
7 gbr2-p30.kszmo.ip.att.net (12.122.2.114) 53.253 ms 54.992 ms 44.571 ms
8 gbr1-p60.kszmo.ip.att.net (12.122.1.93) 54.069 ms 55.786 ms 50.788 ms
9 gbr4-p40.sl9mo.ip.att.net (12.122.2.42) 53.704 ms 55.728 ms 49.508 ms
10 gbr1-p60.sl9mo.ip.att.net (12.122.1.241) 54.915 ms 40.013 ms 56.675 ms
11 ar4-a300s1.sl9mo.ip.att.net (12.123.24.89) 74.958 ms 42.220 ms 49.200 ms
12 12.215.4.65 (12.215.4.65) 55.109 ms 12.215.4.69 (12.215.4.69) 54.537 ms 47.413 ms
13 12.215.14.98 (12.215.14.98) 62.395 ms 54.832 ms 56.645 ms
14 12-217-28-127.client.mchsi.com (12.217.28.127) 69.648 ms 61.367 ms 54.071
ms

And just to make this clear, I'm not saying this IS the problem, I'm saying it COULD be the problem. It may very well turn out to be something else, but at this point since there aren't any firewalls or anything known to be in use, I would look at something like this as the culprit.

Sorry for all the multiple posts, one other thing I forgot to add. I have seen weird things like this also caused by incorrect MTU settings. If you've played around with the MTU settings on your home computer at all, I'd suggest setting them back to default and see if the problem goes away.

Thanks for the tip.
I did not play with MTU settings at all, and I can access any other web site on the Internet just fine, even the host's homepage.

The host just came back to me with the traceroute results:


The traceroute will get aborted because of hte firewall. Anyway I will give below the result. I hope that will be of some use. Thank you.

root@jenn [/home]# /usr/sbin/traceroute 66.75.31.174
traceroute to 66.75.31.174 (66.75.31.174), 30 hops max, 38 byte packets
1 66-232-14-220.wholesalecolo.com (66.232.14.220) 2995.894 ms !H 2990.390 ms !H 2999.904 ms !H


Can you see anything?

Yep, I can see that wholesalecolo.com's router has no idea where the packet needs to be routed, so it's just dying. This is your web hoster's problem all the way.

To elaborate on my last post. Basically the !H in the traceroute means that the router is reporting that the host is unreachable. This should not be caused by a firewall blocking traceroutes. You'd most likely get !X or just * * * if there was a firewall disallowing traceroutes.