1) MS sends authentication info too early.
2) The PM either chucks that data, (speculating), or doesn't read data
until after it's sent the login prompt. Thus tossing what MS sent.
That's probably trivial to test.
Even when I bring up a terminal window after dialling, it will sometimes
be a second or so before I get the PM prompt.
Wonder if prompt length has anythign to do with it.
On Thu, 12 Dec 1996, Ronnie D. Franklin wrote:
> Date: Thu, 12 Dec 1996 10:21:11 -0600
> From: "Ronnie D. Franklin" <ronnie@itexas.net>
> To: MegaZone <megazone@livingston.com>, portmaster-users@livingston.com
> Subject: Re: [Fwd: Re: Unable to negotiate a compatible protocol] (fwd)
>
> Thanks for your input, but it is not on my network... we have checked all
> that out and the authentication time is not a problem.. I have almost 0
> duplicate auth requests. Even the acct-delay-time says it is 0. I also
> have a network protocol analyzer and the network is only running at about
> 5% when we have a full load.. One other point.... I have not had one
> problem from the remote POP's which come into here.. go through the same
> router and get on the same ethernet and go to the same radius server.... so
> I really can't see where anyone could even think that the network or radius
> had anything to do with it...
>
> Ronnie
>
> ----------
> > From: Fletcher E Kittredge <fkittred@gwi.net>
> > To: Ronnie D. Franklin <ronnie@itexas.net>
> > Cc: MegaZone <megazone@livingston.com>; portmaster-users@livingston.com
> > Subject: Re: [Fwd: Re: Unable to negotiate a compatible protocol] (fwd)
> > Date: Thursday, December 12, 1996 7:45 AM
> >
> > On Wed, 11 Dec 1996 21:39:32 -0600 Ronnie D. Franklin wrote:
> > > I do not have the problem when the load is in the 25-30 range.. works
> just
> > > great.. and I'm not positive that it is Portmaster problem, but it is
> > > related and I am just looking for an answer or a way to see where the
> > > problem is...
> >
> > I think it is a load problem, but the load is on your network and
> > radius server. I suggest you try correlating the radius reports of
> > duplicate auth requests (which happen when load is too high) with the
> > failure reports.
> >
> > Properly provisioning your network and radius servers will fix this
> > problem.
> >
> > regards,
> > fletcher
>