Jump to content

Can't reach my homepage - Google.com !!!


Sepher
 Share

Recommended Posts

Since yesterday startup, I cannot reach my home page in firefox nor in

iexplorer, it is home page on both, it times out...

Have checked it is not in ie restricted zones, not in firewall, turned off

all av etc, still can't reach it. Tried adding it to hosts file with name

and ip of google (whois) and still no go.

I was able to reach it through anonymouse..

someone please help.

Thx

Seph

Link to comment
Share on other sites

Thanks for confirming it.

The next problem becomes everyone's. So many adservers out there on people's sites are fed by google, that many other sites are not loading properly either, and in the statusbar you can see adservergoogle etc...

crazy, never seen google get wiped before, tho I'm reading its not the 1st time.

~S~

Link to comment
Share on other sites

Heyas people!!

I think I may have a cure!! I have slight problems with Google too, but only when I use the new "Personalized homepage"... I found clearing the cache (in case you don't know, Tools> Internet Options, clicking Delete Cookies, and then Delete Files)... Google will default to using the usual homepage instead and should work. If not then I don't really know!!

-Javawag

Link to comment
Share on other sites

Try doing a traceroute on it, it sounds like it might be getting blocked somewhere. To open Command Prompt, click Start, click Run, type cmd, and then click OK, then type tracert google.co.uk.

You should get something like this:

traceroute www.google.co.uk

traceroute: Warning: www.google.co.uk has multiple addresses; using 66.102.9.104

traceroute to www.l.google.com (66.102.9.104), 30 hops max, 38 byte packets

1 10.188.16.1 (10.188.16.1) 13.744 ms 9.344 ms 6.540 ms

2 wapk-t2cam1-a-ge96.inet.ntl.com (80.1.170.69) 7.476 ms 12.541 ms 9.976 ms

3 popl-t2core-a-ge-wan63.inet.ntl.com (62.255.81.61) 7.837 ms 8.487 ms 28.162 ms

4 pop-bb-a-so-320-0.inet.ntl.com (62.253.185.65) 8.719 ms 7.511 ms 8.082 ms

5 nth-bb-b-so-400-0.inet.ntl.com (213.105.172.13) 30.479 ms 14.469 ms 13.582 ms

6 tele-ic-1-so-700-0.inet.ntl.com (62.253.184.2) 17.158 ms 14.120 ms 14.551 ms

7 212.250.14.66 (212.250.14.66) 30.741 ms 16.093 ms 17.250 ms

8 72.14.238.244 (72.14.238.244) 15.694 ms 72.14.238.240 (72.14.238.240) 16.251 ms 72.14.238.244 (72.14.238.244) 13.679 ms

9 216.239.49.254 (216.239.49.254) 54.961 ms 27.263 ms 25.498 ms

10 64.233.174.42 (64.233.174.42) 62.766 ms 26.019 ms 66.249.95.167 (66.249.95.167) 21.779 ms

11 64.233.174.14 (64.233.174.14) 26.394 ms 26.773 ms 65.142 ms

12 66.102.9.104 (66.102.9.104) 23.082 ms 22.751 ms 21.578 ms

The last address 66.102.9.104 is the address for google. The above is using Linux by the way, so yours will look slightly different.

If you want to paste it here it might give a clue what's happening. By the way, NTL have been having problems routing certain address for some reason, it seems to be some of the servers are timing out returning some of the packets because they are taking so long.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy