By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,004 Members | 1,222 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,004 IT Pros & Developers. It's quick & easy.

Intermittant user authentication error

P: n/a
Helpful folks,

We have been having an intermittent and completely unreproducable
problem concerning user authentication on Windows 2000:

[IBM][CLI Driver] SQL1403N The username and/or password supplied is
incorrect. SQLSTATE=08004

DB2 v7.2 fp5
Windows 2000

This is received by various programs that all use the same userid to
connect to our databases. In most cases simply stopping and restarting
the program will cause the connection attempt to work again. I have
never seen any clues that may relate to this problem, until I ran
across this short reference in the Advanced DBA Certification Guide
and Reference (Snow & Phan), under the section "DB2 for Windows NT
User name and Group Name Restrictions":

"DB2 supports a single namespace. That is, when running in a trusted
domains environment, you should not have a user account of the same
name that exists in multiple domains or that exists in the local SAM
of the server machine and in another domain"

Our setup encompasses both of those scenarios, that is our "production
access user id" APPCIC exists as:

DOMainA/APPCIC
DOMainB/APPCIC
Prodserver/APPCIC (the local SAM)

Where DOMainA and DOMainB are trusted domains.

The Certification Guide with the quoted reference is focused on V8 and
the section referes specifically to Windows NT, but I can't help but
think that this may be the cause of our problems. The error is fairly
infrequent, but quite annoying.

Does anyone have any experiences with such a a situation, and could
the definition of our production userid being defined in multiple
domains be responsible for the error message above?

Any help or suggestions would be greatly appreciated.

Sean
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
This annoying design restriction was finally lifted in V8.2. As the doc's
say, what you've done won't work - DB2 searches for the userid over the
possible domains, and if it finds the wrong one first, you'll have problems.
If you cannot update to V8.2, you'll have to use unique userids and/or
enable Kerberos or client authentication.

"Sean C." <db*****@yahoo.com> wrote in message
news:2f**************************@posting.google.c om...
Helpful folks,

We have been having an intermittent and completely unreproducable
problem concerning user authentication on Windows 2000:

[IBM][CLI Driver] SQL1403N The username and/or password supplied is
incorrect. SQLSTATE=08004

DB2 v7.2 fp5
Windows 2000

This is received by various programs that all use the same userid to
connect to our databases. In most cases simply stopping and restarting
the program will cause the connection attempt to work again. I have
never seen any clues that may relate to this problem, until I ran
across this short reference in the Advanced DBA Certification Guide
and Reference (Snow & Phan), under the section "DB2 for Windows NT
User name and Group Name Restrictions":

"DB2 supports a single namespace. That is, when running in a trusted
domains environment, you should not have a user account of the same
name that exists in multiple domains or that exists in the local SAM
of the server machine and in another domain"

Our setup encompasses both of those scenarios, that is our "production
access user id" APPCIC exists as:

DOMainA/APPCIC
DOMainB/APPCIC
Prodserver/APPCIC (the local SAM)

Where DOMainA and DOMainB are trusted domains.

The Certification Guide with the quoted reference is focused on V8 and
the section referes specifically to Windows NT, but I can't help but
think that this may be the cause of our problems. The error is fairly
infrequent, but quite annoying.

Does anyone have any experiences with such a a situation, and could
the definition of our production userid being defined in multiple
domains be responsible for the error message above?

Any help or suggestions would be greatly appreciated.

Sean

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.