Re: Raduis
Dale E. Reed Jr. (daler@iea.com)
Sat, 28 Sep 1996 11:50:37 -0700
Dan Struthers wrote:
>
> >> I think you are referring to sysname, I changed that to portmaster.lgnd.com
> >> and reset secret to another word.... restarted everything and still no go.
> >> Now, one additional point, when attempting to authenticate, it takes a very
> >> long time to return the 'get a life' message invalid login I mean. In the
> >> order of 20 -30 seconds. Is there some way to trace what the authentication
> >> mechanism is doing at a packet level?
> >
> >You said DNS was fine, but what about IN-ARPA? Radius users IN-ARPA,
> >and so
> >would syslog. That is why your IP address is in your syslog and Radius
> >is taking so long.
> >
> >Do a "dig -x 206.47.47.29" and see what it returns.
>
> Thanks for your reply;
>
> I did a dig on bserv.com and got nothing, then I did a dig on lgnd.com (the
> name server for the second C) and got back data. How can I specify to radius
> to ask lgnd.com for the IN-ARPA info? Can I add something to the name server
> on the first C?
You can't. This is a configuration issue on the machine running
Radius. I
highly recommend to those people running RadiusNT to put ALL host
information
in the lost hosts file for Radius so that DNS is not an issue. This is
simply
because most people using NT in this situation are not as knowledgeable
about
the workings of the DNS, like unix oriented users are. You could do the
same
thing for a unix box running radius as well to fix the issue right now
until the
primary DNS issue is taken care of.
--
Dale E. Reed Jr. (daler@iea.com)
_____________________________________________________________________
Internet Engineering Associates | RadiusNT, Emerald, and NT FAQs
Internet Solutions for Today | http://www.iea.com/~daler