Battman

>If it is a local, software firewall, like Zone >Alarm, you need to allow incoming connections >from your router in addition to opening the port. Hi, i already did that: >Just forwarding 7023 in router and firewall did >not do the job - i had to disable the firewall, >then the game finally loaded the scenario. Its Sygate firewall running here, and preventing unwanted connections in and out is its job. As far as i know, intelligent trojans or tools can exploit a combination of router, firewall and Winblows still. Also the firewall reported port scans sometimes. So switching the firewall off for combat mission is not a proper solution. I guess this is just another case where developers of a game know the main port, but not the other ports or services their game uses/requires. Ted, though it depends what you run on your computer, the xp firewall is not recommendable. Putting it short, its simple but therefore crap. My solution for now is the open several things up for the specific ip of the other player. Thats better than switching fw off completely. But also not a proper solution if he knows that. He could still set up some stupid tool, for example as "revenge" for having lost a recent game, or just out of boredom. K, seems i have to find out whats needed for myself. Maybe ill tell here if i find out.

Hi, i recently tried to set up a game via internet. Just forwarding 7023 in router and firewall did not do the job - i had to disable the firewall, then the game finally loaded the scenario. But being scanned is not what i like, so which ports or windows services are needed furthermore, except for port 7023, so i dont have to open the fw wide assed?