Re: Server registration lost after domain password change

From: Billy Yao [MSFT] (v-binyao_at_online.microsoft.com)
Date: 04/08/04


Date: Thu, 08 Apr 2004 04:12:24 GMT

Hello Per,

I learned that when changing your domain user password on the WinXP client, you will lose registered SQL
Servers in SQL Enterprise Manager. In addition, you applied the method in KB 323280 but the problem
persists if you change the password.

===========================

Based on my experience, even after applying SP1 for Windows XP, we may still experience the same
problem. The methods in the following Knowledge Base (KB) articles should solve the problem you met
with:

323280 FIX: Registered remote servers disappear from SQL Enterprise Manager in
http://support.microsoft.com/?id=323280

316994 Denied Access to Encrypted Files After You Change Your Password
http://support.microsoft.com/?id=316994

===========================

Nevertheless, the fix in XP service pack 1 only works if the registry key "MasterKeyLegacyNt4Domain" is
set on the Windows XP machine:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-
8c7a-00c04fc297eb]
"MasterKeyLegacyNt4Domain"
Type: REG_DWORD
Value: 00000001

To add that key, you can follow the detailed steps below:

a) Open Registry Editor (Start-> Run -> Regedt32)
b) Go to the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-
8c7a-00c04fc297eb
c) Create the follow value (Edit->New->DWORD Value):

        Value Name: MasterKeyLegacyNt4Domain
        Value Type: REG_DWORD
        Value: 00000001

d) Change your network account password and login again to see if the problem goes away.

===========================

If the problem still cannot be suppressed, please help provided us with the following information:

1) Whether or not the problem happens on all WinXP clients which have applied Service Pack 1 and added
that registry key.

2) Please check the 2 DLL files mentioned in the KB 316994 above
        Lsasrv.dll & Msv1_0.dll

3) Check if the servers' registration will come back if you change the password back and login again.

4) Determine your SQL Server's actual version by executing the following script in Query Analyzer:

----------------------------------------------------
SELECT @@version
SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'),
SERVERPROPERTY ('edition')
----------------------------------------------------

Best regards,

Billy Yao
Microsoft Online Support
----------------------------------------------------
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.



Relevant Pages

  • Re: using PIAS at the time of deployment
    ... PIA's do not contain any code, they are simply .NET metadata representing ... the COM interfaces exposed by the native COM servers. ... > suite and then manually added the files in the global assembly cache ... > and registered them in the registry also. ...
    (microsoft.public.dotnet.framework.interop)
  • RE: User rights on Terminal Services
    ... For actually using COM servers and ActiveX controls, ... User rights on Terminal Services ... I am not sure if there is any registry tomfoolery in it - what is the best ...
    (Focus-Microsoft)
  • Re: Question on event log errors
    ... other then your regular windows updates and the live update from symantec. ... Registry failed unrecoverably. ... The hardware of these 2 servers are identical. ...
    (microsoft.public.windows.server.general)
  • Re: interval of time-synchronization
    ... Do you mean there are no servers listed or the servers time out? ... Have a look the following Registry keys' value - do you have these two listed: ... | "Will Denny" schrieb im Newsbeitrag ... | MS-MVP Windows - Shell/User ...
    (microsoft.public.windowsxp.general)
  • Re: potential replication problems --
    ... the "enable journal wrap automatic restore" registry hack and was ... replmon and sonar look fine on both servers ... Active Directory could not use DNS to resolve the IP address of the ... source domain controller listed below... ...
    (microsoft.public.windows.server.active_directory)