Re: [RadiusNT] SNMP concurrency-checking inconsistencies
Dale E. Reed Jr. ( (no email) )
Thu, 30 Sep 1999 10:09:21 -0700
Josh Hillman wrote:
> > Josh Hillman wrote:
> > > I tried duplicating the problem about 30 times since you wrote back and
> > > only three times that I could get the problem to come up was when
> > > was running as a service. When it's running from the command prompt as
> > > "radius -x18" it authenticated successfully every time.
> From: Dale E. Reed Jr. <firstname.lastname@example.org>
> > Define the auth and acct log files, make sure you debug registry value
> > is 18, and restart the services. The tail2.exe program on our ftp
> > site can be used to watch the debug.
> I set up the log files as
> and set the Debug value to 18 in the registry, then restarted Radius (as a
> radrecv: Request from host c72cc20e code=1, id=226, length=105
> Sending Reject of id 226 to c72cc20e (Max 5)
> User: test already logged onto system 1 time(s).
> RadiusNT: err(13): Couldn't open /logfile for logging
> Resp Time: 16 Auth: 10/1 -> 11 Acct: 0/0/0 -> 0
> Nothing showed up in the acctlog.txt file.
Double check that Max 5 has a community defined, and that all ports
are defined for it. Unfortunately, witout a high debug mode, we
don't know what port they were on to see if that port exists and has
the SNMPUser set correctly. Since it doesn't even show an SNMP
check, either the Community or SNMPUser value is missing.
Dale E. Reed Jr. Emerald and RadiusNT__________________________________________IEA Software, Inc. www.iea-software.com
For more information about this list (including removal) go to:http://www.iea-software.com/support/maillists/liststart