Can't get VPN to work in v3 [Merged Threads]

[Guest]

[delta7]

I also have the same issue with VPN not working. I tried the suggestions but none of them worked. I tried installations with and without Defense+ but still had the problem. I also managed to crash Commodo twice (once when I was adding the address of the VPN server) and once when I clicked on one of the help links .. 'what do these settings do' or some similar text.

I've gone back to v2.4 which works fine since I need VPN access to work remotely.

I'll look at upgrading when the problem is resolved in a later version.

[bandsaw]

Making the system idle process trusted worked for me, but I don't like it!!

Where are the Network Monitor logs?  All I see is the application logs and those have not told me anything.

I'm really thinking about going back to Vr 2.4 until the bugs are worked out.

[m-s]

VPN connection gives error:

Disconnected.
Error 619: A connection to the remote computer could not be established, so the port used for this connection was closed.

If disable firewall then connection will be established.

Help

COMODO Firewall Pro 3.0.13.268
Vista x64

Sorry for my bad english.

[Saxo]

A thread already concerning this issue runs here

http://forums.comodo.com/help_for_v3/cant_connect_with_xps_vpn_client_help-t15241.0.html

You could try the suggestions in this one thought it dosn't seem to work for everyone, me inculded sadly

[LaGross]

I also had this problem. Tried a lot of things to make it work but none of it worked. Maybe a problem was that English is not my mother tongue, which made it quite harder to set right configurations also by using a dictionary...

But using VPN is essential for my study where I'll need to connect to the server of our studying project.

Therefore I have reinstalled version 2.4 - there it works fine.

I will wait until the bug is fixed...

[jlitzie]

Hi,

I am also having a VPN issue, but not with the XP version. I use Nortel Contivity which worked fine with 2.4. I've attached a log file from Nortel, but there's not much in it.

The error I receive when trying to connect is:
 - Login Failure due to: Driver failure.

There are no popup alerts.
There are no Firewall or Defense+ log records.
Network zones shows:
 - Nortel IPSECSHM Adapter - Packet Scheduler Miniport
 - The zone is an ip address mask and the ip address in the zone begins with 172
   - This is not my pc, router, or VPN server's ip address. I'm assuming it's an assigned ip for VPN use?
Firewall Network Security rule for Extranet.exe is:
 - Allow IP Out from IP Any to IP Any Protocol is Any
Defense+ for the same file is:
 - Access Rights - All entries are either Ask or Allow
 - Protection Rights - All entries are No
Network Defense is set to Train with Safe Mode
Proactive Defense is set to Clean PC Mode
Firewall Alert settings are medium

Hope this helps.

[m3nth]

First of all, v3 looks *great*... very much improved.

Trying to get VPN working...

Platform is XP SP2, trying to use the default Windows Connection setup to VPN (PPTP). 

Disabling the firewall works fine but the VPN won't connect with any of the other settings, including training mode.  I've also tried to add the PPTP port to no avail, as well as adding in the network that was found when the VPN connected while the firewall was disabled. 

Any help is appreciated... thanks.

[Finster]

Here is my post from yesterday
Operating system Windows XP Pro SP2 x86
As I installed Comodo Firewall Pro 3.0.13.268 I can't open a tunnel to a VPN server. As the log shows a PPTP connection can be established (process- System, TCP out remote port 1723), but the GRE protocol is being blocked without any reason (for the process "System Idle Process") in both directions.
First I thought it should work as the 2.4 version of Comodo Firewall and have created a global rule for GRE protocol (allow, in/out, IP type GRE, source- my local IP, destination- IP of the VPN server)
Then: I selected the "System Idle Process" as an application in "running processes" and created the same rule for it.
Then: allowed GRE for any source/destination in global rules and for "System Idle Process".
Then: allowed everything for "System Idle Process".
Then: allowed EVERYTHING in global rules. In this case I saw as the firewall allowed even the netbios broadcasts (UDP in destination/source ports 137-138), which are being also logged as an activity of the "System Idle Process", but the GRE protocol is being blocked.
What else can I do to allow GRE?!
I have of course no answer til now and I don't think we get any, the thing simply DON'T WORK, that's all

[Finster]

I've just found some relevant information in russian forums. Many people have the same problem, one of them found such "solution":
-Disable firewall (I don't know, what he was meaning- unload the firewall monitor and/or its service or just disable it anywhere in settings)
-Connect to VPN
-Enable firewall
-Now you can disconnect and connect the VPN anytime until you restart
Of course, it's just a bug of comodo, nothing else

[miha]

Hi!

You can try something like this (I noticed you tried something similar, but this way it works, at least  for me): http://forums.comodo.com/help_for_v3/enable_the_connection_help-t15591.0.html;msg107926#msg107926

It is how I got VPN, both IPSEC and PPTP working. I should mention that in global rules I have only incoming ICMP ping request block, as I also use machine as development server.

But I agree, this is making things unnecessary complicated and comodo should come with default rules that support this. I even had to alter System Idle Process rules to get tracert working, that's silly.

[Saxo]

I'm seeing more and more support forums where ppl post problems with Comodo and VPN suggest either swichback to previous versions or even choose another firewall, as many of the suggestions already posted could compromise security.

I still need to hear from Comodo themselves what's the solution concerning this issue?! Several threads here on this board is already running with this problem.

[rkneeshaw]

I'm trying to connect to my corporate networks remote access server using Windows XP's built-in VPN client and it cannot complete authentication when the comodo firewall is enabled.  When I disable the comodo personal firewall, authentication completes and it completes the connection.

[yirgster]

I also cannot get vpn to work using the win-xp network connection.

Worked perfectly in 2.4.

[zombie]

problemz come with final ver. in the rc1 VPN works.

[khe2007]

I didn't like the idea of making the system idle process a trusted process.
So I made a work-around.
1. open comodo firewall pro settings - Firewall- Advanced
2.Go to predefined firewall policies, and add a new policy, give it a name (fex Gre)
3. use a custom policy and configure it like this:
 - action: allow, protocol: ip, direction:in/out
 - source ip: use any or use your own ip address or hostname
 - destination ip: use the ip-address of your vpn-server at work
 - ip-details: choose protocol GRE
4. Save the predefined policy
5. Go to Network Security Policy, and add a new security policy
6. Under application path, choose Running Processes, and choose System Idle Process
7. Choose Use a predefined policy, and choose the predefined policy you just created above (Gre)
8. Save and test
Works ok for me - and you still have a pretty tight security

[Tags:]