can't connect

[acolyte_to_jippity]

So, suddenly i can't connect to pub or gg.

i go into my fav. list, and i'll only have 2 of the 4 ibis servers in it, i hit 'refresh' and sometimes they'll chane which are displayed, sometimes they'll just disappear completely. i right-click on one and examine it's info and it will say server not responding. refreshing that screen fixes it for zm and wcs, but pub and gg will remain blank. i can then join zm or wcs, but pub and gg will eventually refuse the connection because of 4 retries.

wtf?

[ZERO]

They are online so it is either valve or your steam or your internet or valve.

[acolyte_to_jippity]

well, possibble sol'ns?

this started last night

[taz1stP]

he really hates valve he puts them in there twice lol

[DJ_MikeyRevile]

1. Check your valve status...
2. do you have the proper ports open? (change routers recently?)
3. restart compy in safe mode and do a spyware and maleware scan
4. uninstall

[acolyte_to_jippity]

"valve status"?

no changes to routers.

i'll try the malware scan

[DJ_MikeyRevile]

"valve status"?

no changes to routers.

i'll try the malware scan

Valve status as in vac banned in good standing ect...

not saying your "vac banned" that is.

if the scans dont help then let me know.

also is there any errors that pop up? or that you see in console when trying to join.

[acolyte_to_jippity]

no, it's just "connection failed after 4 retries"

console just has:
connecting to <ip address here>...
connecting to <ip address here>...
connecting to <ip address here>...
connecting to <ip address here>...
connection abborted after 4 retries


or something like that

[DJ_MikeyRevile]

no, it's just "connection failed after 4 retries"

console just has:
connecting to <ip address here>...
connecting to <ip address here>...
connecting to <ip address here>...
connecting to <ip address here>...
connection abborted after 4 retries


or something like that


Have you tried cl_allowdownload commands?
cl_allowupload
or
cl_downloadfilter

?? These being used if its permitted that is.

also you might want to check your internet restrictions. Firewall up? Router acting screwy?

Do a full analysis of your problem and write it here, then im sure zero or another who knows more then i do can help indefinitely.



edit: BUT before you even concern yourself with ANY of this... Try just Deleting your entire cstrike folder, restart steam, then open CSS again.

[acolyte_to_jippity]

edit: BUT before you even concern yourself with ANY of this... Try just Deleting your entire cstrike folder, restart steam, then open CSS again.

LITERALLY, nothing has changed. at least, that i know of. it's possible drexel changed something in their internet...but i doubt it.

i'll try deleteing cstrike...tomorrow. i'll need to back up my materials/models/sounds etc... folders to keep my skins intact

[acolyte_to_jippity]

deleteing cstrike did nothing, just fucked up all my skins.

malwareBytes found nothing

i tried manually pinging each server (in order pub,gg,zm,wcs):

C:\Users\adam2>ping 208.43.70.232

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

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

C:\Users\adam2>ping 208.43.70.233

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

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

C:\Users\adam2>ping 208.43.70.234

Pinging 208.43.70.234 with 32 bytes of data:
Reply from 208.43.70.234: bytes=32 time=19ms TTL=118
Reply from 208.43.70.234: bytes=32 time=8ms TTL=118
Reply from 208.43.70.234: bytes=32 time=7ms TTL=118
Reply from 208.43.70.234: bytes=32 time=8ms TTL=118

Ping statistics for 208.43.70.234:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 19ms, Average = 10ms

C:\Users\adam2>ping 174.36.201.114

Pinging 174.36.201.114 with 32 bytes of data:
Reply from 174.36.201.114: bytes=32 time=19ms TTL=118
Reply from 174.36.201.114: bytes=32 time=7ms TTL=118
Reply from 174.36.201.114: bytes=32 time=7ms TTL=118
Reply from 174.36.201.114: bytes=32 time=7ms TTL=118

Ping statistics for 174.36.201.114:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 19ms, Average = 10ms