I haven't been able to find a solution to this problem on the internet, it seems to be somewhat unique. I cannot load http://www.facebook.com BUT I can load m.facebook.com and only the mobile version of the site on my computer. It was alright in the beginning but it is getting kind of old now and I'd REALLY like to figure out how to make the normal url work again... Any thoughts??
Can't access http://www.facebook.com, but m.facebook.com works
- Thread starter LoganABarnes
- Start date
learninmypc
Posts: 9,679 +724
Have you tried https? I believe http is no longer ok although I got there using your link. Weird,I know.
D
DelJo63
Accessing the HTTP www.facebook.com automatically redirects to the HTTPS version (for me on Firefox 19.0 at least)
the m.facebook.com IS the mobile version and the 'M.' is causing that to happen
the m.facebook.com IS the mobile version and the 'M.' is causing that to happen
learninmypc
Posts: 9,679 +724
Ditto, I had to clean my glasses
I tried the https and I got this. The top is obviously the one that won't work and the bottom is all I can get to work.
learninmypc
Posts: 9,679 +724
Thats one of the reasons I dumped google chrome. I had to go into the privacy settings & allow it in the java part since I've disabled java in all my browsers. Using Firefox & SeaMonkey,I had no problem. Dump google chrome & stick with Firefox is my answer.
D
DelJo63
learninmypc :: Facebook is not dependent upon Java and G.C & FF both behave correctly
LoganABarnes :: the message has a ton of info but the problem in reality is in the last line
send packets to the destination.
get a command prompt (start->run and enter CMD or start->search and enter CMD)
1) find the address of facebook.com: enter NSLOOKUP WWW.FACEBOOK.COM and hit enter
I get an address 173.252.110.227
2) now enter PING WWW.FACEBOOK.COM
I get Reply from 173.252.110.27: bytes=32 time=87ms TTL=240 and your time=xxxms may be different OR
again TIMEOUT
3) also enter TRACERT WWW.FACEBOOK.COM
you should see something like
while most of yours will be different, the last line MUST be
If you see several like line 13 ( * * * Request timed Out) and do not see edge-star-ecmp-13-frc1.facebook.com [173.252.110.27],
then the problem is external to your system
Google itself seems to have input on this error
see this
LoganABarnes :: the message has a ton of info but the problem in reality is in the last line
Error 118 (net: ERR_CONNECTION_TIME_OUT) The operation timed out
This error does NOT mean there's anything at all wrong with your PC or settings - - it DOES MEAN that tcp can notsend packets to the destination.
get a command prompt (start->run and enter CMD or start->search and enter CMD)
1) find the address of facebook.com: enter NSLOOKUP WWW.FACEBOOK.COM and hit enter
I get an address 173.252.110.227
2) now enter PING WWW.FACEBOOK.COM
I get Reply from 173.252.110.27: bytes=32 time=87ms TTL=240 and your time=xxxms may be different OR
again TIMEOUT
3) also enter TRACERT WWW.FACEBOOK.COM
you should see something like
Code:
1 <1 ms <1 ms <1 ms localRouter [192.168.0.1]
2 34 ms 19 ms 19 ms cpe-108-184-144-1.socal.res.rr.com [108.184.144.1]
3 8 ms 9 ms 10 ms tge7-8.wlvgcabn-cer01.socal.rr.com [76.166.19.217]
4 14 ms 16 ms 14 ms tge0-8-0-8.vnnycajz-ccr01.socal.rr.com [72.129.13.96]
5 15 ms 15 ms 16 ms agg29.lsancarc-ccr01.socal.rr.com [72.129.13.0]
6 16 ms 15 ms 15 ms ae-5-0.cr0.lax00.tbone.rr.com [66.109.6.102]
7 13 ms 12 ms 15 ms ae-0-0.pr0.lax00.tbone.rr.com [66.109.6.135]
8 13 ms 12 ms 12 ms 66.109.9.206
9 77 ms 76 ms 98 ms FACEBOOK-INC.ethernet12-1.csr1.DCA3.gblx.net [64.215.81.234]
10 78 ms 78 ms 78 ms ae3.bb02.iad1.tfbnw.net [74.119.78.60]
11 79 ms 79 ms 79 ms ae8.bb04.frc1.tfbnw.net [31.13.24.95]
12 87 ms 89 ms 89 ms ae40.dr02.frc1.tfbnw.net [31.13.27.69]
13 * * * Request timed out.
[B]14 87 ms 88 ms 89 ms edge-star-ecmp-13-frc1.facebook.com [173.252.110.27][/B]
Trace complete.edge-star-ecmp-13-frc1.facebook.com [173.252.110.27]
If you see several like line 13 ( * * * Request timed Out) and do not see edge-star-ecmp-13-frc1.facebook.com [173.252.110.27],
then the problem is external to your system
Google itself seems to have input on this error
see this
learninmypc
Posts: 9,679 +724
jobeard, ok, but I know when I tried accessing facebook using google chrome, it would not let me until I went into the settings>Privacy>exceptions area I think it was & pasted the url in there to allow it.
Never had to do anything like that in FF or SeaMonkey.
I have java disabled in those browsers too.
Never had to do anything like that in FF or SeaMonkey.
I have java disabled in those browsers too.
D
DelJo63
that's a Chrome setting, not Java.
The object of the PING & Tracert is to determine if TCP and get there vs. is it some application setting (as you show) or perhaps a firewall setting (seen in other threads when searching for the error string given).
learninmypc
Posts: 9,679 +724
Not having google chrome any more, that path I showed is just a guess, but I won't argue
the point because I don't want to hijack the OP's thread.
the point because I don't want to hijack the OP's thread.
1. 8 ms 1 ms 1 ms 192.168.1.1
2. 8 ms 10 ms 9 ms 10.34.144.1
3. 9 ms 8 ms 11 ms 70.183.68.29
4. 15 ms 13 ms 15 ms ip70-183-68-29.ks.ks.cox.net [70.183.65.9]
5. 59 ms 33 ms 23 ms 70.183.66.246
6. 18 ms 17 ms 18 ms 70.183.71.66
7. * * * Request timed out.
8. 25 ms 28 ms 28 ms equinix.br01.dfw1.tfbnw.net [206.223.118.115]
9. 82 ms 96 ms 84 ms ae23.bb01.pao1.tfbnw.net [31.13.31.7]
10. 98 ms 95 ms 102 ms ae13.bb05.prn1.tfbnw.net [31.13.24.242]
11. 107 ms 105 ms 105 ms ae9.dr01.prn1.tfbnw.net [204.15.23.87]
12. * * * Request timed out.
13. * * * Request timed out.
14. * * * Request timed out.
15. * * * Request timed out.
16. * * * Request timed out.
17. * * * Request timed out.
18. * * * Request timed out.
19. * * * Request timed out.
20. * * * Request timed out.
21. * * * Request timed out.
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.
This is what was returned from my CMD. I tried what Chrome has suggested a few times now allowed facebook through chrome. I also allowed chrome in a text doc in my root files on my computer. After all of this I still get the same screen. I suppose I should have mentioned that this has been a problem since July 2012.
2. 8 ms 10 ms 9 ms 10.34.144.1
3. 9 ms 8 ms 11 ms 70.183.68.29
4. 15 ms 13 ms 15 ms ip70-183-68-29.ks.ks.cox.net [70.183.65.9]
5. 59 ms 33 ms 23 ms 70.183.66.246
6. 18 ms 17 ms 18 ms 70.183.71.66
7. * * * Request timed out.
8. 25 ms 28 ms 28 ms equinix.br01.dfw1.tfbnw.net [206.223.118.115]
9. 82 ms 96 ms 84 ms ae23.bb01.pao1.tfbnw.net [31.13.31.7]
10. 98 ms 95 ms 102 ms ae13.bb05.prn1.tfbnw.net [31.13.24.242]
11. 107 ms 105 ms 105 ms ae9.dr01.prn1.tfbnw.net [204.15.23.87]
12. * * * Request timed out.
13. * * * Request timed out.
14. * * * Request timed out.
15. * * * Request timed out.
16. * * * Request timed out.
17. * * * Request timed out.
18. * * * Request timed out.
19. * * * Request timed out.
20. * * * Request timed out.
21. * * * Request timed out.
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.
This is what was returned from my CMD. I tried what Chrome has suggested a few times now allowed facebook through chrome. I also allowed chrome in a text doc in my root files on my computer. After all of this I still get the same screen. I suppose I should have mentioned that this has been a problem since July 2012.
D
DelJo63
Hmm - - interesting. Notice my path enters TFBNW.NET at node 10, flows thru 10,11,12,13 and arrives at note 14 on frc1.facebook.com
yours enters TFBNW.NET at node 8 and flows thru 8,9,10,11 and NEVER finds facebook.com
What the node numbers are and the precise ip addresses are doesn't matter - - what does matter is
TFBNW.NET never flows into frc1.facebook.com [173.252.110.27]
the nodes I traverse ALL belong to facebook.com:
the nodes you traverse also ALL belong to facebook.com
This is a problem in the facebook network it self, not your computer.
I recommend you email the content of your last post (# 11) to the network administrator at
- 9 77 ms 76 ms 98 ms FACEBOOK-INC.ethernet12-1.csr1.DCA3.gblx.net [64.215.81.234]
- 10 78 ms 78 ms 78 ms ae3.bb02.iad1.tfbnw.net [74.119.78.60]
- 11 79 ms 79 ms 79 ms ae8.bb04.frc1.tfbnw.net [31.13.24.95]
- 12 87 ms 89 ms 89 ms ae40.dr02.frc1.tfbnw.net [31.13.27.69]
- 13 * * * Request timed out.
- 14 87 ms 88 ms 89 ms edge-star-ecmp-13-frc1.facebook.com [173.252.110.27]
yours enters TFBNW.NET at node 8 and flows thru 8,9,10,11 and NEVER finds facebook.com
- 8. 25 ms 28 ms 28 ms equinix.br01.dfw1.tfbnw.net [206.223.118.115]
9. 82 ms 96 ms 84 ms ae23.bb01.pao1.tfbnw.net [31.13.31.7]
10. 98 ms 95 ms 102 ms ae13.bb05.prn1.tfbnw.net [31.13.24.242]
11. 107 ms 105 ms 105 ms ae9.dr01.prn1.tfbnw.net [204.15.23.87]
12. * * * Request timed out.
13. * * * Request timed out.
14. * * * Request timed out.
What the node numbers are and the precise ip addresses are doesn't matter - - what does matter is
TFBNW.NET never flows into frc1.facebook.com [173.252.110.27]
the nodes I traverse ALL belong to facebook.com:
bb02.iad1.tfbnw.net [74.119.78.60]->bb04.frc1.tfbnw.net [31.13.24.95]->dr02.frc1.tfbnw.net [31.13.27.69]
and finally lead to -> 13-frc1.facebook.com [173.252.110.27]the nodes you traverse also ALL belong to facebook.com
br01.dfw1.tfbnw.net [206.223.118.115]->bb01.pao1.tfbnw.net [31.13.31.7]->bb05.prn1.tfbnw.net [31.13.24.242]->
....dr01.prn1.tfbnw.net [204.15.23.87]
but DO NOT LEAD TO 13-frc1.facebook.com [173.252.110.27]This is a problem in the facebook network it self, not your computer.
I recommend you email the content of your last post (# 11) to the network administrator at
D
DelJo63
If post #12 is correct, then accessing www.facebook.com will fail while accessing
will ALL succeed, showing the failure to be isolated to the facebook network
due to the path that YOU specifically use to get there - - the path can be very different depending where you are located globally
will ALL succeed, showing the failure to be isolated to the facebook network
due to the path that YOU specifically use to get there - - the path can be very different depending where you are located globally
I sent out the e-mail, and the weird thing is that I thought maybe being in california instead of Kansas would change anything. of course it didn't haha. I'll let you all know what the admin says about the issue.
Did you already know how to solve this error? I also encountered this error just now.And I dunno what to do &how to fixed it though I already use any browser. When I want to access Facebook, it looks like the image below...
Attachments
D
DelJo63
Go to \windows\system32\drivers\etc and use notepad to open the file HOSTS
find all entries with FACEBOOK and delete them
save and reboot
find all entries with FACEBOOK and delete them
save and reboot
Ok, found a GREAT fix that has actually worked over 95% of the time. If flushDNS does not work, then you need to activate the HTTPS service.
goto Start>Control Panel
Make sure the CP is in Icon mode, not Category mode.
Open Application Tools>Services.
Find the service HTTP SSL
Double click on it
Set the startup type to automatic and set the service to start.
The problem with this being disabled or in manual mode is that eventually your computer thinks HTTPS:// sites are bad for your system. No matter what you do this can be a problem, especially if you visit them alot. By enabling this, the HTTPS://facebook.com site that is now used will be enabled and you will be able to view facebook.
goto Start>Control Panel
Make sure the CP is in Icon mode, not Category mode.
Open Application Tools>Services.
Find the service HTTP SSL
Double click on it
Set the startup type to automatic and set the service to start.
The problem with this being disabled or in manual mode is that eventually your computer thinks HTTPS:// sites are bad for your system. No matter what you do this can be a problem, especially if you visit them alot. By enabling this, the HTTPS://facebook.com site that is now used will be enabled and you will be able to view facebook.
There is only one real solution and that is changing your DNS servers, see https://developers.google.com/speed/public-dns/docs/using?hl=nl
Just posting to confirm that willempie9's solution worked for me. I was getting similar results to the OP:
from $ ping facebook.com
from $ traceroute facebook.com
But it's now fixed and both ping and traceroute facebook.com are working properly. Hoorah!
If it helps someone else my situation was:
For me, the problem started happening when we switched ISPs. For my laptop, the problem only persists on my home network and not in other networks. Also, it would randomly occasionally connect to facebook.com through Chrome and sometimes in Facebook. m.facebook.com also worked for me when facebook.com didn't.
I guess the problem was just the ISPs DNS for my case.
from $ ping facebook.com
Code:
gku ~ $ ping facebook.com
PING facebook.com (37.61.54.158): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
...
--- facebook.com ping statistics ---
750 packets transmitted, 0 packets received, 100.0% packet lossfrom $ traceroute facebook.com
Code:
traceroute to facebook.com (37.61.54.158), 64 hops max, 52 byte packets
1 192.168.12.1 (192.168.12.1) 1.761 ms 1.223 ms 1.153 ms
2 10.123.60.129 (10.123.60.129) 7.987 ms 9.682 ms 12.133 ms
3 24.156.143.249 (24.156.143.249) 23.648 ms 16.602 ms 11.837 ms
4 69.63.248.201 (69.63.248.201) 14.283 ms 33.509 ms 15.728 ms
5 204.197.190.137 (204.197.190.137) 23.622 ms 13.029 ms 12.952 ms
6 v604.core1.tor1.he.net (209.51.164.49) 11.364 ms 13.180 ms 22.003 ms
7 100ge1-2.core1.nyc4.he.net (184.105.80.9) 26.253 ms 33.456 ms 26.541 ms
8 10ge1-2.core1.nyc5.he.net (72.52.92.165) 93.551 ms 91.282 ms 92.683 ms
9 xe-01.linx.london01-baku01.az-ix.net (195.66.225.235) 112.411 ms 103.710 ms 101.468 ms
10 deltatelecom-bk02-yellowxchange-ffm01.az-ix.net (85.132.60.69) 167.142 ms 171.346 ms 166.719 ms
11 r04-greenxchange-r02.az-ix.net (85.132.60.62) 165.458 ms 168.417 ms 160.183 ms
12 bakinternet-deltatelecom-link-for-internet-xchange.az-ix.net (85.132.2.246) 166.741 ms 166.853 ms 159.649 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *But it's now fixed and both ping and traceroute facebook.com are working properly. Hoorah!
If it helps someone else my situation was:
For me, the problem started happening when we switched ISPs. For my laptop, the problem only persists on my home network and not in other networks. Also, it would randomly occasionally connect to facebook.com through Chrome and sometimes in Facebook. m.facebook.com also worked for me when facebook.com didn't.
I guess the problem was just the ISPs DNS for my case.
yep m.facebook.com is cellphone mobility; http is internet explorer; https is secure server on chrome; www works with a secure browser....the only reason m.facebook.com works on a desktop is that it is signed in via chrome "anymore questions"
It all adds up to what browser is been used check the browser settings to see if the certificate is checked in the box or not. If its checked its secure if not checked it is http. That is on the chrome settings box. Browsing comes in many forms such as the search engine it could be Ask search engine the older browser for older computers or cellphones, or up to date searches with google, yahoo, or whatever....
Last edited by a moderator:
