facebook not working wireless

Toggle sidebar Toggle sidebar
Status
Not open for further replies.
S

stulljack

Honorable
Jan 23, 2014
2
0
10,510
Facebook/Firefox works wired & on wireless Droid Tablets but not on wireless laptops, 1Toshiba/Win7 & 1 Acer/Win Vista with a D-link wireless router. First noticed 7 pm EST.
 
Solution
Murissokah
Very weird. Your DNS is fine and you can trace up to your local level 3's tier 1 network server in less than 80ms, then it drops. I guess you could try using a different DNS server to hope the site will redirect you to another route, something like opendns (208.67.222.222) or Google's public DNS (8.8.8.8), though that's a long shot.

Just to be sure, the same device can access through the other network (192.168.1.x) and not through the WiFi network (192.168.0.x)?

I know this is going to sound lame, but did you try restarting your routers? This sometimes works because it refreshes their cache.
Sort by date Sort by votes
COLGeek

COLGeek

Cybernaut
Moderator
Apr 6, 2009
54,251
3,433
179,340
Double check your date/time settings (including the proper time zone) on the devices that can't connect to FB. Accurate time is needed for the certificate exchange between your system and FB servers. This is a common cause of such issues.
 
Upvote 0 Downvote
Murissokah

Murissokah

Distinguished
Aug 12, 2007
1,451
94
19,940


What is your network setup? A single router with ethernet+WiFi+WAN or one for ethernet/WAN and another for WiFi? Is it just facebook that doesn't work? Does it get to the site at all? Please try runing pings and traces from both interfaces and paste the results for us. (if you don't know how to, press win button, type cmd, type ping www.facebook.com, then do the same and type tracert www.facebook.com).

 
Upvote 0 Downvote
S

stulljack

Honorable
Jan 23, 2014
2
0
10,510
One for ethernet/WAN (consolidated communications)and another for WiFi D-link. It is just facebook that doesn't work. Does not reach page. The connection has timed out. The server at www.facebook.com is taking too long to respond.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

From Toshiba/Firefox:

C:\Users\Tim>ping www.facebook.com

Pinging star.c10r.facebook.com [31.13.69.80] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 31.13.69.80:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\Tim>tracert www.facebook.com

Tracing route to star.c10r.facebook.com [31.13.69.80]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1
2 1 ms 1 ms 1 ms Zhone.Home [192.168.1.1]
3 28 ms 27 ms 28 ms 72.22.30.178.nauticom.net [72.22.30.178]
4 27 ms 27 ms 28 ms gibs-isp-acc-hr0-e10-11.consolidated.net [72.22.
30.205]
5 28 ms 28 ms 28 ms tctr-isp-cor-hr2-e3-1.consolidated.net [72.22.17
.6]
6 28 ms 27 ms 29 ms te1-8.na41.b016104-1.pit02.atlas.cogentco.com [3
8.104.120.129]
7 28 ms 28 ms 28 ms vl3809.mag01.pit02.atlas.cogentco.com [38.20.55.
209]
8 28 ms 28 ms 28 ms te4-1.ccr01.pit02.atlas.cogentco.com [154.54.5.1
10]
9 39 ms 38 ms 37 ms te0-7-0-25.mpd22.dca01.atlas.cogentco.com [154.5
4.7.117]
10 38 ms 39 ms 38 ms be2112.ccr41.iad02.atlas.cogentco.com [154.54.5.
233]
11 38 ms 38 ms 37 ms 4.68.63.173
12 39 ms 40 ms 78 ms ae-4-90.edge2.Washington4.Level3.net [4.69.149.2
08]
13 FACEBOOK-IN.edge2.Washington4.Level3.net [4.53.114.46] reports: Destinatio
n net unreachable.

Trace complete.

C:\Users\Tim>ping www.facebook.com

 
Upvote 0 Downvote
Murissokah

Murissokah

Distinguished
Aug 12, 2007
1,451
94
19,940
Very weird. Your DNS is fine and you can trace up to your local level 3's tier 1 network server in less than 80ms, then it drops. I guess you could try using a different DNS server to hope the site will redirect you to another route, something like opendns (208.67.222.222) or Google's public DNS (8.8.8.8), though that's a long shot.

Just to be sure, the same device can access through the other network (192.168.1.x) and not through the WiFi network (192.168.0.x)?

I know this is going to sound lame, but did you try restarting your routers? This sometimes works because it refreshes their cache.
 
Upvote 0 Downvote
Solution
R

r0aaad

Reputable
Mar 4, 2014
21
0
4,510
I need help with this as well. I am using a Router/WIFI and a DLINK Mobile Companion DIR-505 to connect to internet with my PC.

This is my results:


"C:\Users\r0ad>ping www.facebook.com

Pinging star.c10r.facebook.com [2a03:2880:f006:801:face:b00c:0:1] with 32 bytes
of data:
Reply from 2a03:2880:f006:801:face:b00c:0:1: time=40ms
Reply from 2a03:2880:f006:801:face:b00c:0:1: time=40ms
Reply from 2a03:2880:f006:801:face:b00c:0:1: time=43ms
Reply from 2a03:2880:f006:801:face:b00c:0:1: time=46ms

Ping statistics for 2a03:2880:f006:801:face:b00c:0:1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 46ms, Average = 42ms

C:\Users\r0ad>tracert www.facebook.com

Tracing route to star.c10r.facebook.com [2a03:2880:f006:801:face:b00c:0:1]
over a maximum of 30 hops:

1 3 ms 3 ms 3 ms dsldevice.lan [2001:2002:5ae3:5326:a6b1:e9ff:fe7
d:50ec]
2 * * * Request timed out.
3 26 ms 22 ms 20 ms 2001:2000:4020:12::1
4 24 ms 23 ms 21 ms kbn-b4-link.ipv6.telia.net [2001:2000:3080:30f::
1]
5 70 ms 46 ms 47 ms adm-b5-v6.telia.net [2001:2000:3018:d::1]
6 41 ms 46 ms 46 ms facebook-ic-156922-adm-b5.c.telia.net [2001:2000
:3080:65e::2]
7 39 ms 41 ms 48 ms po126.msw01.09.ams2.tfbnw.net [2620:0:1cff:dead:
bef0::145]
8 42 ms 43 ms 44 ms edge-star6-shv-09-ams2.facebook.com [2a03:2880:f
006:801:face:b00c:0:1]

Trace complete."

Any thoughts?
 
Upvote 0 Downvote
COLGeek

COLGeek

Cybernaut
Moderator
Apr 6, 2009
54,251
3,433
179,340

Start your own thread. Thanks.
 
Upvote 0 Downvote
Status
Not open for further replies.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom