[pptp-server] Windows 98 / Windows 2000 Problem.

[Gill, Vern]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

No, the require statements are not the "breakers". It is something
else. The options file he has is identical, excepting ip addresses
and system names, to the one I have been using for over a year now.
By the way, looks like you also used my combined patch. Cool! Anyway,
the options file, which is nearly identical to mine, has worked for
9x/Me/NT/2k for a long time now. Something else is causing the
problem.

PGP Signed! Why?

"If all the personal computers in the world -
~260 million computers - were put to work on a
single PGP-encrypted message, it would still
take an estimated 12 million times the age of
the universe, on average, to break a single message."

- - William Crowell,
Deputy Director of the
National Security Agency, in testimony to the
U.S. Congress, March 20, 1997

- -----Original Message-----
From: robert [mailto:berzerke at swbell.net]
Sent: Thursday, May 10, 2001 7:38 PM
To: Kirk
Cc: pptp-server at lists.schulte.org
Subject: Re: [pptp-server] Windows 98 / Windows 2000 Problem.


?=
<Pine.LNX.4.33.0105100746310.4710-100000 at death.prince-of-darkness.cc>
MIME-Version: 1.0
Message-Id: <01051021381300.18517 at linux>
Content-Transfer-Encoding: 8bit

On Thursday 10 May 2001 09:47, Kirk wrote:
> Ill give it a shot, I put it on the server already, but alas I dont
> run windoze at home :-)
>
> Does it have something to do with the order in which I
> wrote the config??

No.  Certain config lines "break" things.  I think the require lines
you have 
are the breakers.  However, once you have a working example, then you
can add 
back one line at a time until it breaks.  Then post so others can
learn what 
lines to avoid.

>
> Kirk
>
> >On Wed, 9 May 2001, robert wrote:
> >
> >
> > Try this config.  Do not add anything to it or change it (except
> > for the name line and maybe adding a debug line)!
> >
> > name *
> > lock
> > mtu 1490
> > mru 1490
> > proxyarp
> > auth
> > +chap
> > +chapms
> > +chapms-v2
> > ipcp-accept-local
> > ipcp-accept-remote
> > lcp-echo-failure 3
> > lcp-echo-interval 5
> > deflate 0
> > mppe-128
> > mppe-40
> > mppe-stateless
> >
> > On Wednesday 09 May 2001 16:37, Kirk wrote:
> > > Hello,
> > >
> > > Im new to the list. I have been going thru the archives
> > > searching for a solution. The problem I've been having is with
> > > windows 2000 and 98 working at the same time.  I found great
> > > examples in the archive and read _many_ posts.  The root of the
> > > problem is that if I have it setup to work with 2000 (ie
> > > commenting out the mppe-40 in the options.pptp file) windows
> > > 2000 works fine and so does the beta 2 of windows XP, but then
> > > the windows 95/98/ME clients cannot pass data (yes they are
> > > using 128bit encryption). If I put back the mppe-40 windows
> > > 98/me work but then 2000/xp doesnt work. They all connect fine
> > > all the time, just no icmp & tcp traffic for who ever is the
> > > odd one out at the time.  Im kind of in a catch 22 here.
> > >
> > > I can send my other configs if they are needed, didnt want to
> > > make my first post that long.
> > >
> > > Thanks in advance.
> > > Kirk
> > >
> > > System, RedHat 7.1
> > > kernel 2.4.3
> > > linux-2.4.0-openssl-0.9.6-mppe.patch
> > > ppp-2.4.0
> > > smbpw-mppe-stripdom-requiremppe.diff
> > > pptpd-1.1.2
> > > iptables for routing/firewalling
> > >
> > > ####options.pptp
> > > debug
> > > #kdebug 9
> > > lock
> > > #proxyarp  <-- tired this both commented out and not, made no
> > > difference name pptpd
> > > auth
> > > +chap
> > > +chapms
> > > +chapms-v2
> > > chapms-strip-domain
> > > #mppe-40
> > > mppe-128
> > > mppe-stateless
> > > require-chap
> > > require-mppe
> > > require-mppe-stateless
> > > ms-wins 10.10.10.41
> > > idle 1800
> > > mtu 1490
> > > mru 1490
> > > ipcp-accept-local
> > > ipcp-accept-remote
> > > lcp-echo-failure 30
> > > lcp-echo-interval 5
> > > deflate 0

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com>

iQA/AwUBOvvpWheamMdwy9TXEQJtawCg339mcEkD/0VEYzQzw7PEfSHItJ4AoKcL
OOWaBRXB6MBkQXj2F5XQX8at
=Ovb5
-----END PGP SIGNATURE-----