Problems accessing a web site

[joesnake]

We are having trouble accessing my wifes new web site from our virgin connection. The hosting company cannot find a problem.
Can any of you guys help by trying to to get onto:

www.mstanya.com (http://www.mstanya.com)


Thanks

[Druchii]

MsTanya will appear here soon.

No issues from Norway.

[Peter_]

We are having trouble accessing my wifes new web site from our virgin connection. The hosting company cannot find a problem.
Can any of you guys help by trying to to get onto:

www.mstanya.com (http://www.mstanya.com)


Thanks
Just says site under construction.

[STONEISLAND]

Just says site under construction.

[ro53ben]

There's a sub-forum for this...

http://www.cableforum.co.uk/board/80/

[joesnake]

Thanks guys.

I have bought the url and hosting for my wifes birthday on Friday and have just put up a holding page.

I can get to the site from work (not virgin) but not from my PC or laptop at home. Has anyone any ideas what is going wrong with my home cable connection and what I can do to resolve it by Friday.

The only relevant post in that sub-forum dates back to 2004. But if this post is in the wrong forum will someone please move it.

[spiderplant]

Can you post a traceroute? This is what I get

Tracing route to mstanya.com [208.43.104.135]
over a maximum of 30 hops:

1 79 ms 2 ms 2 ms
2 32 ms 32 ms 32 ms
3 32 ms 31 ms 32 ms
4 35 ms 37 ms 31 ms man-bb-a-as0-0.network.virginmedia.net [213.105.175.1]
5 39 ms 37 ms 38 ms gfd-bb-b-ae1-0.network.virginmedia.net [213.105.175.146]
6 41 ms 39 ms 39 ms redb-ic-1-as0-0.network.virginmedia.net [62.253.185.78]
7 132 ms 132 ms 132 ms 89.167.186.194
8 115 ms 116 ms 117 ms ip70-167-150-62.at.at.cox.net [70.167.150.62]
9 116 ms 116 ms 115 ms border1.te7-2-bbnet2.wdc008.pnap.net [216.52.127.98]
10 302 ms 116 ms 116 ms te1-1.cer01.wdc01.washingtondc-datacenter.com [66.151.100.66]
11 116 ms 117 ms 119 ms po1.fcr01.wdc01.washingtondc-datacenter.com [208.43.118.134]
12 116 ms 116 ms 116 ms ns12.sovdns.com [208.43.104.135]

Trace complete.

[joesnake]

spiderplant - I am at work at the moment. Will try when I get home tonight.

Thanks

[GazCBG]

I can get to it from my Virgin Connection in Lincoln

C:\Documents and Settings\Owner>tracert mstanya.com

Tracing route to mstanya.com [208.43.104.135]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 16 ms 6 ms
3 7 ms 8 ms 8 ms nott-cam-2a-v649.network.virginmedia.net [82.13.49.221]
4 7 ms 7 ms 10 ms nott-t3core-1a-ae3-0.network.virginmedia.net [195.182.175.129]
5 9 ms 9 ms 11 ms nott-t3core-1b-ge-100-0.network.virginmedia.net [80.1.79.98]
6 13 ms 10 ms 11 ms nth-bb-b-as1-0.network.virginmedia.net [213.105.174.173]
7 17 ms 23 ms 18 ms gfd-bb-a-so-100-0.network.virginmedia.net [213.105.175.137]
8 13 ms 14 ms 13 ms gfd-bb-b-ae0-0.network.virginmedia.net [213.105.172.6]
9 15 ms 27 ms 15 ms redb-ic-1-as0-0.network.virginmedia.net [62.253.185.78]
10 110 ms 125 ms 108 ms 89.167.186.194
11 93 ms 102 ms 92 ms ip70-167-150-62.at.at.cox.net [70.167.150.62]
12 94 ms 92 ms 93 ms border1.te7-2-bbnet2.wdc008.pnap.net [216.52.127.98]
13 94 ms 101 ms 94 ms te1-1.cer01.wdc01.washingtondc-datacenter.com [66.151.100.66]
14 105 ms 93 ms 95 ms po1.fcr01.wdc01.washingtondc-datacenter.com [208.43.118.134]
15 113 ms 93 ms 94 ms ns12.sovdns.com [208.43.104.135]

[joesnake]

Thanks so far guys. These are my results from home:-


Tracing route to mstanya.com [208.43.104.135]
over a maximum of 30 hops:

1 3 ms 1 ms 1 ms 192.168.1.1
2 9 ms 9 ms 9 ms 10.14.176.1
3 30 ms 9 ms 8 ms popl-t3core-1a-ge-500-1440.network.virginmedia.net [62.255.161.9]
4 25 ms 37 ms 8 ms pop-bb-a-as2-0.network.virginmedia.net [213.105.174.234]
5 37 ms 23 ms 11 ms pop-bb-b-ae0-0.network.virginmedia.net [213.105.174.230]
6 11 ms 11 ms 17 ms gfd-bb-a-so-010-0.network.virginmedia.net [213.105.172.137]
7 10 ms 10 ms 9 ms gfd-bb-b-ae0-0.network.virginmedia.net [213.105.172.6]
8 10 ms 13 ms 32 ms redb-ic-1-as0-0.network.virginmedia.net [62.253.185.78]
9 105 ms 114 ms 103 ms 89.167.186.194
10 92 ms 98 ms 91 ms ip70-167-150-62.at.at.cox.net [70.167.150.62]
11 * 93 ms 90 ms border1.te7-1-bbnet1.wdc008.pnap.net [216.52.127.36]
12 93 ms 91 ms 100 ms te1-1.cer01.wdc01.washingtondc-datacenter.com [66.151.100.66]
13 112 ms 95 ms 98 ms po1.fcr01.wdc01.washingtondc-datacenter.com [208.43.118.134]
14 * * * Request timed out.
15 *

[Wayfair]

And mine are pretty much the same as Spider and Garry.

[Peter_]

Tried another connection no problems connecting again and virtually instant.

[GazCBG]

Hi,

If you still having problems, try and contact your hosting provider as your IP maybe being blocked.

[joesnake]

Thanks all for your help.

Problem was with my router. As soon as I made a direct connection to the modem I could access the site, so it looks like a dying router. Oh well, was thinking of getting a new one anyway. Now I have to decide which one to get.

[ro53ben]

Before you replace it, try a factory reset of the router and re-configure it. Sometimes the config gets corrupted.

[joesnake]

Thanks for the advice ro53ben, I will try thatm, but I want to replace it with a wireless router.

[velocite]

GarryP is probably on the money with his blocked IP address suggestion.

When you connected directly to the cable modem it may have triggered the reallocation (from Virgin) of your external (Internet facing) IP address, giving you one which wasn't blocked by ns12.sovdns.com

Had you instead tried routing via an external proxy (e.g. webcache.virginmedia.com, port 8080) to hide your real external IP address, you'd probably have achieved a connection.

Due to the dynamic nature of IP address allocation from Virgin there's always the possibility of picking up an address which has been blocked by some websites due to past abuse (from spammers hijacking machines or spoofing addresses).

If you encounter the issue in the future, try the external proxy test before you start pulling cables.

[Joxer]

No reset required, as I have said before, it will be bogon filters, get the router to use you PCs Mac address (and reboot the modem) and all will be well through the router too. Most routers have this option.

If as suggested above a proxy fixes it, then so will this.

It is not a VM or router issue as you get to the last hop in the traceroute, beyond eithers influence.