Home > Windows > Access server locally using alias name failes (archive)

Access server locally using alias name failes (archive)

Error message when you try to access a server locally by using its FQDN or its CNAME alias after you install Windows Server 2003 Service Pack 1: “Access denied” or “No network provider accepted the given network path.

\<servername><sharename>

In this scenario, you experience one of the following symptoms:
• You receive repeated logon windows.
• You receive an “Access denied” error message.
• You receive a “No network provider accepted the given network path” error message.
• Event ID 537 is logged in the Security event log.

P.S.: archive post Dec 1st, 2006

Note: You can access the server by using its FQDN or its CNAME alias from another computer in the network other than this computer on which you installed Windows Server 2003 SP1.

Additionally, you can access the server on the local computer by using the following paths:
• IPaddress-of-local-computer
• Netbiosnameor ComputerName

Click on read more to get the fix…

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlLsaMSV1_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 or the DNS alias, that is used for the local shares on the computer, and then click OK.

Note Type each host name on a separate line.

Note If the BackConnectionHostNames registry entry exists as a REG_DWORD type, you have to delete the BackConnectionHostNames registry entry.
7. Exit Registry Editor, and then restart the computer.

MS Link: KB926642

Categories: Windows Tags: