Benefit from a mission critical IT monitoring with Monitis Premium or get it FREE for your entry level monitoring needs.
-Over 200,000 users
-More than 300,000 websites monitored
-Used in 197 countries
-Recommended by 98% of users
Course Of The Month
Become a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Windows 10 issue with mapped drive
Posted on 2016-08-08
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?
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?
[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
Active 5 days ago
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
Active today
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.
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.
Active today
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.
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.
Active today
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\
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.
is meant for Windows Server 2003 but it still applies in Windows 10.
Went to HKEY_LOCAL_MACHINE\SYSTEM\
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.
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
The following article is comprised of the pearls we have garnered deploying virtualization solutions since Virtual Server 2005 and subsequent 2008 RTM+ Hyper-V in standalone and clustered environments.
- Virtualization
- Windows 10
- Windows Server 2016
- Windows Server 2012
- Hyper-V
- Windows, Azure, *Clustering
Windows 10 Creator Update has just been released and I have it working very well on my laptop. Read below for issues, fixes and ideas.
This video Micro Tutorial explains how to clone a hard drive using a commercial software product for Windows systems called Casper from Future Systems Solutions (FSS). Cloning makes an exact, complete copy of one hard disk drive (HDD) onto another d…
- Microsoft Legacy OS
- Storage
- Storage Software
- Windows OS
- Storage Hardware
- Windows 10, Windows Vista, Windows 8, Windows 7, *Disk Cloning
If you’ve ever visited a web page and noticed a cool font that you really liked the look of, but couldn’t figure out which font it was so that you could use it for your own work, then this video is for you!
In this Micro Tutorial, you'll learn yo…
- Microsoft Applications
- Windows 10
- Windows OS
- Fonts Typography
- Windows 7, Microsoft Word
Suggested Courses
Earn Certification
HTML5 Specialist - Certification
Free withPremium
Course of the Month5 days, 11 hours left to enroll
Earn Certification
Managing Projects with Microsoft Project 2013 (Exam 74-343)
$49.00$44.10
626 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.