Windows domain problems?

[george]

Hello,

I have installed DB2 v8.1 on a windows 2000 machine that is part of a
domain but not the domain server. I set the authentication to Client
and trust all clients. I have a problem with users logging on to the
database as follows:

I have 3 users user-a, user-b, user-c

If I am logged into a workstation or the database server at the
operating system level on the network as user-a, I can not log on to
the database as user-a but I can log on as user-b or user-c. If I log
on to the workstation as user-b, I can log on to the database as
user-a or user-c but not user-b. If I log on to the workstation as
user-c I can not log into the database as user-c but I can as user-a
or user-b.

I set up the clients to use what ever authentication was specified in
the database (client in this case).

Any suggestions on how to resolve this?

Thanks

George

[Garfield Lewis]

Hi George,

Are the users defined both locally and on the domain? If so do they have the
same password? Has the security service been started ("net start
db2ntsecserver" if not)? Do you have the DB2_GRP_LOOKUP set?

--
Garfield A. Lewis
DB2 UDB Development,
IBM Canada Laboratory
"george" <gm*****@rrsytec.com> wrote in message
news:b3**************************@posting.google.c om...

Hello,

I have installed DB2 v8.1 on a windows 2000 machine that is part of a
domain but not the domain server. I set the authentication to Client
and trust all clients. I have a problem with users logging on to the
database as follows:

I have 3 users user-a, user-b, user-c

If I am logged into a workstation or the database server at the
operating system level on the network as user-a, I can not log on to
the database as user-a but I can log on as user-b or user-c. If I log
on to the workstation as user-b, I can log on to the database as
user-a or user-c but not user-b. If I log on to the workstation as
user-c I can not log into the database as user-c but I can as user-a
or user-b.

I set up the clients to use what ever authentication was specified in
the database (client in this case).

Any suggestions on how to resolve this?

Thanks

George