troubleshooting Question
Windows 10 issue with mapped drive
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?
Learn from the best
Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.
Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 5 Comments.
Try for 7 days”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.
Our community of experts have been thoroughly vetted for their expertise and industry experience.