I am experiencing this same problem using Outlook 2000 on Windows 98.

Checkpoint Firewall-1/VPN-1 V4.1 SP1
SecuRemote Build 4153

I have downloaded the latest version of SecuRemote (Build 4157),
hopefully that will fix the issues I am experiencing:

1) Packets do not start encrypting right away, I have to force it by
pinging / telnetting to an Internal IP and then the encryption starts -
PERIODICALLY

2) Sometimes an encrypted session will not completely encrypt. I am
seeing drops in my logs when I fire up Outlook, the typical Port
1039/1035 and Port 135 traffic goes through, and then a single packet
coming from my laptop will not make it through for some reason (shows as
an ICMP drop hitting my ghost rule), and everyone's Outlook crashes. -
PERIODICALLY

Neither of these symptoms happen all the time, which leads me to believe
that there may be something else going on.

I'll try the new SecuRemote Build and let everyone know how I made out.

Chuck.


-----Original Message-----
From: Gabriele Reggiani [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 03, 2000 6:54 AM
To: [EMAIL PROTECTED]
Subject: [FW1] Securemote and Windows98






Anyone knows if Securemote 4.1 has some problem on Windows 98 platforms?
The client gets correctly the data from the server, and I can create the
site
object, but when I try to connet the client to the server ftp (the
server beyond
the firewall) the securemote doesn't start encrypting although the site
is
included in the encryption-domain.
Thanks
Gabriele




========================================================================
========
     To unsubscribe from this mailing list, please see the instructions
at
               http://www.checkpoint.com/services/mailing.html
========================================================================
========


================================================================================
     To unsubscribe from this mailing list, please see the instructions at
               http://www.checkpoint.com/services/mailing.html
================================================================================

Reply via email to