Solved

SQL 2005 Error 18456

Posted on 2009-04-15
11
423 Views
Last Modified: 2012-05-06
I have a pc that gets an error when trying to set up an ODBC connection. I get the error code 18456, SQLSTATE 28000. "LOGIN FAILED for X user. It is set up as Mixed mode authentication, but it is only happening on 1 pc. When the user goes to another pc, it works fine (when making the same connection). Any thoughts on any local settings to check for this? We're running McAfee and pretty much disabled it to see if it was blocking any ports. Thanks for your help
0
Comment
Question by:SLNNT
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 5
11 Comments
 
LVL 8

Expert Comment

by:SNilsson
ID: 24148845
Are you using Windows NT authentication in the Dsn, on all computers you have tested or do you sometimes use SQL server authentication ?
0
 

Author Comment

by:SLNNT
ID: 24148874
Win NT authentication on all of them. It works on every other computer but this one
0
 
LVL 8

Expert Comment

by:SNilsson
ID: 24148994
There is a connection to the server since you get 'login failed', so dont worry about ports and such on the client.
When this person goes and try on another working computer I guess that the current user logs out and he logs in to the active directory, if not you are connecting using different accounts.
Also you might want to try loggin on with another account on the faulty machine and see if its an account problem.

0
Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.

 
LVL 8

Expert Comment

by:SNilsson
ID: 24149018
Also the computer must of course be a member in the Domain.
0
 

Author Comment

by:SLNNT
ID: 24149042
The pc is on the domain, and when I log in to the pc, it works. I have tried deleting the user profile, and have the user log back in to recreate it, and still doesn't work. The user should have the same AD credentials as I do.
0
 
LVL 8

Expert Comment

by:SNilsson
ID: 24149273
Since he has logged on to another computer and succesfully connected.
I can only think of a few scenarios:
1. Another user is logged on to windows when he test on another computer.
2. He logs on with a local account when using his own computer.
3. The Dsn does not save the machine configuration on his computer, he might not be adminitrator on the machine.

 
0
 

Author Comment

by:SLNNT
ID: 24149371
Those are the things I considered but..
1. He logged in under his name on a different pc (same domain)
2. Logs into domain on his pc
3. We added him along with domain admin to admin group on pc with same result
0
 
LVL 8

Expert Comment

by:SNilsson
ID: 24149477
Only thing I can think of is that you can set up a trace on the SQL server when he logs in and hopefully get a more verbose error, and also run the trace when he log in from another computer to see if there is any differences in the credentials.
0
 

Author Comment

by:SLNNT
ID: 24149644
ok, I looked at the Log files and when he tried to connect I got this..
"SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security"

I need to have this user log in to a different pc and see the log files off of the SQL server
0
 
LVL 8

Expert Comment

by:SNilsson
ID: 24150044
There seems to be a related problem here:
http://www.experts-exchange.com/Databases/Q_21868099.html

0
 

Accepted Solution

by:
SLNNT earned 0 total points
ID: 24171934
figured it out. When you specify the server it connects to (drop down list), instead of choosing an option, I just typed in the server name which I think, caused it to go out and find the server name therefore making a "new" connection
0

Featured Post

Transaction Monitoring Vs. Real User Monitoring

Synthetic Transaction Monitoring Vs. Real User Monitoring: When To Use Each Approach? In this article, we will discuss two major monitoring approaches: Synthetic Transaction and Real User Monitoring.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Recently, when I was asked to create a new SQL 2005 cluster, Microsoft released a new service pack for MS SQL 2005 what is Service Pack 3. When I finished the installation of MS SQL 2005 I found myself troubled why the installation of SP3 failed …
Data architecture is an important aspect in Software as a Service (SaaS) delivery model. This article is a study on the database of a single-tenant application that could be extended to support multiple tenants. The application is web-based develope…
NetCrunch network monitor is a highly extensive platform for network monitoring and alert generation. In this video you'll see a live demo of NetCrunch with most notable features explained in a walk-through manner. You'll also get to know the philos…
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…

691 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question