Sorry, I had the same problem here and I forgot to mention that step.
da
----------
From: Mark A. Knight <RadAdmin@Express-Connect.Net>
To: 'RadiusNT@emerald.iea.com'
Subject: RE: Long Authentification Delay Time
Date: Thursday, June 12, 1997 2:58 PM
I wish the answer was that simple! I do not have the "Log into Network"
checked on the WIN95 machine I am using to dial in from. Any other
suggestions?
-----Original Message-----
From: Dale E. Reed Jr. [SMTP:daler@iea.com]
Sent: Thursday, June 12, 1997 9:43 AM
To: RadiusNT@emerald.iea.com
Cc: NTISP Mail-List (E-mail)
Subject: Re: Long Authentification Delay Time
Mark A. Knight wrote:
>
> Okay, I upgraded my MAX to 5.0Ap10. That was the latest patch I could
> find. I still have long delays in logging in. I am pretty sure the
> additional delay (normally 30 seconds) comes AFTER the MAX has sent
> the request to my RadiusNT server and RadiusNT has done its deal. The
> reason I say this is because I dial in from one box, switch over to my
> RadiusNT server, see the authentication and accounting packets, start
> my stopwatch, and the other system finally connects 30 seconds later.
>
> There must be an attribute I have set incorrectly in the MAX as best I
> can figure.
This has nothing to do with RadiusNT. You have the client configured
to "Log into Network" and its trying to contact a DC for an NT Network".
Uncheck that silly Win95 option and your problem will go away.
-- Dale E. Reed Jr. (daler@iea.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.emerald.iea.com---------------------------------------------------------- RadiusNT Mailing List listserver@emerald.iea.com
----------