From: jin10101010@xxxxxxxxxxx
Date: Thu Jul 11 2002 - 22:47:05 GMT-3
As I know,
It would be multiple situations.
First, check the ADSL adapter IP address to route properly.Sometimes ISP assign
their private address no the public address.
Second,check what is the operating system on the VPN Client.etc,win98,2000,nt
win95 has a bug. or update the vpn client version to the newest one
Third,Check the if the vpn client make the NAT Through the Network option Selec
ted on the properties tab of OPTION.
Fourth,change or adjust to proper value of Network Adapter's Frame size option.
In some practical situation, Frame size was the very serious problem. But I don
't understand why it does.
And then repost the result to the group.
Thanks.
Good luck.
P.S:
I know VPN Trouble shooting is so hard work.
Please take care of you.
----- Original Message -----
From: "Raymond Jett" <rajett@cisco.com>
To: "Tom Young" <gitsyoung@yahoo.co.jp>; <ccielab@groupstudy.com>
Sent: Thursday, July 11, 2002 11:38 PM
Subject: RE: VPN300's error message
> There's an option for using UDP 10000 for communcations.
>
> Use that for going through NAT
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of Tom
> Young
> Sent: Thursday, July 11, 2002 1:24 AM
> To: ccielab@groupstudy.com
> Subject: VPN300's error message
>
>
> Hi, group
>
> I am using VPN3015 for doing a VPN now. If the
> remote client use the leased line, it will be working. But
> if the remote client using a NAT translation(ISDN or
> ADSL), it is will no woking, even remote client got a
> fixed IP address for 1-1 NAT translation.
> The error message in the VPN3015 is "XAUTH required but
> selected protocol doesn't support XAUTH". Who has the
> experience for this problem? Could you tell me how to do
> that ?
>
> Thanks
>
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:36:27 GMT-3