If Windows authentication is not working in contentACCESS and an alias was created for contentACCESS

Introduction

This page describes a known issue in which Windows authentication fails for inPoint or contentACCESS File Server Shares when they are accessed through an alias name, and explains how to resolve it by updating the Windows registry on the server running IIS.

Problem

Shares with an alias name cannot be opened on the inPoint / contentACCESS File Server.

Solution

Update the registry key described below on the server running IIS to resolve the issue.

1. In Registry Editor, locate and click the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
2. Right-click MSV1_0, point to New, and then click Multi-String Value.
3. Type BackConnectionHostNames and press ENTER.
4. Right-click BackConnectionHostNames and click Modify.
5. In the Value data box, type the host name or host names for the site(s) that are on the local server (for example, myapp.mydomain.com), and then click OK.

info

Note: Restart the IIS service after modifying the registry key for the change to take effect.