WAKI MIKO!1RAYMOObes   10/07/28(Wed)17:37

your router has to create an entry in the NAT table for every server you query and then look up the specific entry for every answer it receives. this uses a lot of cpu and can easily slow down weak routers. furthermore the table size is limited, so it may delete previous entries, such as normal http/tcp connections.

i dunno if there is a setting that limits how many servers the server browser queries at once.

another "solution" is to set up your PC as an exposed host, which simply forwards all packages to your computer and disables NAT. i wouldnt recommend this though as it is a security risk

>>5668

Considering I'm only refreshing either my favorites or friends serverlists, with less than 25 entries in each at any given time, does that still sound like the cause?

I used to get NAT errors in the router's logs when I'd do a masterlist refresh in COD4, but that was querying a lot more servers, and TF2 never did it before now so that's why idgi

Grayman !cPS3sUXjaM   10/07/28(Wed)18:07

http://blog.roberthallam.org/2008/05/tf2-lost-connection-to-server-solved/

I had to do this recently despite it never being a problem before, so I guess something has changed connections-wise

I had the same issue, fixed it by setting the download speed for Steam to 256k/DSL.

Of course, now it's deciding it wants to be unplayable now that I've upgraded to Windows 7.

Stuttering and hanging up the ass. None of the "fixes" I've found have worked.

Goddammit.

Nevermind that, apparently my version of TF2 hates running in 64bit. -32bit as a launch parameter cleared everything up.