Internet issues, Spotify, Steam and Game Servers affected

Auratius

Reputable
Mar 17, 2015
5
0
4,510
Hey everyone,

On the 11th of November, my ISP (Telstra) said they were going to be making some changes to our local network infrastructure to improve network capacity. Since that day, I have been unable to connect to any game servers, steam, or watch any online tv shows (aside from netflix). I have narrowed the problem down to not being able to connect to foreign servers. I have contacted my ISP who have checked my router, my local cabling and have found no issues. Other symptoms include random wireless dropouts and a chrome error: ERR_NAME_NOT_RESOLVED
When I open Spotify, it does not connect immediately, it requires a reboot most times to connect to its online services, and the error shown is: Error Code 4.

I have extremely frustrated as I have not been able to play any online games, watch tv shows or even access the steam store. I would greatly appreciate any help.

Listed below are troubleshooting methods already tested:

- Flushing DNS (Both with Chrome and CMD)
- Clearing Cache
- Rebooting Router
- Setting different static IP address
- Setting DNS address (8.8.8.8, 8.8.4.4)
- Disabling all firewalls
- Resetting wireless adapter
- Testing multiple wireless adapters

I would really, really, really appreciate any help. This issue is painfully irritating.
Thank you :)

Yours,
Aura


 
Solution
What you want to do is run a continuous ping cmd from a window to 8.8.8.8. This is to see if you are losing connectivity to the DNS server. You can try 4.2.2.2 also which is a non google dns server.

If this looks good then I would use the NSLOOKUP command to see if you have actual DNS issues. Sometimes browsers lie and say it is DNS when it is something else.

First pick a location I will call it x.y.z.com as example and see if things work

NSLOOKUP x.y.z.com
NSLOOKUP x.y.x.com 8.8.8.8
NSLOOKUP x.y.z.com 4.2.2.2

The first is using whatever default DNS your pc/router is using. The second forces it to use google. The third forces it to use a level3 dns server.

Key is to see if you get responses at all. To a point you may get...
What you want to do is run a continuous ping cmd from a window to 8.8.8.8. This is to see if you are losing connectivity to the DNS server. You can try 4.2.2.2 also which is a non google dns server.

If this looks good then I would use the NSLOOKUP command to see if you have actual DNS issues. Sometimes browsers lie and say it is DNS when it is something else.

First pick a location I will call it x.y.z.com as example and see if things work

NSLOOKUP x.y.z.com
NSLOOKUP x.y.x.com 8.8.8.8
NSLOOKUP x.y.z.com 4.2.2.2

The first is using whatever default DNS your pc/router is using. The second forces it to use google. The third forces it to use a level3 dns server.

Key is to see if you get responses at all. To a point you may get different actual ip resolved. This may or may not be a issue. You need to try a couple different web sites to see if anything stands out.

If you get values from this command your network connectivity is fine and DNS is fine and something else is causing problems. Tends to be things like firewalls or virus software but it is extremely hard to say....other than it proves it is not an actual DNS issue.
 
Solution