Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Login Resolution To Wrong Domain Account


Login Resolution To Wrong Domain Account

Author
Message
Ted Zatopek
Ted Zatopek
SSC Rookie
SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)

Group: General Forum Members
Points: 39 Visits: 200
We have a domain ID that was created under a particular name and then renamed in AD under the same SID. Occasionally SQL starts to resolve login attempts under the old name instead on the new name. So application login attempts fail. I can verify this is happening by doing the following...

1. Open the new login dialog box and click on search.
2. Type in Domain\NewDomainName and click on Check Names.
3. The correct ID (the new name) is displayed.
4) Click OK
5) The incorrect ID (the old name) is displayed.

If I then type in the correct ID name and click OK, the correct new name is added to the login list. The login attempt to the application is then successful.

The problem is resolved for several days and then it reoccurs.

The current suggestion in my group is to reboot the boxes, but I can't get downtime for a couple of weeks. The environment is a 3+1 cluster on 4 64-bit boxes.

Anybody have any ideas on what the root cause of this could be?

Thanks for any help



RBarryYoung
RBarryYoung
SSCrazy Eights
SSCrazy Eights (9.4K reputation)SSCrazy Eights (9.4K reputation)SSCrazy Eights (9.4K reputation)SSCrazy Eights (9.4K reputation)SSCrazy Eights (9.4K reputation)SSCrazy Eights (9.4K reputation)SSCrazy Eights (9.4K reputation)SSCrazy Eights (9.4K reputation)

Group: General Forum Members
Points: 9436 Visits: 9517
Yes, SQL Server does seem to "sticky-cache" a lot of the AD security information for a long time. Rebooting your server is probably the recommended way to fix that.

Alternatively, you could try removing the Login from SQL Server and then re-adding it. That might work, but it might also be more trouble than it's worth.

-- RBarryYoung, (302)375-0451 blog: MovingSQL.com, Twitter: @RBarryYoung
Proactive Performance Solutions, Inc.
"Performance is our middle name."
Ted Zatopek
Ted Zatopek
SSC Rookie
SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)

Group: General Forum Members
Points: 39 Visits: 200
Thanks for the info. "sticky-cache" does seem like a pretty appropriate description of this AD behavior.

I had tried removing the ID and readding it, but unfortunately that didn't resolve the sticky-ness. :-)



Orlando Colamatteo
Orlando Colamatteo
SSCrazy Eights
SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)

Group: General Forum Members
Points: 8229 Visits: 14368
I rarely recommend it, but in this case I would try rebooting too.

This thread has a lot of the same symptoms: http://www.sqlservercentral.com/Forums/Topic1328455-1550-1.aspx

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Ted Zatopek
Ted Zatopek
SSC Rookie
SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)

Group: General Forum Members
Points: 39 Visits: 200
That thread does sound like the same thing.

Thanks for your help! For some reason, it's a little comforting to know that someone else seems to be experiencing the same thing.



Ted Zatopek
Ted Zatopek
SSC Rookie
SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)SSC Rookie (39 reputation)

Group: General Forum Members
Points: 39 Visits: 200
We did get an approval for a reboot and that solved the issue.



Orlando Colamatteo
Orlando Colamatteo
SSCrazy Eights
SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)

Group: General Forum Members
Points: 8229 Visits: 14368
Good to know, thanks for posting back the resolution.

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search