Forum Post
Index > Website > cant get to memecode.com

Author/Date cant get to memecode.com
exosceleton
08/03/2007 8:05am
I've got a small, but a weird problem.

When setting up my parents first dsl connection (yes, my mother is going online!) i connected all the wires, booted up and behold: I was connected to the world.

Next step was getting her my favorite email client... one guess wich one that is. I type www.memecode.com...... and nothing. mmmm. Website down, that is irregular for fret. So i checked on my (GPRS) mobile phone... all was well.
I tried a webproxy on the dsl machine... all was well.

But still i cannot connect the normal way trough a web browser.

The dsl helpdesk suggested TRACERT, wich reported a timeout at some local internet backbone. Thinking it was a server connected to the dsl provider i tried the tracert on a machine where i can connect to memecode.

Now the weird part.

the good tracert path runs over the same server, and ends at mail.gmn-usa.com.
mail.gmn-usa.com has the same ip adress as memecode.com: 216.157.143.53.
Something i thought, but i cannot claim a very big expertise on the subject, was impossible.

now i'm stumped. Is there anyone that can shed some light on the (probably perfectly reasonable) situation?
fret
08/03/2007 8:27am
What happening is that a number of domains are hosted on the same machine, mail.gmn-usa.com is one, and www.memecode.com is another. The web server on that machine uses the incoming HTTP request to work out which site the user is after. This is called virtual hosting, it's very common in the web hosting industry.

I'm not sure your parents ISP is not getting through but I suggest you email their support staff. Issues like this are usually due to some mis-configuration in their routers. Send the tracert output too... that usually helps a lot.
exosceleton
08/03/2007 9:13am
I contacted the helpdesk, they will respond somewhere in June probably.

I hoped to see tracert stop dead on one of there servers, then i could blame them more easily. Now they will probably say "see, it's not our fault".

I asked the helpdesk guy if he could see memecode.com, as they are probably on the same network. His response was that he could not check because he was not connected to (translate: allowd on) the internet. He's a real bundle of help.

Allso i contacted the company that i think the problem server belongs to, but as i am not affiliated with their company in any way i don't think i'm a priority.

we'll see.

Thanks fret.
exosceleton
08/03/2007 9:16am
in case anyone stumbling by this forum might know something:
the bad tracert:
/////////////////////////////////////////////////////////
C:\>tracert memecode.com

Tracing route to memecode.com [216.157.143.53]
over a maximum of 30 hops:

1 40 ms 100 ms 100 ms dsldevice.lan [192.168.1.254]
2 61 ms 30 ms 110 ms 195.190.249.12
3 70 ms 30 ms 60 ms iawxsrt-dc2-bb21-ge-3-1-0.302.wxs.nl [213.75.1.5
]
4 40 ms 61 ms 200 ms te3-3.mpd01.ams03.atlas.cogentco.com [195.69.144
.124]
5 70 ms 80 ms 40 ms t10-0-0.core01.ams03.atlas.cogentco.com [130.117
.0.237]
6 60 ms 90 ms 70 ms p1-0.core02.lon01.atlas.cogentco.com [130.117.1.
110]
7 120 ms 190 ms 140 ms p9-0.core02.jfk02.atlas.cogentco.com [66.28.4.25
3]
8 140 ms 170 ms 131 ms p15-0.core01.jfk02.atlas.cogentco.com [66.28.4.1
3]
9 140 ms 190 ms 181 ms p9-0.core01.atl01.atlas.cogentco.com [154.54.5.9
8]
10 150 ms 140 ms 141 ms p14-0.core01.jax01.atlas.cogentco.com [154.54.3.
198]
11 160 ms 251 ms 190 ms p12-0.core01.mia01.atlas.cogentco.com [66.28.4.1
45]
12 200 ms 181 ms 190 ms g0-2.na21.b006686-0.mco01.atlas.cogentco.com [66
.250.13.14]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
////////////////////////////////////////////////////////////////////////////////



the good one:
--------------------------------------------------------------------------------
C:\Documents and Settings\Administrator>tracert memecode.com

Tracing route to memecode.com [216.157.143.53]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 16 ms 16 ms 16 ms 83.160.44.1
3 16 ms 15 ms 15 ms tc1-core-1-ge-4-0-1-0.router.nl.demon.net [82.16
1.255.33]
4 16 ms 15 ms 16 ms tc1-border-2-ge-0-0-0-0.router.nl.demon.net [82.
161.255.38]
5 16 ms 16 ms 16 ms 43.10ge-1-2-0.xr3.3d12.xs4all.net [194.109.7.169
]
6 16 ms 15 ms 16 ms 0.so-0-0-0.xr2.3d12.xs4all.net [194.109.5.201]
7 16 ms 16 ms 16 ms 0.so-7-0-0.xr1.tc2.xs4all.net [194.109.5.14]
8 16 ms 16 ms 16 ms te3-3.mpd01.ams03.atlas.cogentco.com [195.69.144
.124]
9 16 ms 16 ms 16 ms t10-0-0.core01.ams03.atlas.cogentco.com [130.117
.0.237]
10 23 ms 23 ms 23 ms p1-0.core02.lon01.atlas.cogentco.com [130.117.1.
110]
11 94 ms 94 ms 94 ms p9-0.core02.jfk02.atlas.cogentco.com [66.28.4.25
3]
12 93 ms 92 ms 92 ms p15-0.core01.jfk02.atlas.cogentco.com [66.28.4.1
3]
13 109 ms 110 ms 110 ms p9-0.core01.atl01.atlas.cogentco.com [154.54.5.9
8]
14 116 ms 116 ms 116 ms p14-0.core01.jax01.atlas.cogentco.com [154.54.3.
198]
15 119 ms 119 ms 119 ms p12-0.core01.mia01.atlas.cogentco.com [66.28.4.1
45]
16 120 ms 120 ms 120 ms g0-2.na21.b006686-0.mco01.atlas.cogentco.com [66
.250.13.14]
17 120 ms 121 ms 120 ms RapidColo.demarc.cogentco.com [38.112.14.122]
18 120 ms 120 ms 121 ms barney.rapidcolo.com [216.81.79.9]
19 121 ms 121 ms 123 ms mail.gmn-usa.com [216.157.143.53]

Trace complete.
--------------------------------------------------------------------------------
Reply