Problem with Windows Client connecting to DB2 Server

I'll start by saying that I know very little about db2. I am proficient with MS-SQL, but not DB2.

I have a DB2 v9.1 server running on Linux (RHEL4). This server has been in operation since Aug. 07. I have a website that accesses data from this server. The website is written in ASP and is running on a Windows 2000 Server with SP4. Everything has been working fine since August.

Recently we had a major power problem in our office that caused the Windows System to be corrupted and we wound up formatting the system and re-installing everything. I re-installed windows, restored the web site files from a backup and installed the IBM DB2 Client (v9.1 Fix Pack 4a) I downloaded the client from here: http://www-1.ibm.com/support/docvie...uid=swg21255394

The problem I am running into is that the asp page is unable to connect to the db2 server and reports the following error:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[IBM][CLI Driver] SQL30082N Security processing failed with reason "24" ("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001
/refportal/status1.asp, line 63

Just to be clear, the DB2 server has not been modified in any way and the connection string in the asp file has not been modified, so I cannot understand why I would have a user name/password issue unless there is some setup I have to do with the client that I have missed.

I contacted the company that originally setup our system. Their DB2 expert is no longer with them and has not yet been replaced, so they have been unable to help me.

This link shows screen shots of the install of the DB2 client on my web server: http://www.applicationgroup.com/test/db2install.htm

I have done no configuration of the db2 client beyond what is shown in those screen shots.

This is the connection string in use in the asp page (line 63 as specified in the error message):
conn.Open("Driver={IBM DB2 ODBC DRIVER};Database=MyDBName;Hostname=192.168.xx.xx;Port=50000;Protocol=TCPIP;Uid=xxxxxx;Pwd=xxxxxx;")

Thanks for any help,

Neal

I actually needed to create a user on my Windows Server with the same credentials used in the connection string. I don't know why this was required, but it did solve the problem.

Before doing this I was able to load the control Center and see the table names. I couldn't open the tables, but when I tried I noticed that it was stating that the user did not have rights to open the table and it was showing my Windows Login name. This gave me the idea of creating the user credentials in Windows to match the DB2 connection string I already had. I logged in as that user and was able to open the tables in the Control Center, so I tried the web site and that was working as well.