Quote Originally Posted by Delsus View Post
What you fail to realise is what P2P means, it is Peer to Peer, SE's servers host the update, which is then passed to the first clients to update, they then upload what they have recived and also begin to host the update.

With a P2P system if there is server congestion SE is doing somthing badly wrong with thier systems, most of the patch comes from other people uploading, when SE mentioned congestion it was to avoid people realising they truth which is that thier patcher sucks.

SE should have realised that the ports there using are blocked by 99% of firewalls, what they could have done is set the patcher to scan for open unused ports and use those. Or just use a port that is open.

Utorrent is designed to adapt to firewall ports and work around closed ones, which is what SE need to do with thier patcher, a well designed P2P system will never need an end user to configure port forwarding because it opens a direct unsecured connection right to your PC, any port scanner will find it for an intruder to access your PC with no problems. This is the reason Utorrent has an option to randomise the port it uses.
- Many of us who are having the problem are knowledgeable people with proper port forwarding set up, so it has nothing to do with firewall configuration.
- Without you accepting incoming connections (e.g. forwarded ports) you can't receive data from people who can't accept incoming connections either, you can't reach them to ask for it, they can't reach you to offer it. Accepting incoming connections is integral for P2P networks.

Also having an open port won't automatically get you hacked, unless you are sony.