[quote1207517863=RAF 2008]
I had the exact same problem not so long ago. If you haven't already tried, type the following into the developers console:
rate 10000
cl_updaterate 30
cl_cmdrate 100
It worked fine for me after doing that.
[/quote1207517863]
Those numbers don't quite match up... I'll explain their meaning/usage (with default values):
rate '20000' : Bytes per second sent from server to client. With a high-speed connection, it should probably be 8k-16k (test it out with net_graph). If you are experiencing 'choke' (more data sent than client can receive), lower this value.
cl_updaterate '20' : Number of updates per sec client requests from server. Modern acceptable values are anywhere from 60-100, but keep in mind eGO's server have it capped at 60.
cl_cmdrate '30' : Number of command packets you send to the server per second. It's less of a setting to tweak for ping, but more for responsiveness. The most accepted value tends to be 'avg fps + 10'.
There are other applicable commands (cl_lagcompensation, cl_cmdbackup, cl_interp, cl_smoothtime), but those you definitely shouldn't touch unless you absolutely know what you are doing.
FWIW, as long as you don't go changing the settings in the console, Steam handles it well enough if you set the proper speed in the Steam options.