You may cancel your Bitdefender subscription from Bitdefender Central or by contacting Customer Support at: https://www.bitdefender.com/consumer/support/help/
Thank you for your understanding.
Firewall Blocking Access To Wildstar
Hi, I hope someone can help me.
I'm unable to login in to the WildStar MMO while the BitDefender firewall is running. I have created application rules in the firewall for the Wildstar executables (wildstar.exe, wildstar64.exe and houston64.exe), but these don't seem to be enough to allow the game to connect to the authentication servers. I can only connect by disabling the firewall entirely.
I've checked the firewall logs and these lines seem to reference IP address ranges for Wildstar:
2014/06/30 21:00:37.329 [BDFW] [FILTER] Blocked packet because of rule 35. Direction: Outbound, Local Address: 192.168.1.10:137, Remote Address: 207.46.101.29:137, Protocol: 17, Local Packet: 0, PID: 4, Process: system, Cmd. Line: .
2014/06/30 21:00:38.829 [BDFW] [FILTER] Blocked packet because of rule 35. Direction: Outbound, Local Address: 192.168.1.10:137, Remote Address: 207.46.101.29:137, Protocol: 17, Local Packet: 0, PID: 4, Process: system, Cmd. Line: .
2014/06/30 21:00:40.329 [BDFW] [FILTER] Blocked packet because of rule 35. Direction: Outbound, Local Address: 192.168.1.10:137, Remote Address: 207.46.101.29:137, Protocol: 17, Local Packet: 0, PID: 4, Process: system, Cmd. Line: .
How do I identify rule 35?
Also, is there any way to delete the firewall logs and start fresh?
Thanks.
Comments
-
Oops, I think those IP addresses are Microsoft, must have got mixed up when checking the logs.
How can I check to see what rules are preventing Wildstar from connecting?
For now I have worked around the issue by adding 65.25.32.0/20 and 206.127.144.0/20 as zones on my wireless adapter. I assume this means that the firewall is ignoring traffic to those addresses?0
