First thank you for making such a good and free Firewall program. I love it. But now I am having a problem with Games For Windows LIVE in Fallout 3. This only happened recently where Comodo’s Firewall is blocking access for Fallout 3 to connect to GFWL. I have set Fallout 3 as a trusted application and it is still blocking it. Also I have set both ports 88 and 3074 to allow in the Global rules for both TCP and UDP.
Any suggestions would be great. As for right now disabling the firewall completely fixes the problem, but I don’t want to keep disabling it each time I go to play Fallout 3.
Yep the global rules are set to source any with a range. Here’s my global rules and Application Rules too for you. Thanks for the help.
Oh and I have tried to put the firewall in Training Mode to see if that works and it doesn’t. I must have a rule in here that’s blocking it. Also I normally run the firewall in Safe Mode.
EDIT: Just to add to this. I noticed this today in the firewall logs. Looks like Comodo is blocking port 3074 that is used for GFWL. Attaching a screenshot of the logs too. I’ve highlighted what I think are the ports Comodo is blocking for GFWL.
Now open TCP port 445 for incoming traffic:
Firewall → Advanced → Network Security policy → Global Rules → Add → fill in the following:
Description: Incoming Port VPM
Source address: Any
Destination Address: Choose MAC or Single IP address (only when it is fixed) or Host Name
Source Port: Any
Destination Port: 445
Then push Apply → Ok.
Make sure the rule is above the basic block rule (red icon) in Global Rules).
I will try that later but I suspect that is from my work VPN as it connects me to an IP of 10.200.255.169 usually.
I’ve attached another screenshot of my logs which may be of help too. I’ll make the change you suggested above and reply later tonight. Whats weird about this screenshot is that some requests come from Fallout 3 itself and some from Windows Operating System. Whats the difference?
I was looking again at your firewall logs and noticed that part of the time the destination address changed from 10.x.y.x to 169.254.1.100. Do you have a set top box or something similar in your network set up?
If not then yopur network adapter could not make a connection. When Windows doesn’t see a network to connect with it will hand out an IP address to your network adapter in the 169 range. Certain NVIDIA motherboard chipset come or came with a firewall option. Enabling that firewall is a known trouble maker. Disable it when you use it.
When you can’t connect to the GFWL server again check the firewall logs for the used IP address. Also check the status of your network adapter and see what IP address is used.
I do have an Nvidia motherboard but its older and doesn’t have the Nivida firewall. Also my routers gateway is set to 169.254.0.1. It’s normal for me to get a 169 IP. Infact my PC that’s running Fallout 3 has a static IP of 169.254.1.100. Again completely normal. The IP 10.x.x.x is for my work’s VPN. The VPN modifies my LAN IP to a work IP through the Cisco VPN Client, much in the same way Hamachi works.
Anything else you want think of Eric? It works fine when I disable Comodo Firewall.
You said you made D+ inactive. Did you permanently disabled it? You can permanently disable under D+ → Adavnced → Defense + Settings. Or did you install CIS without D+ (there is no D+ button in the main screen)?
Yep the 445 TCP rule is in there screenshot attached. It is an upgrade install. In fact I’ve been upgrading it since 2.x on this computer. I also imported settings from my 2.x install. Are you thinking what I’m thinking Eric? Do a complete fresh install, put the firewall in Training Mode and run the game?