Conflict with User Firewall

[dcwalker]

We have 2 users running Sygate (one XP, One W2K) that cannot connect. We have a policy requiring the vpn client in-built firewall to be running but it cannot start and so the user cannot connect.

This seems to be a conflict between the zone labs built-in firewall and Sygate. A search on the internet shows "outpost" firewall having similar issues.

The client log shows this error:

1 21:11:18.234 12/30/04 Sev=Warning/2 IKE/0xE300008A

Stateful Firewall (Always On) failed to start.

This links discusses "outpost" problems.

http://www.wilderssecurity.com/showthread.php?p=341204#post341204

[aftermath]

The first thing I would do is make sure your firewall policies match. Also make sure that the XP user has disbled the built in XP firewall. Although the VPN client is supposed to interact with both firewalls, it does not EXPLICITLY. The users may have to disable their respective FW's for the VPN client to work.

HTH..

[dcwalker]

We have confirmed this is a conflict between the built-in Zone Alarm and the current Sysgate. The only way we have found to resolve the problem is rebuild the PC and do not install thye current version of Sygate.

The user is now running the previous version of Sygate.

[aftermath]

Thanks for following up, and letting me know how this went.

I thought it was either the policies, or the respective firewalls..........