Isn't 2.3b the one that had a bug and would refuse connections
when using the Emerald DLL? I would make sure you have
2.3c (I just checked, and 2.3c is the version I have).
> 3.My ODBC has an entry for Emerald pointing to our Emerald machine
> (tsunami)
Nice name. I have a bunch of boxes with storm names. :)
> I've read through the mailist and I can't find an answer that will work.
>
> Here's part of my su_dll.log
>
> Tue Nov 18 16:52:47 1997 HandleClientEvent 3: GIONET
> Tue Nov 18 16:52:47 1997 HandleClientEvent 3:
> Tue Nov 18 16:52:47 1997 LoadUser GIONET
> Tue Nov 18 16:52:47 1997 LoadUser Bad
> Tue Nov 18 16:52:47 1997 HandleClientEvent 3: Status: 0
> Tue Nov 18 16:52:51 1997 HandleClientEvent 3: GIONET
> Tue Nov 18 16:52:51 1997 HandleClientEvent 3: mypassword
> Tue Nov 18 16:52:51 1997 LoadUser GIONET
> Tue Nov 18 16:52:51 1997 LoadUser Bad
> Tue Nov 18 16:52:51 1997 HandleClientEvent 3: Status: 0
Could this be a case problem? How about adding a registry
option of IgnoreCase set to 1. The LoadUser is basically
saying it could not find the GIONET user. Check the case
and the database as well.
-- Dale E. Reed Jr. (daler@iea-software.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com