I guess it's a problem a lot of administrators had. In my case, we use
Xircom Ethernet 10/100, GSM and Modem cards. The drivers give the
possibility to release IP lease on the machine's shutdown.

But as I know, there is a key in the Windows registry called
"ReleaseLeaseOnShutDown" which can do it as well. Unfortunately, I did not
remember the whole process about it. Perhaps someone here can tell us more.

--
Societe V. MANE FILS
Yannick Lo Guidice
Poste 1366
Technicien reseau
[EMAIL PROTECTED]
+33 493 097 000
--


-----Original Message-----
From: Ponte, Paul [mailto:[EMAIL PROTECTED]]
Sent: lundi 16 octobre 2000 17:20
To: Fw-1-Mailinglist (E-mail)
Subject: RE: [FW1] SecuRemote/laptops and DHCP



We had the same sets of problems here.  We got past them by using AUTOEXECNT
from the NT resource kit and good old autoexec.bat to do a ipconfig /release
and then ipconfig /renew on every boot.  Then, we trained the users to
always "shut down and restart" when connecting/disconnecting from the
network.  This works great for all users who do dial-up, but users who do
SecuRemote over a DSL or cablemodem connection need to also "kill" the
SecuRemote executable in the system tray.

We don't have any statically assigned IP's, but in your case I would make
those PC's DHCP clients and then put an address reservation into your DHCP
server so they always get the same IP.

Good luck!



Paul F. Ponte
Network Systems Administrator
International Fund for Animal Welfare



-----Original Message-----
From: Rodney Lacroix [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 16, 2000 8:45 AM
To: [EMAIL PROTECTED]
Subject: [FW1] SecuRemote/laptops and DHCP



I have a scenario where SecuRemote does not work very well.  I was hoping
someone had the same issue, and can give me the work-around or solution.

We have users who work in the office and remotely with their laptops.  The
have PCMCIA Nic's that either have a bound IP or a DHCP assigned IP.  After
installing SecuRemote, I can only get the VPN authentication by releasing
the IP address of DHCP clients - this can be a real hassle for people who
are technically challenged (read: all users).  However, statically assigned
clients are a different story - I need to disable or remove the card
altogether to get it to work.

How do I get around this issue?

**************************************************************************
CONFIDENTIALITY:
This e-mail and any files transmitted with it are confidential and intended solely for 
the use of the individual or entity to whom they are addressed. If you are not the 
intended recipient or the person responsible for delivering the e-mail to the intended 
recipient, you are advised that you have received this e-mail in error and that any 
use, dissemination, forwarding, printing or copying of this e-mail is strictly 
prohibited. If you have received this e-mail in error please notify: 
[EMAIL PROTECTED]
**************************************************************************


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

Reply via email to