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 |
|
jonathans
Starting Member
40 Posts |
 Posted - 2009-09-03 : 09:10:59
|
| Hi Guys,Im getting this error when I try connect to a SQL Server on our network. [Login failed for user '%username%'. (Microsoft SQL Server, Error: 18456)]Now I checked the SQL Log, and it seems that the full detail is[Error: 18456, Severity: 14, State: 11.]A little bit about the background, I am using Windows Authentification on a AD (Active Directory) based network. I am assigned to a user group, and that user group is assigned access to log onto SQL.Now, the problem comes in that, everyone else within my user group can connect to the SQL Server, except for me. We've tried removing me from the user group, and readding me. I've used a different machine entirely, we've even tried to put my AD Username into SQL itself (so as to not have it assigned through a user group). All of this has not worked. I am at the point of getting the admin guys to remove me completely out of the AD, and letting it filter down, then recreating me in AD from scratch again. Though this process (due to red tape) can take upto 6 weeks, so I am doing all I can to avoid this route for that reason, and because I don't have a guarentee that it would resolve the issue.Can anyone else help in trying to help me fix this?PS. I dont have a choice but to use the required security standards of the company I am contracted to.WARNING: Running on cold coffee! |
|
|
RickD
Slow But Sure Yak Herding Master
3608 Posts |
Posted - 2009-09-03 : 10:19:01
|
| How long ago were you added to the AD? Silly question, but have you given enough time for the security to trickle down?Can you check in the group from the server to see the members of that group? If so, are you in there? |
 |
|
|
jonathans
Starting Member
40 Posts |
Posted - 2009-09-03 : 10:27:28
|
| Hey Rick,I was added to the AD about 10 months ago, so its had more than enough time to trickle down. The group in AD indicates that I am in that group, as are my coworkers. Both the AD & SQL Admins say nothing changed on either of their sides respectively.Im left guessing (as a final frustration that some how my account in AD has been corrupted (though not visibly)). But to rectify that im guessing involves deleting my AD account, and recreating it (which as said takes upto 6 weeks) and I'm in the middle of a project.*Points at the law's of Murphy and cries*WARNING: Running on cold coffee! |
|
|
|
RickD
Slow But Sure Yak Herding Master
3608 Posts |
Posted - 2009-09-03 : 10:43:34
|
I have had this happen before, but not for a couple of years.Hopefully its not a local policy in your profile thats causing issues. Other than that, the best thing to do (in most cases where it doesn't take 6 weeks!!!) would be to recreate the user on AD.I feel your pain. Can't you get someone to do this faster, tell them that they messed the user up, so they have to get it fixed, then take on a SQL project that is supposed to be finished yeaterday, then complain to management that you can't do any work, so their project is going to slip..  |
|
|
|
jonathans
Starting Member
40 Posts |
Posted - 2009-09-08 : 03:38:50
|
| Hey RickDWell, i've just been informed this morning (how many days later) that recreating the AD account will not happen, and I must find another resolution to the problem.Oh the joys of red tape and beurocracy. |
|
|
|
RickD
Slow But Sure Yak Herding Master
3608 Posts |
Posted - 2009-09-08 : 04:23:53
|
| Not sure, but as an aside, can you physically or with terminal server, log into the server? |
|
|
|
|
|
|
|
|
Error 18456, State 11