CSS , CS 1.6 causing modem problems

Soldato
Joined
5 Jul 2009
Posts
3,704
Im having trouble trying to join css and 1.6 servers when im using the server browser my modem suddenly looses all connection with the internet for a while yet if I dont use the server browser I can still connect to servers fine through the console command :confused:

anyone have an idea for what it could be causing it ?
 
Last edited:
Probably your modem is getting flooded by too many responses from servers, when using the server browser it will be pinging and grabbing serverinfos from potentially hundreds of servers.

Never played the games myself but if they are designed properly you should be able to lower the number of pings per second the server browser is doing, and try putting some filters on to cut out unnecessary server responses.
 
Are you on Virgin media cable internet? Because I had the exact same probelem with TF2, I tried all the solutions offered on the internet but non of them worked. Since I have upgraded to 50MB from 20MB I don't have the problem anymore.
 
Similar problem occurs when Torrenting I presume? if so, then I would definitely look at upgrading the router or find a way of limiting the amount of connections the server browser does :)
 
Homehubs really dislike the steam server browser. Really, really dislike :(

Untill recently (Still does?) they wouldnt even accept connections for more then 20 seconds on L4D/2
 
Try going into steam settings>downloads and lowering the approximate download speed. It should slow down the flood of responses from using the server browser in game.

Similar thing happened to my friend years ago if he refreshed the server browser. The only fix we could find (apart from favourites) was to quickly start/stop refreshing within a few seconds.
 
Try going into steam settings>downloads and lowering the approximate download speed. It should slow down the flood of responses from using the server browser in game.

Similar thing happened to my friend years ago if he refreshed the server browser. The only fix we could find (apart from favourites) was to quickly start/stop refreshing within a few seconds.

didnt work sadly :( but yeah I have to do the same
 
Back
Top Bottom