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. www.iea-software.com
For more information about this list (including removal) go to:http://www.iea-software.com/support/maillists/liststart