If you watch your logs, you can usually see what the particular client is
trying to do and the firewall is rejecting. I took off most of the default
rules as I prefer to control those things myself. The reason your rules
from 4.0 might not work in 4.1 is that I believe the FW1 port that
SecureRemote uses changed from 256 to 264 and your rule in 4.0 might have
reflected the old port. From past experience, I think SecureRemote will
try the new port and if it fails then try the old one or possibly vice versa.
.. Jason Badry
At 11:29 AM 1/10/01 -0500, you wrote:
>>Hi all
>>
>>I am using FW1 4.1 SP2 and SecuRemote client build 4165. I can create and
>>update sites without a problem but when I try and authenticate I get the
>>error message:
>>
>>No answer received from Firewall at x.x.x.x
>>
>>Has anyone come across this problem before and any ideas anyone?
>
>I sure have. It went away when I added "Allow Firewall-1 Connections" in
>my policy. No matter what I put in my own written rule for SecuRemote,
>Version 4.1 would not recognize the VPN connection as a SecuRemote
>session. My rule did work for me in Version 4.0, however.
>
>Hope this helps....
>
>
>-- Joe
================================================================================
To unsubscribe from this mailing list, please see the instructions at
http://www.checkpoint.com/services/mailing.html
================================================================================
