Re: Cisco VPN problem

Chuck, I'd recommend you get a DNS name for your VPN concentrator and
use that instead of a dedicated IP address.  Something like
vpn.chuckscompany.com.  We don't use 'vpn' as part of the DNS name here
but it is something that sounds somewhat like remote access.

Anyway, I don't see it in the registry.  I'll run a scan of my hard
drive to see what turns up.


John A. Jones, CISSP
Americas Information Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787 F: +1-312-601-1782
john.jones@xxxxxxxxxx

-----Original Message-----
From: pctech-bounces@xxxxxxxxxxxx [mailto:pctech-bounces@xxxxxxxxxxxx]
On Behalf Of Chuck Lewis
Sent: Wednesday, November 15, 2006 8:01 AM
To: 'PC Technical Discussion for iSeries Users'
Subject: [PCTECH] Cisco VPN problem

Hi Folks,

 

One of your communications providers switched who they use so some of
our IP addresses changed. It was planned so no big deal or it seemed :-)

 

Part of the change included the IP address for our Cisco PIX VPN. So we
let all remote users know what to change and for 98+ % were fine. On the
others it has been a BEAR. They WILL not connect. The one I did

get to connect I had to COMPLETELY remove the Cisco VPN Client,
Add/Remove AND deleting the subdirectory(s) it created or it remembers
the configuration .

 

Does anyone know if the IP address is cached, etc. somewhere else ?

 

Thanks !

 

Chuck

 

--
This is the PC Technical Discussion for iSeries Users (PcTech) mailing
list To post a message email: PcTech@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/pctech
or email: PcTech-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/pctech.


This email is for the use of the intended recipient(s) only.  If you have 
received this email in error, please notify the sender immediately and then 
delete it.  If you are not the intended recipient, you must not keep, use, 
disclose, copy or distribute this email without the author's prior permission.  
We have taken precautions to minimize the risk of transmitting software 
viruses, but we advise you to carry out your own virus checks on any attachment 
to this message.  We cannot accept liability for any loss or damage caused by 
software viruses.  The information contained in this communication may be 
confidential and may be subject to the attorney-client privilege. If you are 
the intended recipient and you do not wish to receive similar electronic 
messages from us in the future then please respond to the sender to this effect.