Re: [RadiusNT] Funky Cisco 5300 Port Attributes

Matt Nelson ( )
Mon, 09 Aug 1999 08:35:59 -0500

No I don't have Server Access enabled. I didn't mean to imply that the user
couldn't log on. They can. It's just that things such as an expired
account will continue to work if they hit a port that is not in the
database. I figured this out from noticing a test account I had would
disconnect after about 2 minutes sometimes, and other times not disconnect
until you told it to (from the client machine). The thing was the test
account had expired in Emerald, and after the user was logged in for about
2 minutes, it would disconnect. (Which brings up another small point, I
thought if the user was expired, Emerald/RadiusNT would send an immediate
reject, not even allowing the user in.) This only happened if the user
happended to connect to a port RadiusNT knew about of course.). Now that I
seem to have gotten the Async connects resolved, it's the ISDN connects
that I have left to get working correctly. Does that make it a little
clearer? :-)

Matt Nelson N5TKN
NCC Internet / Northeast Arkansas Net.Works

>I don't follow here. The lack of the entry in the ServerPorts table
>will NOT prevent the user from getting online (unless you have
>Server Access enabled). Attributes are associated to the user's service
>type or their own account, not the port they log into.
>Dale E. Reed Jr. Emerald and RadiusNT
>IEA Software, Inc.

For more information about this list (including removal) go to: