This problem occurs because Clearwell uses a CNAME alias that is created in the Domain Name Service (DNS) zone to connect to the Clearwell appliance. By default, the server does not 'listen' on the alias, and does not accept connections to that name.
Solution
Disable Strict Name Checking and add Local Security Authority host names that can be referenced in an NTLM authentication request as follows:
Set the DisableStrictNameChecking registry entry to 1
1. Click Start, click Run, type "regedit", and then click OK.
2. Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
3. On the Edit menu, click Add Value, and then add the following registry value:
Value name: DisableStrictNameChecking
Data type: REG_DWORD
Radix: Decimal
Value: 1
Create the Local Security Authority host names that can be referenced in an NTLM authentication request
1. Click Start, click Run, type "regedit", and then click OK.
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
3. Right-click MSV1_0, point to New, and then click Multi-String Value.
4. In the Name column, type BackConnectionHostNames, and then press ENTER.
5. Right-click BackConnectionHostNames, and then click Modify.
6. In the Value data box, type the CNAME, DNS alias and IP, that is used for the local shares on the computer, and then click OK.
*** Note: Type each host name on a separate line. (User hostname on one line and FQDN on the next, and IP) ***
*** Note: If the BackConnectionHostNames registry entry exists as a REG_DWORD type, you have to delete the BackConnectionHostNames registry entry. ***
7. Restart the Server.
Applies To
Windows server 2003 and above (Standalone and Distributed Architecture or Cluster)