Can't see website through RR?
Mathias Mosinski
I have the following problem. I am trying to access my website(just started)
and upload a new version. I can't seem to access it through my RR cable
service. I can telnet to my school's network and access the website from
their system.
This is a tracert from my computer:
F:\Documents and Settings\Matt>tracert mosinski.net
Tracing route to mosinski.net [66.78.36.190]
over a maximum of 30 hops:
1 22 ms 18 ms 20 ms dt036n01.san.rr.com [24.30.141.1]
2 26 ms 20 ms 18 ms dt036n01.san.rr.com [24.30.141.1]
3 20 ms 7 ms 8 ms ubr6-fe0-0.san.rr.com [24.25.192.105]
4 23 ms 14 ms 14 ms gsrc-pos0-0.san.rr.com [24.25.192.102]
5 21 ms 11 ms 16 ms pop1-las-P7-0.atdn.net [66.185.137.137]
6 70 ms 12 ms 28 ms bb2-las-P0-0.atdn.net [66.185.137.133]
7 25 ms 31 ms 26 ms bb2-sun-P5-0.atdn.net [66.185.152.46]
8 36 ms 25 ms 25 ms bb2-sje-P0-2.atdn.net [66.185.153.49]
9 28 ms 20 ms 25 ms pop1-sje-P6-0.atdn.net [66.185.138.102]
10 89 ms 81 ms 83 ms sl-gw11-sj-4-3.sprintlink.net
[144.228.44.45]
11 92 ms 84 ms 94 ms sl-bb25-sj-6-1.sprintlink.net
[144.232.3.133]
12 85 ms 90 ms 91 ms sl-gw8-sj-10-0.sprintlink.net
[144.232.3.114]
13 54 ms 39 ms 38 ms sl-cogentcomm-7-0.sprintlink.net
[144.228.110.12
2]
14 76 ms 42 ms 57 ms p6-0.core01.sfo01.atlas.cogentco.com
[66.28.4.14
5]
15 105 ms 179 ms 117 ms p14-0.core01.ord01.atlas.cogentco.com
[66.28.4.4
1]
16 125 ms 124 ms 147 ms p15-0.core02.ord01.atlas.cogentco.com
[66.28.4.6
2]
17 166 ms 103 ms 108 ms p6-0.core02.jfk02.atlas.cogentco.com
[66.28.4.85
]
18 123 ms 104 ms 99 ms p6-0.core01.jfk01.atlas.cogentco.com
[66.28.4.12
2]
19 110 ms 169 ms 116 ms
g50.ba01.b002894-1.jfk0101.atlas.cogentco.com [6
6.28.65.146]
20 120 ms 108 ms 102 ms VDI.demarc.cogentco.com [66.250.4.118]
21 122 ms 108 ms 105 ms pos.core2.cft.vdi.net [66.78.63.246]
22 118 ms 112 ms 105 ms ge.edge1.cft.vdi.net [66.78.63.250]
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.
This is the traceroute from my school's computer:
ieng9.ucsd.edu% traceroute mosinski.net
traceroute to mosinski.net (66.78.36.190), 30 hops max, 40 byte packets
1 muir-rs-fddi (132.239.50.247) 1.491 ms 1.070 ms 1.499 ms
2 node-b-msfc--muir-rsm (132.239.255.162) 0.622 ms 0.504 ms 0.518 ms
3 ucsd-gw--node-b-msfc (132.239.255.142) 0.600 ms 0.667 ms 0.590 ms
4 192.12.207.125 (192.12.207.125) 7.348 ms 5.113 ms 5.251 ms
5 65.119.29.93 (65.119.29.93) 7.051 ms 6.924 ms 7.019 ms
6 205.171.13.13 (205.171.13.13) 7.410 ms 7.119 ms 13.131 ms
7 205.171.8.41 (205.171.8.41) 11.913 ms 7.522 ms 7.185 ms
8 205.171.19.38 (205.171.19.38) 7.525 ms 7.313 ms 7.271 ms
9 205.171.1.130 (205.171.1.130) 8.061 ms 7.435 ms 7.436 ms
10 tbr2-p012402.la2ca.ip.att.net (12.122.11.221) 27.046 ms 28.080 ms
8.686 ms
11 tbr2-p013701.sl9mo.ip.att.net (12.122.10.90) 57.337 ms 54.651 ms
75.375 ms
12 tbr1-p012401.sl9mo.ip.att.net (12.122.9.141) 76.156 ms 55.298 ms
57.446 ms
13 tbr1-p013201.wswdc.ip.att.net (12.122.11.233) 72.874 ms 92.614 ms
71.927 ms
14 * * *
15 gar1-p3100.nwrnj.ip.att.net (12.123.214.181) 74.406 ms 73.592 ms
73.935 ms
16 12.119.140.50 (12.119.140.50) 73.983 ms 74.120 ms 73.981 ms
17 pos.core2.cft.vdi.net (66.78.63.246) 75.562 ms 75.532 ms 75.230 ms
18 ge.edge1.cft.vdi.net (66.78.63.250) 75.465 ms 75.263 ms 75.991 ms
19 alexandria.unixhoster.com (66.78.36.190) 75.498 ms 75.825 ms 75.315
ms
"alexandria.unixhoster.com" is the name of the webserver.
I can ping the server from my school's network, but it won't work from home.
How come, I can't access the site? I recently installed a wireless router
between the cable modem and my computer. I believe it worked until about a
week ago or so.
Can anyone help me figure this one out?
Mathias
cablenetguy
message news:aktstq$1kugng$1...@ID-2112.news.dfncis.de...
It doesn't look like a problem with Roadrunner since your traceroute
goes out past the network and dies at hop 22.
Both ISP's resolve your domain to the same IP so it's not a dns
problem and I can traceroute there no problem.
It just appears to me that there was a problem with the
router -ge.edge1.cft.vdi.net [66.78.63.250]- at the time you performed
the traceroute from your roadrunner account at home.
Try it again and see if you can trace it this time.
--
Mark.....otherwise known as
-------------
Cablenetguy
Mathias Mosinski
>
> It doesn't look like a problem with Roadrunner since your traceroute
> goes out past the network and dies at hop 22.
> Both ISP's resolve your domain to the same IP so it's not a dns
> problem and I can traceroute there no problem.
> It just appears to me that there was a problem with the
> router -ge.edge1.cft.vdi.net [66.78.63.250]- at the time you performed
> the traceroute from your roadrunner account at home.
> Try it again and see if you can trace it this time.
>
> --
>
> Mark.....otherwise known as
>
> -------------
> Cablenetguy
I did some tests and realized that it would work if I would connect my
computer directly to the cable modem instead of going through the router. I
also noticed that the IP assigned to the computer would differ from the one
assigned to the router. I had the option in the router setup to clone the
mac address of the network adapter. After I tried that the ip of the router
was changed and I was able to browse to the website. This seems to have
resolved the issue.
Mathias
Kip Patterson
Mathias Mosinski wrote:
You're reaching the website without problems - if you get to the last
router, it is forwarding the packet to the website. It can't
distinguish between the two source IP addresses.
What is happening is that somewhere along the reverse path to you there
is a router that does not know how to correctly route a packet to your
IP.. That is why forcing an IP change fixes the problem.
Kip
Paul Mulcahy
<mathiasmosinsk...@gmx.de> wrote:
>Hi,
>
>I have the following problem. I am trying to access my website(just started)
>and upload a new version. I can't seem to access it through my RR cable
>service. I can telnet to my school's network and access the website from
>their system.
>Mathias
>
Almost every time this happens to someone with a new website, the
files he wants to view have been uploaded to the wrong directory. You
might want to make sure that your files are where RR says they need to
be.
--
It isn't whether you win or lose, it's where you
place the blame.
Mathias Mosinski
Thanks.
"Kip Patterson" <ripa...@columbus.rr.com> wrote in message
news:3D73B049...@columbus.rr.com...