Friday, November 13, 2015

Can't access drive letter after successful network share mapping on Windows 8

I am trying to map a network share to a drive letter persistently on Windows 8.1 (\server\pictures to W:) and after it succeeds, it is not visible in File Explorer nor can I access it by entering the drive letter on "Run".


However, what's confusing is that the system is telling me that the drive is correctly mapped. I've also verified I'm not running any of the processes as the Administrator account, I'm definitely using my user account (that is in the admin group).


Oddly, if I go to the non-elevated command prompt and run explorer.exe w: it will launch file explorer and it will successfully show the drive letter contents.


Update: The problem is solved if I reboot my PC. After reboot, the drive letter W: then shows in explorer and everything is OK. No idea why a reboot fixes this, so would love to know the root cause.


Here are screenshots demonstrating the issues and symptoms:


File explorer not showing the drive letter
file explorer not showing the drive letter


The "Map network drive" feature in File Explorer showing me that's mapped
The


Cmd prompt (run as my user account) also showing it's mapped
Cmd prompt (run as my user account) also showing it's mapped


Trying to use "run" to go to the W: drive letter, also fails
Trying to use

No comments:

Post a Comment

linux - How to SSH to ec2 instance in VPC private subnet via NAT server

I have created a VPC in aws with a public subnet and a private subnet. The private subnet does not have direct access to external network. S...