Help - Search - Members - Calendar
Full Version: Bitdefender 2008, Cisco Vpn, And Rdp
BitDefender Forum > English > Old Forum Topics > Products > Workstation
tbennett300
Hi there

I'm using Bit Defender 2008 with Cisco VPN client 5.0.01.0530. I iniitially had some problems connecting to a VPN at all, but I managed to sort those out. My problem now is that when I have successfully VPN'd in, i cant use Remote Desktop to connect to anything. i saw the article for which I've supplied the link beloew, but it doesn't state how the RDP issue was resolved:

http://forum.bitdefender.com/index.php?sho...amp;#entry26282

At the moment, when I VPN, I have to disable BitDefender firewall and enable Windows Firewall. I've also tried manually adding an 'any/any' rule for the network I'm connecting to, but that doesn't work either.

Surely there's a way round this? I'm sure I'm not the only one ever to have experienced this?

Any help would be appreciated.
Lionel B Dyck
I am trialing BitDefender Internet Security 2009 and it works fine except when I try the Cisco VPN Client (I have the latest running on Windows Vista Home Premium SP1.

When the Cisco VPN client connects all packets are either discarded or bypassed.

If I turn off the Firewall then it works fine.

Any help would be appreciated
reddkap
Here's what worked for me:

I'm using BD Internet Security 2009 on a Vista machine, so I'm not positive that this will apply to BD 2008, but here it is. I had to change one property in the network connection that is created when I open my VPN client (e.g. Local Area Connection 2). Open your Network Connections (Control Panel > Network and Sharing Center > Manage network connections), right click on the connection and select Properties, uncheck the box next to 'BitDefender Firewall NDIS Filter Driver' and click Okay. That's it!

I also tested this with and without multiple other setting that I have seen suggested in various forums. For me, it does not matter whether I create rules (though one is created automatically, when my VPN client connects), it doesn't matter if I to use the 'Generic' setting for my connections, etc. Obviously, you'll need the trust level for your connection to be at least 'Safe', but I don't believe that any other settings should make much of a difference.

Good luck, I hope this works for others as well.
Hunter47
QUOTE (reddkap @ Nov 7 2008, 09:26 PM) *
Here's what worked for me:

I'm using BD Internet Security 2009 on a Vista machine, so I'm not positive that this will apply to BD 2008, but here it is. I had to change one property in the network connection that is created when I open my VPN client (e.g. Local Area Connection 2). Open your Network Connections (Control Panel > Network and Sharing Center > Manage network connections), right click on the connection and select Properties, uncheck the box next to 'BitDefender Firewall NDIS Filter Driver' and click Okay. That's it!

I also tested this with and without multiple other setting that I have seen suggested in various forums. For me, it does not matter whether I create rules (though one is created automatically, when my VPN client connects), it doesn't matter if I to use the 'Generic' setting for my connections, etc. Obviously, you'll need the trust level for your connection to be at least 'Safe', but I don't believe that any other settings should make much of a difference.

Good luck, I hope this works for others as well.

Hunter47
I believe the option you have chosen effectively disables the BitDefender Firewall. If you just select disable The BD FW permenantly and enable the Windows Firewall your VPN should work. At least it does with two different versions of the of the NetScreen/Netgear/Juniper VPNs I use. You still need to add the appropriate exceptions to the Windows fire wall, actually the same ones that didn't work with the Bitdefender firewall.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2009 Invision Power Services, Inc.