sreed

No sign of that false positive this morning. Thank you for the quick action.

I see the same thing. It's a valid TurboTax 2007 file. Looks like there's an overzealous heuristic . Let's hope they fix it soon.

Today I am not seeing any problems with VPN. Perhaps today's update included a patch for this bug.

@Acherner: I have also seen my network connections intermittently fail and self-heal since I installed BD. Perhaps it is delays due to BD processing that are causing timeouts. I don't know. That's something for the BD folks to own up to. So far these problems are tolerable but VPN not working when the firewall is enabled…

I agree. BitDefender's firewall implementation has LOT to be desired. The user interface is opaque and poorly documented. For example, I have not been able to figure out how to open or close a port. Instead there are a bunch of "modes" and "zones".

@Archerner: You don't mention disabling "Enable Intrusion detection system (IDS)" in Advanced Settings, but I'm guessing you've tried that. Also, note that I had to reboot to get it to work. Note, however, I found the VPN was broken again today. Luckily I have my router set up at home to filter pretty well so disabling the…

When I ping any IP address on the other side of the firewall I get all timeouts. I have Terminal Services and bdagent.exe running. This has been the case from the moment I installed BD Internet Security 2009 (on Windows XP sp3). How can I fix this?

I rebooted and now things seem to be working ok. Thanks for your help, Diana.

I think I set it up as you suggest, Diana, but it's behaving the same way. Please let me know if you see anything I missed. It doesn't seem to make any difference how I set transparent tunneling.

I noticed that setting the firewall rule for the vpn client to apply only to locally connected computers allows TCP/UDP traffic to flow but the VPN still doesn't work unless the firewall is disabled. This is pretty screwed up.

If I disable the firewall all these problems go away so it's something that is apparently caused by some firewall feature that is still enabled in Game Mode.