Facebook, google, youtybe won't load, the rest do

isamedin

Posts: 11   +0
Hello, I have dell inspiron 1564, 4 gb ram i3 processor 2.13 ghz . win 8, firefox
changed using the router to my cell hot spot, then the problem above showed up. the websites time out. I can load yahoo.com and all internet mail , such as gmail and hotmail , etc. plus other websites
I ping them and they timed out( 4 trials failed). ran ipconfig and the dell wifi is fine and have an ip address and a dns connection. no virus and no malware infection. used chrome and win ie and I got the same results.
noticed that the websites that load, load a little bit slower. also ran ipconfig to flush the dns , but no change.
I chaned te fire fox network setting to no proxy, that didn't help either

would appreciate the help
 
Last edited:
Thanks v. much, but I don't have a TCP problem , nor generally web connection, as I can connect to several websites and can ping them ok.
the problem is connecting to facebook and google.com and youtube. I can connect to yahoo.com or gmail or hotmail and other webs as I did before, and all the changes I made was using my cell phone as a router (hot spot) and the problem with these specific websites started.
 
I ping them and they timed out( 4 trials failed).
Yes you DO have a TCP problem.
Ping by name is different than Ping by address, but that was explained in the reference.
 
Ok, I I ran ping for the loop command ( 127.0.0.1) and I gt the 4 replies. I ran ipconfg, sent 4 packets received, got my ip address my subnet mask and default gateway ip address.
also ping microsoft website (I.e. using domain name) ping will identify the domain name and the ip adress, the statement would say:
ping e13678.dspb.(...).net [23.195.61.481] with 32 bytes of data
that is the first line of the ping reply. it list the ip address of the domain name. and if you ping it you get the same results.
this happens with facebook, if you ping it with the domain name or with the ip adress. can't connect , and the same with youtube and google.com.
so is this a tcp/ip problem? would appreciate it if you explain
and what do you suggest to fix it?
many thanks
 
Ok, I
  1. I ran ping for the loop command ( 127.0.0.1) and I gt the 4 replies.
  2. I ran ipconfg, sent 4 packets received, got my ip address my subnet mask and default gateway ip address.
  3. also ping microsoft website (I.e. using domain name) ping will identify the domain name and the ip adress, the statement would say: ping e13678.dspb.(...).net [23.195.61.481] with 32 bytes of data
  4. that is the first line of the ping reply. it list the ip address of the domain name. and if you ping it you get the same results.
  5. this happens with facebook,
  6. if you ping it with the domain name or with the ip adress. can't connect , and the same with youtube and google.com.
so is this a tcp/ip problem? would appreciate it if you explain
and what do you suggest to fix it?
many thanks
Good report. #6 says your DNS is failing. The interface to DNS is NSLOOKUP, so try
  • NSLOOKUP facebook.com
  • NSLOOKUP youtube.com
  • NSLOOKUP google.com
The expected result looks like
NSLOOKUP facebook.com
Non-authoritative answer:
Server: dns-cac-lb-01.rr.com
Address: 209.18.47.61 << my dns

Name: facebook.com << the domain name you were testing
Addresses: 2a03:2880:f10d:83:face:b00c:0:25de << the ipv6 address
157.240.11.35 << the ipv4 address

There are THREE normal responses
  1. timeout
  2. notfound
  3. the one shown for facebook above
NOTFOUND means the domain is not registered
TIMEOUT means that nslookup can not access the DNS
 
Really appreciate your attention and patience,
so, I ran the nslookup, and I got my DNS ( gateway) ip address for all 3 commands( facebook, youtube and google.com) here what came back:
c:...\DELL>nslookup facebook.com
server : Unknown
Adress : 192.168.43.1

Non-authoritative answer:
Name : facebook.com
Adress:2a03:2880:f01c:800e:face:b00c:0:2
157.240.20.15
the same answer for google and youtube ( with different addresses)

then I ran ping for facebook ip address that came from nslook, and I got the usual request timed out the 4 times. I don't understand how the nslookup got the ip address yet I can't ping it

then I ran nslookup to yahoo,com ( I can access yahoo, no problem) and I got the a similar answer as above ( the same structure) with 2 ip addresses. ran ping with no problem.

I mean what can a surfer do without google.com?

by the way I'm in saudi arabia, that may explain the non-authoritative part.
also,maybe I should mention I have no problem getting those webs from my cell phone, the same one I'm using as a router, the problem comes up when trying accessing them via my laptop. the laptop connects ok with the hotspot(my cell) except can't connect with these 3 websites!!
sorry for the long post
take care
 
Last edited:
I'm in saudi arabia, that may explain the non-authoritative part
No, we all see this and it's normal - - to get an authoritative response, you need to know where the domain was registered AND then use their DNS address as the second parm to NSLOOKUP.
the laptop connects ok with the hotspot(my cell) except can't connect with these 3 websites!!
YES - - the hotspot IS THE PROBLEM. The connection is the WIFI, but that's not the same as the path to your ISP.

  1. connect to your hotspot
  2. be sure to disconnect all other connections
  3. get a Command Prompt and enter IPCONFIG /ALL >myTcp.txt
  4. followed by NOTEPAD myTcp.txt
now COPY all the content shown by notepad and PASTE that as your follow-up
 
No, we all see this and it's normal - - to get an authoritative response, you need to know where the domain was registered AND then use their DNS address as the second parm to NSLOOKUP.

YES - - the hotspot IS THE PROBLEM. The connection is the WIFI, but that's not the same as the path to your ISP.

  1. connect to your hotspot
  2. be sure to disconnect all other connections
  3. get a Command Prompt and enter IPCONFIG /ALL >myTcp.txt
  4. followed by NOTEPAD myTcp.txt
now COPY all the content shown by notepad and PASTE that as your follow-up
here it is:
Windows IP Configuration

Host Name . . . . . . . . . . . . : Dell
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet 5:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-ProtonVPN Windows Adapter V9
Physical Address. . . . . . . . . : 00-FF-AB-01-5D-8A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Ethernet 3:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Anchorfree HSS VPN Adapter #2
Physical Address. . . . . . . . . : 00-FF-1C-D0-AB-0C
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Ethernet 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Anchorfree HSS VPN Adapter
Physical Address. . . . . . . . . : 00-FF-36-90-0A-2D
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : F2-7B-CB-13-97-BB
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe FE Family Controller
Physical Address. . . . . . . . . : B8-AC-6F-53-E3-25
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Dell Wireless 1397 WLAN Mini-Card
Physical Address. . . . . . . . . : F0-7B-CB-13-97-BB
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::ac09:de65:2b90:edb1%12(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.43.110(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, March 15, 2018 10:28:45 AM
Lease Expires . . . . . . . . . . : Thursday, March 15, 2018 11:58:52 AM
Default Gateway . . . . . . . . . : 192.168.43.1
DHCP Server . . . . . . . . . . . : 192.168.43.1
DHCPv6 IAID . . . . . . . . . . . : 267418571
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-1A-FF-6D-F0-7B-CB-13-97-BB
DNS Servers . . . . . . . . . . . : 192.168.43.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{8DFBD60C-7F46-4555-8FCC-B9B6A67B90D8}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
 
The WiFi config shown is just fine and as you note, you can even access Techspot with it.

If you can't PING facebook using the hotspot, then the DNS is blocking it. try the NSLOOKUP FACEBOOK.COM -- it's being blocked if it times-out; then try NSLOOKUP TECHSPOT.COM -- it's unblocked if you get an address
 
BTW: your Default Gateway . . . . . . . . . : 192.168.43.1 is suspect to me at least. The gateway should be a public address from your Cell Provider. This address looks like it's connected to your router.

When I access via the cell hotspot, mine is Default Gateway . . . . . . . . . : 172.20.10.1
 
Hi there,
ran nslookup for facebook and got an ip address, ping-ed it and the 4 packets were lost ??
did the same with techspot and got the ip address, ran ping ( domain name and ip address ) and it was fine.

here is the cmd printout:
C:\Users\DELLL>nslookup www.facebook.com

Server: UnKnown
Address: 192.168.43.1

Non-authoritative answer:
Name: star-mini.c10r.facebook.com
Addresses: 2a03:2880:f11c:8083:face:b00c:0:25de
31.13.92.36
Aliases: www.facebook.com

C:\Users\DELLL>ping 31.13.92.36


Pinging 31.13.92.36 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

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

so the question is : why can I trace the ip address for facebook and not be able to ping it? it seems that not the DNS server blocking the request to facebook web site, isn't it?

listen, I really appreciate this, hope am not bogging your time. please take your time, there is no rush, I can still log to facebook and you tube from my cell phone ( the prime suspect) , despite the fact that I hate doing that looking on the stupid little screen, touching all over it trying to find a reply button or a sticher
you're good people
 
so the question is : why can I trace the ip address for facebook and not be able to ping it? it seems that not the DNS server blocking the request to facebook web site, isn't it?
WELL, isn't this fun! Correct, the DNS is not blocking - - somewhere upstream from you, that IP ADDRESS is being blocked - - let's find out where:
  • tracert 31.13.92.36 >trace.txt
  • notepad trace.txt
again COPY the content and PASTE as follow-up
 
WELL, isn't this fun! Correct, the DNS is not blocking - - somewhere upstream from you, that IP ADDRESS is being blocked - - let's find out where:
  • tracert 31.13.92.36 >trace.txt
  • notepad trace.txt
again COPY the content and PASTE as follow-up

ok, here it is:

C:\Users\DELLL>tracert 31.13.92.41

Tracing route to edge-z-1-p2-shv-01-frt3.facebook.com [31.13.92.41]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 193 ms 112 ms 118 ms 151.248.98.133
9 171 ms 118 ms 116 ms 151.248.96.28
10 146 ms 117 ms 153 ms 151.248.96.28
11 154 ms 116 ms 120 ms ae1.br02.fra1.tfbnw.net [80.81.195.40]
12 128 ms 118 ms 117 ms po116.asw01.fra2.tfbnw.net [31.13.24.224]
13 130 ms 115 ms 119 ms po213.psw02.fra3.tfbnw.net [157.240.34.229]
14 195 ms 117 ms 180 ms 173.252.67.81
15 157 ms 114 ms 121 ms edge-z-1-p2-shv-01-frt3.facebook.com [31.13.92.41]

Trace complete.
 
The first 7 are just the routers being configured to NOT respond to ping - - notice the trace just proceeds to the next, all the way to
31.13.92.41

This all says that the simple PING 31.13.92.41 and PING FACEBOOK.COM should respond AND so should your browser.
 
The first 7 are just the routers being configured to NOT respond to ping - - notice the trace just proceeds to the next, all the way to
31.13.92.41

This all says that the simple PING 31.13.92.41 and PING FACEBOOK.COM should respond AND so should your browser.


thanks v. much, it was - as you said- fun.
take care
 
would appear you are giving up...

well, I don't know what else to do, would love very much to access google.com and facebook from my laptop
this is the first time accessing them from my mobile, and let me tell you,I hate that.
have more ideas? love to hearing from you.
much thanks
 
well, I don't know what else to do, ....
Neither do I. The configuration data and tracing contradict your reported symptom. The system address for edge-z-1-p2-shv-01-frt3.facebook.com of 31.13.92.41 is responding to ping (meaning that the name AND address are not being blocked) and to me, my browsers ( IE, Chrome, Opera & Firefox) all access it (so the server is active too).

The one thing that bugs me the your Gateway address of 192.168.43.1 should not work for any website or ping reply as that is a LAN address and it should be a Public IP.

SO - - I don't know what else to do either.
 
Neither do I. The configuration data and tracing contradict your reported symptom. The system address for edge-z-1-p2-shv-01-frt3.facebook.com of 31.13.92.41 is responding to ping (meaning that the name AND address are not being blocked) and to me, my browsers ( IE, Chrome, Opera & Firefox) all access it (so the server is active too).

The one thing that bugs me the your Gateway address of 192.168.43.1 should not work for any website or ping reply as that is a LAN address and it should be a Public IP.

SO - - I don't know what else to do either.

hey Jobeard. hope all is well
I went back to the router and and every thing is ok now. interestingly though, we have a problem with the internet at work, so h hooked my phone with the desktop, and the same exact problem appeared. now my phone is the suspect( sony xperia xa pro or something). email is working anyway, so, no biggy.
thanks man
take care
 
IMO, it's not the phone itself, but the service provider - - who provides your service?
 
Back