Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Windows 10 issue with mapped drive

Posted on 2016-08-08
5
Medium Priority
?
66 Views
Last Modified: 2016-08-15
Been running some test PCs with Windows 10 installed and noticed this issue.
We currently have logon scripts which map a user to their needed network drives.

In this case, the mapped drive references an old server name which is actually a CNAME to the current server.
In Windows 7, this is working fine and the drives are mapped.

In Windows 10, when a user logs in, there is no drive mapped or error displayed.

It is when I try mapping it manually that I get the error "The target account name is incorrect."
Doing a ping test, the server name resolves fine and I can ping the server.
If I map it using the current server name, it works.

Is there a setting in Windows 10 I need to change?
0
Comment
Question by:SeeDk
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
5 Comments
 
LVL 14

Expert Comment

by:Don Thomson
ID: 41747334
Can you map it in Windows 7 using the new name. If you can - change you login script to use the new name.  If not then modify the login script to change it based on the OS
0
 

Author Comment

by:SeeDk
ID: 41747388
Yes, it can and I had thought of changing the script but wanted to see if there is a way to fix it on Windows 10 without touching that.
I don't know the reason for the CNAME existing and would have to check if there are any applications relying on this naming before making a change.
0
 

Author Comment

by:SeeDk
ID: 41747550
Found this in Event Viewer logs on the PC when it tried connecting to the share the first time.
Doing it a second or third time does not log an error although the same pop up error message appears.

The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server server2$. The target name used was cifs/server1. This indicates that the target server failed to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Ensure that the target SPN is only registered on the account used by the server. This error can also happen if the target service account password is different than what is configured on the Kerberos Key Distribution Center for that target service. Ensure that the service on the server and the KDC are both configured to use the same password. If the server name is not fully qualified, and the target domain (DOMAIN) is different from the client domain (DOMAIN), check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server.
0
 

Accepted Solution

by:
SeeDk earned 0 total points
ID: 41750576
This registry key mentioned here: https://support.microsoft.com/en-us/kb/926642
is meant for Windows Server 2003 but it still applies in Windows 10.

Went to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
Added Multi-String value BackConnectionHostNames and typed in the CNAME as the value.

Rebooted and it is now working!

Tried many, many other registry fixes and suggestions before landing on this one.
Went back to the PCs and undid all the other fixes just to confirm this was the only one needed.

Don't know why this is such an obscure fix, I would imagine there are many environments which have CNAMES set up on file servers for DR purposes.

Just glad this got it working even on the recently released 1607 build.
0
 

Author Closing Comment

by:SeeDk
ID: 41756114
Solution found outside of EE.
0

Featured Post

Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Configuring Remote Assistance for use with SCCM
An introduction to the wonderful sport of Scam Baiting.  Learn how to help fight scammers by beating them at their own game. This great pass time helps the world, while providing an endless source of entertainment. Enjoy!
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…

715 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question