=======================================
*Initializing with logfiles and Registry set to debug level 31...
ServerPorts Column 12 (16): 'CallDate'
13 ServerPorts Columns Loaded
Apr 18 14:44:01 2000 [ERR]: SNMP Initialization Failure. Make sure mib.txt
is in your Data Directory. SNMP Stats & Concurrancy have been disabled.
Professional features enabled.
Apr 18 14:44:01 2000 [NOTICE]:
RadiusNT Professional Initialized...
radrecv: Request from host d12a4f23 (tcm-glenelder) code=1, id=97,
length=181
User-Name = "ejluckey"
Challenge-Response =
"\004\247\303>\035\264\215\203f\312\306Z\345\324\205.\005"
NAS-Identifier = 209.42.79.35
NAS-Port = 12
Acct-Session-Id = "720978"
Interface_Index = 1268
Received unknown attribute 39049, vendor 429
User-Service = Framed-User
Framed-Protocol = PPP
Chasis-Call-Slot = 1
Chasis-Call-Span = 1
Chasis-Call-Channel = 12
Connect-Speed = 1
Caller-Id = "3#**1*"
NAS-Port-DNIS = ""
NAS-Port-Type = Async
Checking for duplicate logins.
Apr 18 14:49:01 2000 [INFO]: SQL Statement: {CALL
RadCheckOnline('ejluckey')}
Apr 18 14:49:01 2000 [INFO]: ejluckey found on-line 1 time(s).
Sending Reject of id 97 to d12a4f23 (tcm-glenelder)Apr 18 14:49:01 2000
[NOTICE]: User: ejluckey already logged onto system 1 time(s).
Resp Time: 16 Auth: 15/2 -> 17 Acct: 47/0/0 -> 47
================
No Mib.txt in the data directory. When I installed this with RadiusNT 3.0 it
created the c:\radius subdirectory and the default Emerald setup didn't have
the SNMP mib file to look at. When I ran radius -x15 from the command line
from c:\radius, it found the Mib.txt file!
Buuuuuttttttttt...
Now all logins connect even after an SNMP Check saying that it found the
users listed online on the corresponding port:
======================================
*Initializing with logfiles and Registry set to debug level 31...
ServerPorts Column 12 (16): 'CallDate'
13 ServerPorts Columns Loaded
Professional features enabled.
Apr 18 15:02:46 2000 [NOTICE]:
RadiusNT Professional Initialized...
radrecv: Request from host d12a4f23 (tcm-glenelder) code=1, id=111,
length=183
User-Name = "ejluckey"
Challenge-Response = "\004\250\315tJ\335\011\327.\203\307\266\205KxC/"
NAS-Identifier = 209.42.79.35
NAS-Port = 275
Acct-Session-Id = "17956926"
Interface_Index = 1531
Received unknown attribute 39049, vendor 429
User-Service = Framed-User
Framed-Protocol = PPP
Chasis-Call-Slot = 2
Chasis-Call-Span = 1
Chasis-Call-Channel = 19
Connect-Speed = 1
Caller-Id = "3#**1*"
NAS-Port-DNIS = ""
NAS-Port-Type = Async
Apr 18 15:06:03 2000 [INFO]: SQL Statement: {CALL RadGetConfigs(117)}
Checking for duplicate logins.
Apr 18 15:06:03 2000 [INFO]: SQL Statement: {CALL
RadCheckOnline('ejluckey')}
Apr 18 15:06:03 2000 [INFO]: ejluckey found on-line 1 time(s).
Apr 18 15:06:03 2000 [INFO]: SQL Statement: {CALL
RadCheckOnlineSNMP('ejluckey')}
Apr 18 15:06:03 2000 [INFO]: Server:tcm-glenelder
SNMPUser:.1.3.6.1.4.1.429.4.10.1.1.18.1788 User:ejluckey
Sending Ack of id 111 to d12a4f23 (tcm-glenelder) User-Service =
Framed-User
Framed-Protocol = PPP
Session-Timeout = 18000
Idle-Timeout = 900
Class = "IEAS1\0031172\0018"
Resp Time: 47 Auth: 21/1 -> 22 Acct: 45/0/0 -> 45
Seems like you fix one thing, then that breaks something else... This user
should not have been able to get on. Any ideas?
-----------------------------------------------------------------
Thanks,
TKT
-----------------------------------------------------------------
----- Original Message -----
From: "Dale E. Reed Jr." <daler@iea-software.com>
To: <emerald@iea-software.com>
Sent: Tuesday, April 18, 2000 2:34 PM
Subject: Re: Fw: [Emerald] Work on SNMP Concurrency Checking
> NCKCN wrote:
> >
> > Okay, pretty much confirmed that SNMP will work only running in debug
mode.
> > Is this possible? When I run as a service, I get users "hung" and denied
> > service even with SNMP all set up correctly. I stop the service, run as
> > radius -x31 and SNMP Concurrency works perfectly. Any ideas?
>
> Go into the RadiusNT admin, and define your auth and accounting
> logfiles.
> Then use regedit to modify the debug registry setting and change it to
> 31 and restart the service.
>
> You can then use a tool like tail
> (ftp://ftp.iea-software.com/NT/TAIL2.EXE)
> to watch the logfile and see whats going on, just like foreground debug
> would show. This is a very handy setup for watching RadiusNT from a
> remote computer, but be careful with the file size. I like 18 for
> debug as its smaller output.
>
> --
>
> 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
For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart