Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
SiggePersson
Starting Member
3 Posts |
Posted - 2010-10-04 : 09:08:41
|
Hi.I have a SQL login to a database.There are two servers that use it, one test server and one production server.The Test server can login using that login, the production server can not."Login failed for user xxx"All three servers belong to the same domain.Using ODBC DataSource administrator, with Windows NT integrated security, i successfully connect from both servers.But when i switch to specific user name and password, the production server fails.Conncection failed:SQLState:'28000'SQL Server Error:18456[Microsoft][SQL Native Client][SQL Server]Login failed for user 'xxx'I am at a loss to where to start the error search.I dont believe its really something wrong with SQL in itself, but rather something related to the network and how the servers are setup, but i am hoping someone in this forum will be more "in tune" with networking than me.Thanks in advance.Sigge |
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2010-10-04 : 12:04:20
|
Have you verified that the login exists on the production server and it has the password you are using?CODO ERGO SUM |
|
|
SiggePersson
Starting Member
3 Posts |
Posted - 2010-10-05 : 04:03:45
|
It is just a login that exists in SQL, not a windows account.Production and Test use the same SQL database (read only) |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2010-10-05 : 08:59:52
|
so u are using a DSN to connect? sure you're (1) using the correct DSN and (2) That is is a system DSN and (3) you're passing the proper credentials?if this doesn't help, create a UDL on the server that you CAN connect from. Copy that to the one you can't and use the "test connection" function of the UDL.To create a UDL1. Right-click empty portion of desktop.2. Choose NEW, Text Document3. Rename txt file to "test.udl"4. Double-click the icon5. Enter correct info in the provider and connection tabs6. Click Test Connection |
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2010-10-05 : 09:40:58
|
quote: Originally posted by SiggePersson It is just a login that exists in SQL, not a windows account.Production and Test use the same SQL database (read only)
OK, but you didn't answer my questions:"Have you verified that the login exists on the production server and it has the password you are using?"CODO ERGO SUM |
|
|
SiggePersson
Starting Member
3 Posts |
Posted - 2010-10-06 : 10:21:00
|
It has been resolved.The SQL-server had been upgraded to 2008 by the owner, and the testserver had 2008 native client installed, but not the production server.Thanks for your time and help. |
|
|
|
|
|
|
|