Could be about several problems with Network Settings, PC Security and others. This method bypasses those and will give you access. If you even could 'see' that drive, you should use the PING command from Command Prompt (CMD) to ping the IP of that drive. If that fails, it could also an hardware problem. Without to have access to machine, it's difficult to give an correct answer.
I can access via IP Address and I put a hosts entry in but that still doesn't fix the problem Microsoft has created.
This hasn't been working since 10041 I believe. In 9926 it worked just fine although I would have to add a Windows Credential for 9926 to access the files but I could at least see the device. And this most certainly is not a hardware problem.
You could simply Map as Network Drive! As long as you use an Preview/Alpha/Beta, you could have different problems with any of the editions! Take it as it's works, so you could do and access what you need. If you like to spend time and dig into those problem, it's in real just losed time at some point and that could be already with very next build. I wouldn't bother with that, you got the access you need, and that's the only thing which counts!
That's what I have done, however I don't think you can create a Symbolic Link if you cannot see it under the Network Icon.
Well is still the only bulletproof way to access a share in 2015. Especially on networks where OS from different kind or generations are present, given the attitude of MS to break things on SMB/CIFS protocol is still unmatched. I guess they did it again, and the users have to wait for a new SAMBA release (and then firmware upgrades on appliances) to properly see the shares as they are used to.
I have no such problems with '49 (10041 clean install -> WU upgrade to '49). I tried to map Win10 and Win8.1u PC shares and an SMB share from my OpenWRT router. Everything works fine. Although, IOMeter (1.1.0 x64) doesn't seem to find my mapped drives. (That's why I searched for Win10 mapping issues.) But in the mean time I realized I have that problem with Win 8.1u (shares mapped under Win8 client from various LAN servers including Windows and Linux) as well (so it must be broken since Win 8.x and/or regardless of Windows version [host] in this IOMeter build).