August 20, 2007 at 3:34 pm
Hi all. I am experiencing a very strange problem. I manage approx. 12 Servers all running 2000. All are running Mixed Mode. This weekend we installed Windows Updates (alot of them) on both servers and clients. After the updates were installed, the servers were restarted. Since then, when I attempt to connect to one server in particular using Windows Authentication, I get the following error (in Enterprise Manager or Query Analyzer):
SQL Server Enterprise Manager
SQL Server registration failed becuase of the connection failure displayed below. Do you wish to modify anyway?
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGIN'
I am logged into our domain and a member of Domain Admins, etc...
Any Help would be greatly appreciated.
Thank You in advance.
mailto:jtontz@co.riverside.ca.us
August 20, 2007 at 11:56 pm
- which OS are you using ? W2003, XP, ... ?
- did you have a look at :
- http://support.microsoft.com/kb/925001 ?
- http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=110&messageid=246883
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
August 21, 2007 at 9:17 am
Thanks for the info, but I am running ONLY 2000 and have NO linked servers either to or from this server. It is a pretty basic setup. So far, we are seeing the errors when an XP workstation attempts to connect to this server using windows authentication. Almost all of the Windows 2000 Pro workstations appear to connect to this server via Windows Authentication fine (so far out of 4 I have found 1 that doesn't... Developer workstation). Still looking. Any help is appreciated.
August 21, 2007 at 9:43 am
It's a secure channel/AD thing. For some reason your token isn't being accepted.
Check times (need to be fairly synched) among machines. Check the AD channels (need a network/AD person to do this) for both machines.
August 21, 2007 at 11:16 am
Thanks Steve.
One other thing. The server itself... When I login via Remote Desktop and launch Enterprise Manager/ Query Analyzer, I can authenticate via windows authentication (don't know if this helps). When checking the AD channels, should I be checking the clients to the SQL Server, the clients to AD Servers (Domain controllers), or SQL Server to AD Servers?
Please Advise.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply