SQL Server 2000 connectivity question 2

[vamoose]

I have a server running Windows 2003 server and MSSql 2000 sp4.

I have a PC which is running Windows XP-Pro sp2 with which I can connect to the SQL database on the server just fine using an ODBC connection. SQL server driver = 3.85.1117

I have a second PC which is running Windows 2000 sp4 with which I cannot connect to the SQL database on the server using an ODBC connection. SQL server driver = 3.85.1022

Both ODBC connections are identical, and I am using the same username and password, Windows authentication using the network login ID, both PC users have Administrator privledges and I can connect to and browse the contents of the server's hard drives with either PC.

The only thing I can see that is different is the SQL server driver version. Could this be my problem and if so how do I go about upgrading this older driver to a newer version ?

Any other thoughts or suggestions, thank you very much.

 

[ptheriault]

Upgrade your version of MDAC.

- Paul
- If at first you don't succeed, find out if the loser gets anything.

 

[vamoose]

Do you think that this is my problem ? Could you please tell me what version of MDAC am I looking for ? I assume this will be found on Microsoft's web site ?

Thanks so much.

 

[vamoose]

I do have MDAC version 2.8 installed on the Windows 2000 sp4 machine.

 

[gmmastros]

Take a look here: faq962-5481


-George

"The great things about standards is that there are so many to choose from." - Fortune Cookie Wisdom

 

[vamoose]

I have downloaded and installed MDAC 2.81 for Windows 2000, deleted the ODBC connection and re-booted the PC. I now have the driver 3.85.1117 installed. I created a new ODBC connection and it fails connectivity tests with the error of:

Connection failed:
SQLState: '28000'
SQL Server Error: 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.

Does this sound familiar to anyone ? Thanks

 

[ptheriault]

Are you using NT authentication? It sounds like the account you are using may be locked out on the domain or you are not logged in.

- Paul
- If at first you don't succeed, find out if the loser gets anything.

 

[vamoose]

Yes, I am using Windows NT authentication on both PC's. Yet still the XP-Pro sp2 can connect but the Windows 2000 sp4 cannot. Both ODBC connections are now exactly the same. I am stumped.

 

[ptheriault]

Are both PC logged into the Domain with the same user account?
Are you sure that the PC you are having trouble with is actually logged into the domain? Can you release and renew the IP address?

Have you looked at the FAQ that George posted?

- Paul
- If at first you don't succeed, find out if the loser gets anything.

 

[vamoose]

More information that I have found out.
1. The server uses a domain
2. The server has 2 NIC cards
NIC #1 uses a domain
NIC #2 does not use a domain, static IP address, this is the one I am connecting with the following PC's.
3. The Windows XP-Pro and Windows 2000 PC's do not use a domain, both have static IP address.
4. The Windows XP-Pro and Windows 2000 PC's user exists on both these PC's and does not exist on the server.
5. SQL is setup to accept SQL and Windows authentication.
6. This user name does not exist on the server in SQL-Security-Logins yet somehow the XP-Pro machine still manages to connect using Windows NT authentication.
Does this help at all ?

 

[vamoose]

Would the lack of DCOM installed on the Windows 2000 machine prevent it from connecting to the SQL Server ?

 

[gmmastros]

Can you show us the connection string you are using to connect to the database. Obviously, if you are using SQL Authentication, replace the username and password with XXXX's.

Also, if you are connecting using ADO, you would be better off using an OLEDB connection string instead of ODBC connection string. In my experience OLEDB is more stable and faster because it bypasses ODBC.



-George

"The great things about standards is that there are so many to choose from." - Fortune Cookie Wisdom