I can’t host games in Warcraft. I can’t figure out how to allow it in Comodo. I know I have to allow tcp in/out for ports 6112-6119, but I can’t figure out how I do that. I know I have to add a rule in Predefined Firewall Policies. I tried the following rules, but they didn’t work. Source address: any, Destination address: any, Source port: 6112-6119, Destination port: 6112-6119. I tried changing source port to any while not touching destination port, and I tried changing source port back to 6112-6119 and changing destination port to any. But like I said, it didn’t work. Am I supposed to restart warcraft every time I change the rules? I can’t figure out what I’m doing wrong. Please help me.
- Create the following rule in Network Security Policy - Global Rules:
Action: Allow
Protocol: TCP or UDP
Direction: In/Out
Source Address: Any
Destination Address: Any
Source Port: Port Range (6112 - 6119)
Destination Port: Port Range (6112 - 6119)
Make it the first rule in the list.
- In Network Security Policy - Application Rules locate the Warcraft’s executable (should be there by now) and assign the “Trusted Application” policy to it.
See if the game works. If it doesn’t, check the firewall log (Firewall - Common Tasks - View Firewall Events) to see if anything related to warcraft is being blocked.
If the game works:
- Switch the Warcraft’s executable to Custom Policy, create two rules for it:
a)
Action: Allow
Protocol: TCP or UDP
Direction: In/Out
Source Address: Any
Destination Address: Any
Source Port: Port Range (6112 - 6119)
Destination Port: Port Range (6112 - 6119)
b)
Action: Block
Protocol: IP
Direction: In/Out
Source Address: Any
Destination Address: Any
Source Port: Any
Destination Port: Any
Same procedure here: if it stopped working, check the Firewall Events to see what’s going on.
This is strange. It doesn’t work and there aren’t any logs at all. What on earth am I doing wrong.
Does it work when firewall is disabled (rightclick on icon in tray->firewall->disabled)?
No that doesn’t work either. This is really strange. I re-installed windows yesterday, so it’s not like I have installed many programs. What on earth could be blocking my hosting ability on battlenet. I can easily join other games, but I can’t host any.
billward,
Whether COMODO is blocking your connections or not, you should see the game’s executable listening on some port(s) in Firewall - Common Tasks - View Active Connections when you run the game as a server. Do you see that?
The destination is port 6112. The source ports seem very random.
So, you see active connetions belonging to the game’s executable there, right? If you do, then I would say COMODO isn’t the problem. I mean - proper rules, no alerts, nothing in the logs, active connections seen… nothing indicates that the firewall interferes with the game. Did the game ever work before you installed Comodo?
The game worked fine before I re-installed windows. And before I re-installed windows I had comodo too. I checked my router and the settings are correct there too. Could it possibly be a Kaspersky/comodo conflict?
Edit: I just got this message frim Kaspersky, while I was waiting for a game to start (not hosting): The application [warcraft] cannot establish connection with the server 217.157.204.160. Please check your internet connection settings. If you have a firewall installed, check that the application avp.exe is allowed internet access.
Before I re-installed windows I had comodo v2. Now I use v3.
There may well be some misunderstanding between Warcraft, Kaspersky’s HTTP scanner (or whatever the part that scans the internet traffic is called) and COMODO. I’m not sure about the earilier versions, but Kaspersky 7 intercepts outgoing connections to predefined ports (HTTP, POP3, stuff like that) before COMODO notices it, so to COMODO it looks like the avp.exe establishes them. I have no idea if Kaspersky interferes with incoming connections the same way.
Anyway, disabling the Kaspersky HTTP scanner to see if something changes may be a good idea.
I found the bug. Somehow windows firewall had not been disabled when I installed comodo. I hadn’t checked that, because windows firewall should normally be disabled when you install a new firewall. Thanks for the help. And btw (L)