Is Centralized Protection Policy CPP incompatible with Macintosh users?

[waynehenderson]

It seems that CPP leaves OS X users SOL.

I'm using VPN client 4.7.00(0510) in Mac OS X Panther 10.3.9. Our server apparently is configured to push CPP to the clients, which are set to "Stateful Firewall (Always On)". (This is on my Dell laptop running client 4.6.03.0021)

As I understand it, the Mac client has no such built-in firewall (doesn't need it) and therefore can't respond to the server that a firewall is present. CPP then drops the connection.

Is there anything I can tell the IT guys to try, other than disabling CPP, so that the VPN does not require this of a Mac client, thereby letting Mac clients connect properly? Or am I just hosed?

[waynehenderson]

Was this so dirty a question that no one can answer?

I'm just looking for:

1) Confirmation that CPP disables Mac clients from connecting and

2) Whether there is a solution at the server that could allow CPP to continue functioning for the Windows crowd but still allow Mac users to connect.

Please help if you can. Thanks.

[vabruno]

wow cant believe no one has answered this. I have the exact same question as im running version 4.8x on a MAC 10x with no luck pushing down firewall policy.

[waynehenderson]

I eventually gave up - and believe there is no solution.

Fortunately for me another Mac user in the company tipped me off to a server that doesn't require this nonsense, so I just use that and all is well.

Haven't been able to use the Tiger built-in VPN, although it looks "close".