Re: SQL Cluster environments - serious problem NT AUTHORITY\ANONYMOUS

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

We had a problem that seems to be like yours some. I opened a case at Microsoft and they gave us a two-step workaround:
- set the DisableStrictNameChecking registry entry to 1
- set the DisableStrictNameChecking registry entry to 1
You may give it a try. Be careful, it worked for me, no warranty that it's ok for you:
--------------------------------
1. 914060 A logon window appears in Windows Server 2003 Service Pack 1 NLB when you try to browse the virtual NLB cluster name
http://support.microsoft.com/default.aspx?scid=kb;EN-US;914060

2. WORKAROUND
Warning This workaround may make your computer or your network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend this workaround but are providing this information so that you can implement this workaround at your own discretion. Use this workaround at your own risk.
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To work around this problem, set the DisableStrictNameChecking registry entry to 1. Then, use one of the following methods, as appropriate.
FROM:
http://support.microsoft.com/kb/281308/


Windows Server 2003
To resolve this problem in Windows Server 2003, complete the following steps:
1. Create the CNAME record for the file server on the appropriate DNS server, if the CNAME record is not already present.
2. Apply the following registry change to the file server. To do so, follow these steps:
a. Start Registry Editor (Regedt32.exe).
b. Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
c. On the Edit menu, click Add Value, and then add the following registry value:
Value name:
Data type: REG_DWORD
Radix: Decimal
Value: 1
d. Quit Registry Editor.
1. Restart your computer.
---------------------------------------------------

Good luck
Pierrot



"anxcomp" <anxcomp@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:42EFF911-1A0F-472B-80C2-C80BE61DC79F@xxxxxxxxxxxxxxxx
Hello,

I'm trying resolve common serious problem in my cluster environments (it
appear only in SQL cluster environment, no problem with standalone
installation).

I run two node cluster (A/A), sql server and cluster service work under
domain admin account. Whenever I try connect to other resource/server (for
example network share \\ from job) outside the cluster in the same domain ,
sql break security context and I receive "NT AUTHORITY\ANONYMOUS LOGON" on
destination server.

I started few months ago topic on SqlTeam forum, but unfortunately didn't
get explicitly answer

http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=107269

Another example, two instances:

VIRTUAL1\SQL1 - SQLServer
VIRTUAL2\SQL2 - SQLServer, Analysis Services

When I created Linked Server on VIRTUAL1\SQL1 to VIRTUAL2\SQL2 (Analysis
Services) I got "NT AUTHORITY\ANONYMOUS LOGON" when try connect, when Linked
Server is on VIRTUAL2\SQL2 I'm able connect to VIRTUAL2\SQL2 (Analysis
Services).

I think it is the same problem as I experience with sql agent (described at
SqlTeam forum).

Could anybody help me find where is the problem, please. Active Directory,
Cluster Service, SQL ?

SQL 2005, Windows 2003

--
Regards,
anxcomp

.

Relevant Pages

  • Re: Printmig.exe 3.1 error...
    ... Seems there was a registry key named ... ",2" that was listed as the first print queue in the registry that did not ... imported into the new Print Cluster with no issues. ... already migrated one print server from our old cluster to the first instance ...
    (microsoft.public.windows.server.general)
  • Re: Erroneous Cluster mode....
    ... entire registry for "clusterintallationstate" and it was ... >> because it said that the server was part of a cluster. ... >> could it suddenly become a member of a cluster, ...
    (microsoft.public.windows.server.clustering)
  • Re: Windows 2003 Standard Server believes to be a clustermember
    ... This registry value is installed by default in Windows Server 2003, ... Windows NT/2000/2003 Cluster Technologies ...
    (microsoft.public.windows.server.clustering)
  • Re: Cannot remove cluster node
    ... Here is how to forceably remove the cluster. ... Create a new registry file: ... \Cluster Server] ... the lab to be put into production. ...
    (microsoft.public.windows.server.clustering)
  • RE: issues authentication w/2003 server AND SP1, IIS 6, FPSE 2002
    ... Server 2003 with Service Pack 1. ... In Registry Editor, locate and then click the following registry key: ... > following article number to view the article in the Microsoft Knowledge Base: ...
    (microsoft.public.frontpage.extensions.windowsnt)