Re: [RadiusNT] Funky Cisco 5300 Port Attributes

Dale E. Reed Jr. ( (no email) )
Mon, 09 Aug 1999 09:40:04 -0700

Matt Nelson wrote:
> 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

I still don't follow. As I mentioned earlier the lack of the entry
in the ServerPorts table will NOT cause this. What was the disconnect
cause (if it reports it in the Stop record) on the calls? That
just sounds like either line problems, noisy modems, or something
in that area.

> 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

It will.

> 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? :-)

Nope. I'm guessing there is another reason for this, as the things
you are describing are not behaviors of RadiusNT. :(


Dale E. Reed Jr. Emerald and RadiusNT__________________________________________IEA Software, Inc.

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