Updating CS:Source and UUnet

Skippy

New Member
Joined
Apr 1, 2005
Messages
9
Reaction score
0
Is anyone else having problems updating CS:Source with UUNet? Been updating for the last 2 days and its gone up from 95% to 96%!
Just wondering if its somthing on my side, or if there is any kind if port shaping or anything.

Thanks
 
Look at the thread with UUNET problems - they're busy upgrading their intl. bandwidth link to Miami.
 
With regards to UUNet's ADSL, in many cases Steam will connect to an international server instead of a local one such as SGS. At the moment UUNet is experiencing a fair amount of performance issues over their international links, which will have a negative effect on any services that go international. Unfortunately I don't believe there's any way to force Steam to go to a specific server for updates.
 
basically dump uunet for something better
rather have a cap and be able to use it then have no cap and bad conn
 
Naah, I figure, if I where on Telkscum, I would already be capped, 6 days into the month, which basically = no internet conenction to me.
 
So far uunet is better than a capped telkom account. The problem I believe is, they need to start shape Bittorent as well, like they do with the rest of the p2p applications, then their uncapped solution will be perfect. Why? Every person I know that has uunet adsl uses it to download p2p bittorent 24/7 and that is why international latencies and bandwidth suck now, because p2p is one of the worst things that have hit the internet.

It will be a shame if they change their uncapped adsl to a cap/payasyougo solution instead of shaping the applications that hurt their international links...
 
mine's updated fine but i find that pinging the server helps to keep the connection alive and kicking as they're not exactly a beacon of speed..

just put in the command prompt
ping -t -l 1 -w 25000 <server ip or url>
 
Top
Sign up to the MyBroadband newsletter
X