New Zealand ADSL Mailing List

From: Bryce Farmilo <bryce_at_esnz.com>
Date: Wed, 7 Jun 2000 09:28:53 +1200
Message-ID: <6B26D61909F6D31198270090274DC66401B0FD@OBI-WAN>

Rob,

You can usually get the SecuRemote client to work with DHCP if you stop it
auto-starting and start it manually from the desktop or from the start menu.
If you hunt in the registry for the run key
(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run) you
should find a reference to fwenc which is the SecuRemote app. Just remove
it from there and create a shortcut to it on your desktop.

Once you've loged into NT start the fwenc app and you should find that the
DHCP works fine and once you've started SecuRemote that should work fine
also.

Cheers,

Bryce.

-----Original Message-----
From: rob.edkins@axon.co.nz [mailto:rob.edkins@axon.co.nz]
Sent: Tuesday, 6 June 2000 9:48 p.m.
To: craig.little@ssi.co.nz; adsl@freebsddiary.cx
Subject: RE: M10s & Checkpoint VPNs

>
> > Well, as of this minute I'm happily connected via the
> > Securemote client
> > through from my home Jetstream connection behind an M10 to a
> > Checkpoint
> > Firewall using IPSec.
>
> What pinholes or other settings have you made on the M10 to
> make it work?
>

You need the Nokia Firmware 5.3.0 R2

You then need to configure (via the telnet interface) a pinhole for IP type
50. Specify "OTHER" for the protocol type, then enter the numeric value 50.

I had some interesting times trying to get the Securemote client to bind to
the ethernet interface on my laptop using a DHCP derived address.

It works on Win98, but not NT. This seems be be related to the order in
which NT binds the NDIS drivers.

In the end, I simply used a static IP address on NT.

Rob

This message is part of the NZ Broadband mailing list.
see http://freebsddiary.cx/adsl/ for archives, FAQ,
and various documents.
To unsubscribe: send mail to majordomo@freebsddiary.cx
with "unsubscribe adsl" in the body of the message