Can't connect to some servers and websites

[arshiafaraji22]

Hey,
Its been a long time that i have this probelm.
i cant connect to some websites or servers with any device that use my wifi. But with vpn everything is okay.
Like i can't connect to psn, some steam based games like PUBG and many other websites even now i using vpn to be here.

And yeah i did talk to my isp, changed dns, restarted router, disable anti virus and fire wall.
I did everything and i still got this problem for 1 year.

 

[SugarPsycho]

Are you using DHCP or are you using a self-configured DNS server?

 

[arshiafaraji22]

Are you using DHCP or are you using a self-configured DNS server?

Yeah im using DCHP and i put my dns to automatic configure and its changes to my isp DNS. ( i already tried google dns and opendns , but still same )

 

[bill001g]

First try to use the NSLOOKUP command and see if it resolves and if it looks valid. You can also do nslookup www..... 8.8.8.8 for example to force it to use google. you can try a number of dns servers.

It it resolves but does not connect I would look at the firewall settings on your machines. Some times windows is too smart and decides for example your network is public.

You could see if ping works to the ip address. In general if it is a firewall type of block ping will work but web will not.

 

[arshiafaraji22]

First try to use the NSLOOKUP command and see if it resolves and if it looks valid. You can also do nslookup www..... 8.8.8.8 for example to force it to use google. you can try a number of dns servers.

It it resolves but does not connect I would look at the firewall settings on your machines. Some times windows is too smart and decides for example your network is public.

You could see if ping works to the ip address. In general if it is a firewall type of block ping will work but web will not.

Thanks for replies,
I did nslookup and it seems like it sets on my ISP dns.

And Im pretty sure there isnt any problem in devices' firewalls.

I forgot to say, If i try to connect to a server by keep disconnecting and connecting 10 times, it may connect. Like i close PUBG 10 times to play it every single match.

Thanks again

 

[anotherdrew]

That sounds more like high packet loss. Pull up a command prompt and do "ping -n 50 google.com". Let us know what you got as far as loss and min, max, and average time.

 

[arshiafaraji22]

That sounds more like high packet loss. Pull up a command prompt and do "ping -n 50 google.com". Let us know what you got as far as loss and min, max, and average time.

C:\Users\CSPN>ping -n 50 google.com

Pinging google.com [172.217.21.238] with 32 bytes of data:
Reply from 172.217.21.238: bytes=32 time=237ms TTL=49
Reply from 172.217.21.238: bytes=32 time=150ms TTL=49
Reply from 172.217.21.238: bytes=32 time=167ms TTL=49
Reply from 172.217.21.238: bytes=32 time=184ms TTL=49
Reply from 172.217.21.238: bytes=32 time=200ms TTL=49
Reply from 172.217.21.238: bytes=32 time=215ms TTL=49
Reply from 172.217.21.238: bytes=32 time=232ms TTL=49
Reply from 172.217.21.238: bytes=32 time=143ms TTL=49
Reply from 172.217.21.238: bytes=32 time=160ms TTL=49
Reply from 172.217.21.238: bytes=32 time=175ms TTL=49
Reply from 172.217.21.238: bytes=32 time=193ms TTL=49
Reply from 172.217.21.238: bytes=32 time=211ms TTL=49
Reply from 172.217.21.238: bytes=32 time=227ms TTL=49
Reply from 172.217.21.238: bytes=32 time=143ms TTL=49
Reply from 172.217.21.238: bytes=32 time=129ms TTL=49
Reply from 172.217.21.238: bytes=32 time=176ms TTL=49
Reply from 172.217.21.238: bytes=32 time=190ms TTL=49
Reply from 172.217.21.238: bytes=32 time=206ms TTL=49
Reply from 172.217.21.238: bytes=32 time=220ms TTL=49
Reply from 172.217.21.238: bytes=32 time=234ms TTL=49
Reply from 172.217.21.238: bytes=32 time=149ms TTL=49
Reply from 172.217.21.238: bytes=32 time=166ms TTL=49
Reply from 172.217.21.238: bytes=32 time=182ms TTL=49
Reply from 172.217.21.238: bytes=32 time=200ms TTL=49
Reply from 172.217.21.238: bytes=32 time=214ms TTL=49
Reply from 172.217.21.238: bytes=32 time=129ms TTL=49
Reply from 172.217.21.238: bytes=32 time=247ms TTL=49
Reply from 172.217.21.238: bytes=32 time=160ms TTL=49
Reply from 172.217.21.238: bytes=32 time=176ms TTL=49
Reply from 172.217.21.238: bytes=32 time=130ms TTL=49
Reply from 172.217.21.238: bytes=32 time=210ms TTL=49
Reply from 172.217.21.238: bytes=32 time=225ms TTL=49
Reply from 172.217.21.238: bytes=32 time=142ms TTL=49
Reply from 172.217.21.238: bytes=32 time=160ms TTL=49
Reply from 172.217.21.238: bytes=32 time=177ms TTL=49
Reply from 172.217.21.238: bytes=32 time=140ms TTL=49
Reply from 172.217.21.238: bytes=32 time=207ms TTL=49
Reply from 172.217.21.238: bytes=32 time=232ms TTL=49
Reply from 172.217.21.238: bytes=32 time=242ms TTL=49
Reply from 172.217.21.238: bytes=32 time=153ms TTL=49
Reply from 172.217.21.238: bytes=32 time=167ms TTL=49
Reply from 172.217.21.238: bytes=32 time=181ms TTL=49
Reply from 172.217.21.238: bytes=32 time=200ms TTL=49
Reply from 172.217.21.238: bytes=32 time=209ms TTL=49
Reply from 172.217.21.238: bytes=32 time=228ms TTL=49
Reply from 172.217.21.238: bytes=32 time=142ms TTL=49
Reply from 172.217.21.238: bytes=32 time=130ms TTL=49
Reply from 172.217.21.238: bytes=32 time=179ms TTL=49
Reply from 172.217.21.238: bytes=32 time=195ms TTL=49
Reply from 172.217.21.238: bytes=32 time=136ms TTL=49

Ping statistics for 172.217.21.238:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 129ms, Maximum = 247ms, Average = 184ms

I'm okay with google.



C:\Users\CSPN>ping -n 50 playstation.com

Pinging playstation.com [209.200.152.198] with 32 bytes of data:
Reply from 209.200.152.198: bytes=32 time=345ms TTL=240
Reply from 209.200.152.198: bytes=32 time=187ms TTL=240
Request timed out.
Request timed out.
Reply from 209.200.152.198: bytes=32 time=130ms TTL=240
Reply from 209.200.152.198: bytes=32 time=130ms TTL=240
Reply from 209.200.152.198: bytes=32 time=130ms TTL=240
Reply from 209.200.152.198: bytes=32 time=130ms TTL=240
Reply from 209.200.152.198: bytes=32 time=130ms TTL=240
Reply from 209.200.152.198: bytes=32 time=132ms TTL=240
Reply from 209.200.152.198: bytes=32 time=134ms TTL=240
Reply from 209.200.152.198: bytes=32 time=225ms TTL=240
Reply from 209.200.152.198: bytes=32 time=152ms TTL=240
Reply from 209.200.152.198: bytes=32 time=156ms TTL=240
Reply from 209.200.152.198: bytes=32 time=169ms TTL=240
Reply from 209.200.152.198: bytes=32 time=187ms TTL=240
Reply from 209.200.152.198: bytes=32 time=201ms TTL=240
Reply from 209.200.152.198: bytes=32 time=212ms TTL=240
Reply from 209.200.152.198: bytes=32 time=226ms TTL=240
Reply from 209.200.152.198: bytes=32 time=235ms TTL=240
Reply from 209.200.152.198: bytes=32 time=147ms TTL=240
Reply from 209.200.152.198: bytes=32 time=166ms TTL=240
Reply from 209.200.152.198: bytes=32 time=184ms TTL=240
Reply from 209.200.152.198: bytes=32 time=131ms TTL=240
Reply from 209.200.152.198: bytes=32 time=146ms TTL=240
Reply from 209.200.152.198: bytes=32 time=231ms TTL=240
Reply from 209.200.152.198: bytes=32 time=149ms TTL=240
Reply from 209.200.152.198: bytes=32 time=161ms TTL=240
Reply from 209.200.152.198: bytes=32 time=282ms TTL=240
Reply from 209.200.152.198: bytes=32 time=196ms TTL=240
Reply from 209.200.152.198: bytes=32 time=209ms TTL=240
Reply from 209.200.152.198: bytes=32 time=221ms TTL=240
Reply from 209.200.152.198: bytes=32 time=238ms TTL=240
Reply from 209.200.152.198: bytes=32 time=145ms TTL=240
Reply from 209.200.152.198: bytes=32 time=154ms TTL=240
Reply from 209.200.152.198: bytes=32 time=169ms TTL=240
Reply from 209.200.152.198: bytes=32 time=187ms TTL=240
Reply from 209.200.152.198: bytes=32 time=199ms TTL=240
Reply from 209.200.152.198: bytes=32 time=208ms TTL=240
Reply from 209.200.152.198: bytes=32 time=224ms TTL=240
Reply from 209.200.152.198: bytes=32 time=230ms TTL=240
Reply from 209.200.152.198: bytes=32 time=144ms TTL=240
Reply from 209.200.152.198: bytes=32 time=160ms TTL=240
Reply from 209.200.152.198: bytes=32 time=177ms TTL=240
Reply from 209.200.152.198: bytes=32 time=193ms TTL=240
Request timed out.
Reply from 209.200.152.198: bytes=32 time=257ms TTL=240
Reply from 209.200.152.198: bytes=32 time=230ms TTL=240
Reply from 209.200.152.198: bytes=32 time=235ms TTL=240
Reply from 209.200.152.198: bytes=32 time=151ms TTL=240

Ping statistics for 209.200.152.198:
Packets: Sent = 50, Received = 47, Lost = 3 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 130ms, Maximum = 345ms, Average = 185ms

 

[anotherdrew]

Your ping times are on the high side and 6% loss is also higher than expected. You said this happens on all devices connected to WiFi. Does it also happen to wired devices?

From a command prompt run "tracert google.com". The first router listed should be yours, the second your ISP (unless you have 2 routers or a router and a modem ... then the 3rd would be your ISP).

Please do the ping again, but this time use the address of your router and your ISP. Please copy the last 4 lines of the ping report here.

 

[arshiafaraji22]

Your ping times are on the high side and 6% loss is also higher than expected. You said this happens on all devices connected to WiFi. Does it also happen to wired devices?

From a command prompt run "tracert google.com". The first router listed should be yours, the second your ISP (unless you have 2 routers or a router and a modem ... then the 3rd would be your ISP).

Please do the ping again, but this time use the address of your router and your ISP. Please copy the last 4 lines of the ping report here.

Actually this ping is normal here. Yeah It does happen in wired device too.

Ping statistics for 192.168.1.1:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 3ms, Average = 2ms

My ISP:

Ping statistics for 94.183.36.1:
Packets: Sent = 50, Received = 49, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 196ms, Average = 34ms

 

[anotherdrew]

Your ping inside your network is fine. The ping to your ISP is not. This could be due to their router being overwhelmed by traffic. It could be a line issue, but you said the ISP tested the lines. Do you know others in the neighborhood using the same ISP? Do they have the same problem?

 

[arshiafaraji22]

Your ping inside your network is fine. The ping to your ISP is not. This could be due to their router being overwhelmed by traffic. It could be a line issue, but you said the ISP tested the lines. Do you know others in the neighborhood using the same ISP? Do they have the same problem?

Yeah I have friend he gets his internet from same ISP and same service I use. He got no problem.

 

[anotherdrew]

Ask your friend to do the tracert to see if you guys go through the same router (94.183.36.1). If so, does he get the same result if he pings it. If his results are better than yours, then you might have an issue with your line or even the router/modem. Your ISP should be able to run tests on the line without sending a technician to your home.