Also, I forgot to mention that I'm behind an app called "Cisco Clean Access Agent" in order to get on the internet.

You are not going to be able to play multiplayer. I don't know how many times I've already said this, but there is a big difference between simply having ports OPEN/ALLOWED and ports/traffic FORWARDED. Your University would have to FORWARD ALL incoming traffic to them on TCP ports 6112, 6000 for the game to work with its current network structure. I don't see that happening. (Not to mention, that even if they "forwarded" those ports to only you, that cisco CAA would most definately be setup to not allow the game traffic).


the Monk

That's right, you don't need the ports forwarded unless you're wanting to HOST, however since many SOHO routers tie NAT-relaxing to port-forwarding forwarding the traffic even when not wanting to host is the best way to make sure that everything will work just fine (including "migrating" to another host should the original host disconnect).

The OP has other issues though:

1. He seems to have to run a UNI-provided firewall-client (the Cisco CAA) which almost certainly is why he can't connect. (the admins there would have to make exceptions for Sins in the cisco software)

2. For hosting they (the UNI) would have to "forward" all traffic on the two TCP ports to his system. (which we both know won't be done)


the Monk

Does anyone even read my posts? lol (as I remember saying this a few times already.......or maybe that was a dream I had....hehe)

TCP = connection-oriented protocol (very stable, and in essence is like a telephone conversation, both sides need to "acknowledge" message transmission)


UDP = connection-less protocol (great for spamming, like using a "walkie-talkie" instead of a telephone)


"Most" of the games you're talking about use mainly UDP as their transport backbone. Sins uses TCP so that it can provide a stable game environment (ie. updates between client locations aren't GUESSED at, they're VERIFIED) When you're playing an FPS or another RTS and you see "teleporting", "bullets dissapearing" etc. blame UDP not lag!


Having said all this,

TCP requires (for most things) bi-directional traffic. Which means the HOSTS and CLIENTS are treated the same and therefore need the same attention to network config.

UDP requires nothing of the client, just send, send and send the data, IF the data gets there, great, if NOT I'll just send it again. This means the HOSTS require network config, but the clients can be as dumb as doornails, just keep spamming that network traffic!    Highly in-efficient network code!


thanks,

the Monk

That's right! How many of those require "bi-directional" transport on said ports that isn't using NAT-T type "tunneling"?




Most people that you cannot connect-to, or stay connected-to are contributers to your connection woes themselves. I know I've said that before somewhere.   




Where does it say that a game has to work in every capacity for everyone? Having said that, the devs are constantly improving everything about Sins. I'm sure the hosting issues will be mitigated with another update.

Your main issue (not being able to connect to games) is actually being "worsened" by the HOSTS (without knowing it) of the games you're trying to connect to. Re-read my thread on NAT-filtering and you'll understand exactly what I'm talking about (the HOSTS not relaxing their NAT enough, and you at the university are probably behind a strict-NAT setup). The NAT issue is often mitigated by employing "port-forwarding" which unfortunately you aren't in a position to do.


the Monk