Windows dns cname alias

Security, Compliance and Identity. Microsoft Edge Insider. Azure Databases. Autonomous Systems. Education Sector. Microsoft Localization. Microsoft PnP. Healthcare and Life Sciences. Internet of Things IoT. Enabling Remote Work. Small and Medium Business. Humans of IT. Green Tech. MVP Award Program. Video Hub Azure. Microsoft Business. Thank you for your post here. Connecting to SMB share on a Windows based computer or a Windows Server based computer may not work with an alias name.

If the issue persists, could you please provide the exact error message received when you attempt to access the share with CNAME? If you have any questions or concerns, please do not hesitate to let me know.

Office Office Exchange Server. Not an IT pro? Windows Server TechCenter. Sign in. United States English. When you enable the "Remove this item when it is no longer applied", it enables "replace".

I said other than using replace in the GPO because I wanted to learn something new since i never use aliases for file servers and wanted to find what the issue was with regards to that alias. I had already replaced the drive mappings via gpo.

Since my question wasn't how on to update drive mappings that part was just irrelevant to my question and I was just curious on if anyone had any other ways they had done it. Ah, gotcha. Read that part too quickly before replying - it seemed like you couldn't use "replace" for some reason and wanted suggestions for other methods.

I suggest coming up with a plan to remove the CNAME and implement DFS namespace, or add the hostname as per the resolution section in the article above.

Thank you for the link! I will be sure to read up on it. I have been planning to implement a DFS namespace since I dislike CNAME aliases for anything, let alone a file share, but time wise I had not gotten around to it since noticing the issues.

You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.

The SPN may be incorrect because it's registered for an old server. That is, the first component of the SPN will always be the user supplied name as in the following example:. To resolve this issue on a file server that is running the SMB version 1 protocol, add the DisableStrictNameChecking value to the registry:. We don't recommend that you resolve this issue for a file server that isn't Windows-based by typing the following commands in an elevated Command Prompt window on a Windows-based computer.