-952 Authentication Error on Solaris 10

Ian Michael Gumby wrote:
> Superboer,

> order to get a -952 issue, its a server generated issue. So maybe its
> a configuration issue in ODBC? Like the password isn't coming across
> ok or that the user doesn't have connect privileges with the specified
> db? (And that could be it.)

If the user doesn't have connect privileges, then the error is different.
IDS first goes through the authentication process (making sure you're the one
you're saying), and then checks the privileges. Each situation has a different
set of errors.
Some versions had an issue with passwords longer than 8 characters. I think
this was specific to Solaris. It's easy to check if anybody thinks that this
maybe the issue (you can change the password, if it's longer than 8 chars, for
testing purposes).

Regards.


--
Fernando Nunes
Portugal

http://informix-technology.blogspot.com
My email works... but I don't check it frequently...

On Mar 26, 4:41 pm, nate....TakeThisOut@kc.rr.com wrote:
> I'm running IDS 9.40.FC9 on two new Solaris 10 DB servers - one for
> prod, one for test. The prod one is live and functioning OK. I'm in
> the process of setting up the test one (a little backwards, I know,
> but there are reasons...). I can log into the test box through SSH
> with informix and a couple of different accounts used by the
> application. I can open dbaccess and run SQL commands just fine.
> However, when I attempt to connect from a Windows server via ODBC or
> ILoginDemo, I get a -952 error that the password validation failed.
> Here is the message that appears in the online log:
> Password validation for user [nate] failed!
> Check for password aging/account lock-out.
> listener-thread: err = -952: oserr = 0: errstr = nate: User (nate)'s
> password is not correct for the database server.
> I'm at a loss as to how I can SSH into the server, but still get an
> authentication error when I try to connect to Informix with the same
> account information. Any thoughts or ideas would be greatly
> appreciated.
> Thanks,
> Nate

I never did figure out what the root cause of the problem was. We
ended up restoring an OS backup from prod to test, and after restoring
a Level 0 backup to the test DB server everything started working.
Thanks for all the suggestions.
-Nate