For some reason I can't connect to Stockholm servers in Matchmaking. I just get "connection failed after 4 retries" and if I click View Game Info on a friend that is on a Stockholm server I can't see any players and it says "server not responding".
What could be causing this? I've never used the CS:GO MM Server Picker and have every windows/antivirus firewalls disabled.
For some reason I can't connect to Stockholm servers in Matchmaking. I just get "connection failed after 4 retries" and if I click View Game Info on a friend that is on a Stockholm server I can't see any players and it says "server not responding".
What could be causing this? I've never used the CS:GO MM Server Picker and have every windows/antivirus firewalls disabled.
a friend of mine had a similar problem with Luxembourg so it kept giving him abandons and after a few times it reset his rank from 6ish back to #freshmeat be careful about getting too many abandons if you dont wanna lose your rank
a friend of mine had a similar problem with Luxembourg so it kept giving him abandons and after a few times it reset his rank from 6ish back to #freshmeat be careful about getting too many abandons if you dont wanna lose your rank
Possibly verify game cache i guess
Possibly verify game cache i guess
146.66.156.167 is an IP for the stockholm servers, can you ping it at all?
146.66.156.167 is an IP for the stockholm servers, can you ping it at all?
tigid-Possibly verify game cache i guess
I did, I also reinstalled my game and nothing happened.
I also reduced my In-Game server browser: Max pings/minute to 500 as some people had this problem with MvM.
Gemmellness146.66.156.167 is an IP for the stockholm servers, can you ping it at all?
C:\Users\Owner>ping 146.66.156.167
Pinging 146.66.156.167 with 32 bytes of data:
Reply from 146.66.156.167: bytes=32 time=74ms TTL=46
Reply from 146.66.156.167: bytes=32 time=74ms TTL=46
Reply from 146.66.156.167: bytes=32 time=74ms TTL=46
Reply from 146.66.156.167: bytes=32 time=74ms TTL=46
Ping statistics for 146.66.156.167:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 74ms, Maximum = 74ms, Average = 74ms
- - -
Is this good or bad?
[quote=tigid-]Possibly verify game cache i guess[/quote]
I did, I also reinstalled my game and nothing happened.
I also reduced my In-Game server browser: Max pings/minute to 500 as some people had this problem with MvM.
[quote=Gemmellness]146.66.156.167 is an IP for the stockholm servers, can you ping it at all?[/quote]
C:\Users\Owner>ping 146.66.156.167
Pinging 146.66.156.167 with 32 bytes of data:
Reply from 146.66.156.167: bytes=32 time=74ms TTL=46
Reply from 146.66.156.167: bytes=32 time=74ms TTL=46
Reply from 146.66.156.167: bytes=32 time=74ms TTL=46
Reply from 146.66.156.167: bytes=32 time=74ms TTL=46
Ping statistics for 146.66.156.167:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 74ms, Maximum = 74ms, Average = 74ms
- - -
Is this good or bad?
biskuitC:\Users\Owner>ping 146.66.156.167
Pinging 146.66.156.167 with 32 bytes of data:
Reply from 146.66.156.167: bytes=32 time=74ms TTL=46
Reply from 146.66.156.167: bytes=32 time=74ms TTL=46
Reply from 146.66.156.167: bytes=32 time=74ms TTL=46
Reply from 146.66.156.167: bytes=32 time=75ms TTL=46
Ping statistics for 146.66.156.167:
Packets: Sent = 4, Received = 4, Lost = 0 (0% lo
Approximate round trip times in milli-seconds:
Minimum = 74ms, Maximum = 75ms, Average = 74ms
- - -
Is this good or bad?
good i guess, means that the problem is likely with your game instead of PC/routing. bad news is im not sure how to fix it. a friend had a problem where he couldnt connect to luxembourg in quickplay at all, wonder if it's the same bug. did you try -default?
[quote=biskuit]
C:\Users\Owner>ping 146.66.156.167
Pinging 146.66.156.167 with 32 bytes of data:
Reply from 146.66.156.167: bytes=32 time=74ms TTL=46
Reply from 146.66.156.167: bytes=32 time=74ms TTL=46
Reply from 146.66.156.167: bytes=32 time=74ms TTL=46
Reply from 146.66.156.167: bytes=32 time=75ms TTL=46
Ping statistics for 146.66.156.167:
Packets: Sent = 4, Received = 4, Lost = 0 (0% lo
Approximate round trip times in milli-seconds:
Minimum = 74ms, Maximum = 75ms, Average = 74ms
- - -
Is this good or bad?[/quote]
good i guess, means that the problem is likely with your game instead of PC/routing. bad news is im not sure how to fix it. a friend had a problem where he couldnt connect to luxembourg in quickplay at all, wonder if it's the same bug. did you try -default?
-default gives me the same :(
-default gives me the same :(
i had this problem with virginia valve servers a while ago
it just disappeared at one point no idea why
i had this problem with virginia valve servers a while ago
it just disappeared at one point no idea why
I guess I'm just waiting for Valve to fix their shit as always.
The TF Team is literally full of retards.
I guess I'm just waiting for Valve to fix their shit as always.
The TF Team is literally full of retards.
biskuitI guess I'm just waiting for Valve to fix their shit as always.
The TF Team is literally full of retards.
the TF team is full of talented individuals that sometimes try to optimize the horrible framerate they achieved over the years
[quote=biskuit]I guess I'm just waiting for Valve to fix their shit as always.
The TF Team is literally full of retards.[/quote]
the TF team is full of talented individuals that sometimes try to optimize the horrible framerate they achieved over the years
Try going to steam -> settings -> in game and change server browser pings/min to a lower number than 4000 (like 500).
The rest of my post doesn't matter but you can read it if you want.
------
There's an option to reduce how fast you send requests to servers in steam. If you ping too fast it denies access because it thinks your ddosing it or something. The option somewhere in steam and it helped me when I couldn't connect to Virginia servers. The default is 4000 I think and I reduced it to 500 maybe? It was a while ago I don't really remember the specifics.
Sorry for the vague response but hopefully you can find the setting and change it. It's in steam not tf2.
Edit: I found the thread I used to fix the problem initially (it's a slightly different problem then yours but I wouldn't be surprised if it has the same solution)
http://steamcommunity.com/app/440/discussions/0/620713633847476540/
Try going to steam -> settings -> in game and change server browser pings/min to a lower number than 4000 (like 500).
The rest of my post doesn't matter but you can read it if you want.
------
There's an option to reduce how fast you send requests to servers in steam. If you ping too fast it denies access because it thinks your ddosing it or something. The option somewhere in steam and it helped me when I couldn't connect to Virginia servers. The default is 4000 I think and I reduced it to 500 maybe? It was a while ago I don't really remember the specifics.
Sorry for the vague response but hopefully you can find the setting and change it. It's in steam not tf2.
Edit: I found the thread I used to fix the problem initially (it's a slightly different problem then yours but I wouldn't be surprised if it has the same solution)
http://steamcommunity.com/app/440/discussions/0/620713633847476540/
Boomfan56Try going to steam -> settings -> in game and change server browser pings/min to a lower number than 4000 (like 500).
The rest of my post doesn't matter but you can read it if you want.
------
There's an option to reduce how fast you send requests to servers in steam. If you ping too fast it denies access because it thinks your ddosing it or something. The option somewhere in steam and it helped me when I couldn't connect to Virginia servers. The default is 4000 I think and I reduced it to 500 maybe? It was a while ago I don't really remember the specifics.
Sorry for the vague response but hopefully you can find the setting and change it. It's in steam not tf2.
Edit: I found the thread I used to fix the problem initially (it's a slightly different problem then yours but I wouldn't be surprised if it has the same solution)
http://steamcommunity.com/app/440/discussions/0/620713633847476540/
I already mentioned that I tried that and it didn't work unfortunately..
[quote=Boomfan56]Try going to steam -> settings -> in game and change server browser pings/min to a lower number than 4000 (like 500).
The rest of my post doesn't matter but you can read it if you want.
------
There's an option to reduce how fast you send requests to servers in steam. If you ping too fast it denies access because it thinks your ddosing it or something. The option somewhere in steam and it helped me when I couldn't connect to Virginia servers. The default is 4000 I think and I reduced it to 500 maybe? It was a while ago I don't really remember the specifics.
Sorry for the vague response but hopefully you can find the setting and change it. It's in steam not tf2.
Edit: I found the thread I used to fix the problem initially (it's a slightly different problem then yours but I wouldn't be surprised if it has the same solution)
http://steamcommunity.com/app/440/discussions/0/620713633847476540/[/quote]
I already mentioned that I tried that and it didn't work unfortunately..
I got this problem too, as far as I can tell it's only on Stockholm servers for me (other members of my stack could get in to check). I'm the guy who lost his rank and got reset to fresh meat, it happened when I was stacked with 6 other players, 4 got in while me and my local friend couldn't join. The only notable similarity between me and the other player who couldn't get in was our proximity to each other so I think this is all a ping issue, maybe we exceeded a max ping option. We both got our ranks reset while the coordinator found subs to play in our spots instead of calling it an abandon. Maybe only solo queue until they fix this, it seems like you can't get the abandon if you get this error in a solo queue.
I got this problem too, as far as I can tell it's only on Stockholm servers for me (other members of my stack could get in to check). I'm the guy who lost his rank and got reset to fresh meat, it happened when I was stacked with 6 other players, 4 got in while me and my local friend couldn't join. The only notable similarity between me and the other player who couldn't get in was our proximity to each other so I think this is all a ping issue, maybe we exceeded a max ping option. We both got our ranks reset while the coordinator found subs to play in our spots instead of calling it an abandon. Maybe only solo queue until they fix this, it seems like you can't get the abandon if you get this error in a solo queue.