HavocXphere
Honorary Master
I've been having some login troubles with steam lately & sorted it out so I figured I'd document it here and maybe help someone.
This applies mainly to those utilizing local content servers (WebAfrica/IS) in combination with steamwatch.
The Problem
Content servers are local and authentication servers are not. For some retarded reason Steam is designed to start downloading updates etc *whilst* trying to log in. The result is that the ADSL connection gets saturated with local downloads and the international ones time out meaning you get a connection problems message & the login fails.
384k and 512k people are particularly prone to this as the content servers can easily saturate those lines.
The Solution
Open your router admin page and find the QoS (Quality of Service settings).
Set port 27030 (UDP&TCP) to lowest priority
Set ports 27031-27039 (UDP&TCP) to highest priority
Optional: Find your steam shortcut and add -tcp to the end.
All of the above is based purely on my own trial & error and thus might be entirely wrong.
This applies mainly to those utilizing local content servers (WebAfrica/IS) in combination with steamwatch.
The Problem
Content servers are local and authentication servers are not. For some retarded reason Steam is designed to start downloading updates etc *whilst* trying to log in. The result is that the ADSL connection gets saturated with local downloads and the international ones time out meaning you get a connection problems message & the login fails.
384k and 512k people are particularly prone to this as the content servers can easily saturate those lines.
The Solution
Open your router admin page and find the QoS (Quality of Service settings).
Set port 27030 (UDP&TCP) to lowest priority
Set ports 27031-27039 (UDP&TCP) to highest priority
Optional: Find your steam shortcut and add -tcp to the end.
Remember you've probably got two shortcuts, one on your Desktop and one in your registry at HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run This forces TCP instead of UDP. Still undecided whether this has any effect as the QoS appears to fix the problem on its own.
All of the above is based purely on my own trial & error and thus might be entirely wrong.