v3.0 Cisco IPSec client on W2K

[Longar, Dennis]

Well, give this a try.

Have a 2K DOS prompt open at with the connect start tool.
When you tell the 2K machine to connect to the VPN, in the
DOS window ping the address of the 3030's public side.

The strangest part of this is, I got one machine (my home machine)
that will only connect if I ping during the connect, and my 2k test
machine at my work, works fine without pinging the remote.

So I've always just assumed it was my home computer setup, but if
this works for you then it is a cisco bug.

Let us all know if it works please!

Thanks!

-Dennis

> -----Original Message-----
> From: Alastair Morrison [mailto:alastair.morrison at strath.ac.uk]
> Sent: Friday, April 20, 2001 4:25 AM
> To: VPN at SECURITYFOCUS.COM
> Subject: v3.0 Cisco IPSec client on W2K
>
>
> I have a Cisco 3030 concentrator running v3.0 code configured
> with a group (internally configured) enabled for IPSec.
>
> I have an NT4.0 machine running the v2.5 Cisco IPSec client.
> A W2K machine running the v3.0 Cisco IPSec client.
>
> The NT machine establishes a connection.
>
> The W2K machine fails with message
> - Remote peer is no longer responding.
> The corresponding Event log message(s) on the concentrator being
> - Duplicate first packet detected.
>
> Both clients are configured the same (such as they can be).
> I have tried changing various of the IPSec settings on the
> concentrator
> to no avail.
>
> I would appreciate any views on how to get the v3.0 client on
> W2K working.
> Please reply to my personal address as well as the list as I
> receive the list
> digest and the sooner I get some guidance on this particular
> issue the better!
>
> Thanks,
> Alastair Morrison
> Strathclyde University
>
> ---------------------------------------------
> alastair.morrison at strath.ac.uk
> Strathclyde University
> Glasgow      UK
>
> VPN is sponsored by SecurityFocus.COM
>

VPN is sponsored by SecurityFocus.COM