Can't access http://www.facebook.com, but m.facebook.com works

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??

Have you tried https? I believe http is no longer ok although I got there using your link. Weird,I know.

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

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.

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.

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

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 not
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

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.

while most of yours will be different, the last line MUST be

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

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.

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).

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.

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.

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

• 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

If post #12 is correct, then accessing www.facebook.com will fail while accessing

• www.google.com
• www.yahoo.com
• www.twitter.com

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.