ICO Problem (yes another)

from Sins Forums
I just bought the Collectors Edition of SoaSE from stardock :), but i found one big prob when i want to play MP i always get kicked from Ironclad Online no matter what im doing , i cant join , i cant host , i cant even stay in lobby for more then 30 secs... I have a router (but never had problems with other games) and firewall+ Antivirus which i tried to turn off with no effect... 

Anyone have solution for this pls ?


btw game is full up to date
technical
2,847 views 7 replies
Reply #1 from Sins Forums Top

Yes the solution is you will need to forward ports (this game is true p2p).

Please download and read my guide "Networking and SINS" (not the other one) which is linked-to from the bottom of the "Technical FAQ" stickied in the "Technical" forum. My guide contains all of the information necessary in order to set things up correctly.

thanks,

the Monk
CursorFX - Customize your Windows cursor
Reply #3 from Sins Forums Top
Your router has its own hardware firewall. You can use the_Monk's advice or you can be lazy and just put your computer's network address into DMZ mode via your router's control tools and tell your software firewall that the Sins.exe program is safe (not sinslauncher.exe -- I think that's its name). That will take care of port forwarding for you, but be sure to turn off DMZ when you're done playing online. This is less safe than what is advised in the technical FAQ's, but if you have a fully-updated system with a software firewall running then you'll be just fine.
Reply #5 from Sins Forums Top
Well i got same prob again , dont know why i didnt mess with anything after it was working... Well i played for about 2 hours , then i went sleep, next day i wasnt working again. Still get disconnected from Ironclad Online , i tried port forwarding , DMZ , uPnP , disabling firewall. Nothing helped me.

my network map is - cable modem - router - pc...

Thx for any helpw
Reply #6 from Sins Forums Top
Same here. Was working fine, then not. This is first time I tried since upgrading to 1.03. Is this a problem with the new patch?