Could both of these problems be related to the OS not releasing the DHCP
assigned IP address when it shuts down, thus when the machine is booted again
and dialled up, the NIC still has an IP address in the encryption domain and SR
thinks it is still connected to the network and does not try to communicate via
the modem link?

The old 'ReleaseLeaseOnShutdown' registry hack for MS :-)

Mike




Joe Voisin <[EMAIL PROTECTED]> on 27/07/2000 15:36:41

To:   "'LEMPEREUR Vincent'" <[EMAIL PROTECTED]>,
      [EMAIL PROTECTED]
cc:    (bcc: Mike Anning/WEY/EU/CHEP)
Subject:  RE: [FW1] secure remote client




We also have this problem from time to time.  I instruct the users to ping
the firewall if they are not prompted for authentication when they try to
access resources.

With laptops, I have also come across a problem with users having a NIC in
their laptop that is on the same subnet/network as they are trying to
contact and it actually tries to talk to the network via the dead ethernet
line instead of the dialup line.  What one of the IS people does in my
department is take out the NIC when booting.  Windows 2000 does not seem to
suffer from this as it disables Ethernet when it's disconnected.

I don't know if this helps you out at all.  Hopefully it does. :)

======================================================================
Joseph Voisin, Systems Administrator, Engel Canada Inc.
www.engelmachinery.com | [EMAIL PROTECTED] | (519)836-0220 x436
======================================================================


-----Original Message-----
From: LEMPEREUR Vincent [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 27, 2000 10:00 AM
To: [EMAIL PROTECTED]
Subject: [FW1] secure remote client



Dear all,

We have secure remote client installed on some laptops
to allow users go through our firewall with vpn when they
dial up to our network.
But very strange sometimes the users don't receive the firewall
pop-up windows that ask them to enter their user name
and password and even if we force it, the firewall does not answer
or sometimes it does not answer but let them go after 5 minutes
And very strange enev if the user go through the firewall he can't connect
to
any network ressoures
Of course these users are well defined on the firewall

can anybody help me ?


Title: secure remote client
We also have this problem from time to time.  I instruct the users to ping the firewall if they are not prompted for authentication when they try to access resources.
 
With laptops, I have also come across a problem with users having a NIC in their laptop that is on the same subnet/network as they are trying to contact and it actually tries to talk to the network via the dead ethernet line instead of the dialup line.  What one of the IS people does in my department is take out the NIC when booting.  Windows 2000 does not seem to suffer from this as it disables Ethernet when it's disconnected.
 
I don't know if this helps you out at all.  Hopefully it does. :)
 

======================================================================
Joseph Voisin, Systems Administrator, Engel Canada Inc.
www.engelmachinery.com | [EMAIL PROTECTED] | (519)836-0220 x436
======================================================================


-----Original Message-----
From: LEMPEREUR Vincent [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 27, 2000 10:00 AM
To: [EMAIL PROTECTED]
Subject: [FW1] secure remote client

Dear all,

We have secure remote client installed on some laptops
to allow users go through our firewall with vpn when they
dial up to our network.
But very strange sometimes the users don't receive the firewall
pop-up windows that ask them to enter their user name
and password and even if we force it, the firewall does not answer
or sometimes it does not answer but let them go after 5 minutes
And very strange enev if the user go through the firewall he can't connect to
any network ressoures
Of course these users are well defined on the firewall

can anybody help me ?

Reply via email to