How map drive on Azure VM Windows 2012 R2
From my Windows 10 Pro desktop I want to map a drive to my VM. I did File Explorer > MY PC > Computers and then set drive letter and used Network Path (\mine\C) from VM > C: properties > Sharing tab > Network Path
But desktop Windows 10 gets error: "cannot access \mine\C) … Error code 0x80070035 The network path was not found."
Same error if I use Network Path \\c
Doug Null
jww1 Answer
The Error code 0x80070035 could be caused by various causes, you can verify these general methods on your side. However, In this case, I think the key point is that you access the windows share or map drive from desktop to Azure VM cross the Internet.
On Windows, you need to open the port 445 (SMB over TCP/IP) to access the file share. But many ISPs or firewall will block port 445 due to security reasons. So you're unable to access the windows share in Azure VM from the on-premise network directly. You can add the port 445 in your NSG associated with your Azure VM subnet and turn off the local windows firewall if needed then check if a port is blocked by your ISP. You also can install Wireshark or Network Monitor 3.4 then capture the network packets to analyze it.
It's recommended to map the drive on-premise network to Azure VM via VPN tunnels. First, You can configure a point-to-site VPN connection with a self-signed certificate in the Azure portal. Once you access your Azure VM via VPN successfully. You will be assigned a private IP address from the VPN address scope. Then you can check if the port 445 is open on Azure VM from your desktop using telnet. When a computer port is open a blank screen will show up, meaning that the connection has been successful. An unsuccessful connection will be accompanied by an error message.
At last, you can map a drive to your VM via its private IP address.
Nancy Xiong - MSFT • edited Sep 28, 2018 by Nancy Xiong - MSFTUser contributions licensed under CC BY-SA 3.0