Thanks for the response,
but the problem is that they definitely are getting a different IP address on the second dial up session.
I have verified this myself using ipconfig on the laptop and by looking at the FW log
WM
| "Dameon D. Welch-Abernathy" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 18/05/2000 01:31 AM
|
To: [EMAIL PROTECTED] cc: [EMAIL PROTECTED] Subject: Re: [FW1] SecuRemote timeout |
On Wed, May 17, 2000 at 07:02:58PM +1000, [EMAIL PROTECTED] wrote:
> After the establishment of a successful SecuRemote session ( requiring
> the use of SecureID as authentication), a laptop user closes their Dialup
> ISP session.
> A few minutes later, the user re-dials the ISP, ( gains a different IP
> address), and the SecuRemote VPN session is re-established, without a
> SecureID authentication request.
If the user dials up and gets a different IP address, they will be forced
to re-authenticate by default. It sounds like your user is getting the
same IP address when he dials up. In this case, the answer is no.
--
Dameon D. Welch-Abernathy a.k.a. PhoneBoy
[EMAIL PROTECTED] http://www.phoneboy.com
The views expressed herein are not necessarily those of anyone else.
================================================================================
To unsubscribe from this mailing list, please see the instructions at
http://www.checkpoint.com/services/mailing.html
================================================================================
