Tuesday, February 05, 2013 8:27 PMI have a stubborn problem mapping drives from a Windows 8 [home] machine. I can map correctly to shares on my home network NAS. However I cannot map to shares on the corporate (university) network I use, which is running Active Directory using some version of Windows Server (which I think is Server 2008, though apparently the share itself may be located on "a SAN which will have its own custom OS which may not necessarily be Windows"). I can map perfectly well to these shares from other machines (one running XP, the other running Windows 7 Pro). I have seen comments in forums about Windows 8 RT not being able to connect to domain shares, but I am using the full (but not the Pro) version. I connect to the university network via a VPN, but that is not the problem as such, because I can connect to shares on the local hard disk of a user machine on that network, across the VPN, with no problem. The university IT department don't yet support Windows 8 so can't shed any light. If I try to make the connection through Explorer, it just hangs up with nothing happening. If I try to do it through net use in a Command window, passing my username and password, I can map to a group share but not to my personal share - if I try to connect to that, I get "System Error 67 The network name cannot be found". I'd be very grateful for any suggestions - I am currently out of ideas to try. The usual sorts of things like connecting via IP rather than name, turning off firewall and anti-virus, checking NetBios running, have all been tried exhaustively.
Wednesday, February 06, 2013 4:13 AM
SMB3.0 is new in Windows 8 and Windows 2012. I would try the workaround from the KB at first; http://support.microsoft.com/kb/2686098
- Marked As Answer by Cheers ZHANGMicrosoft Contingent Staff, Moderator Tuesday, February 12, 2013 7:09 AM
Wednesday, February 13, 2013 10:45 AM
Thank you for the suggestion below, Yagmoth. Unfortunately, it doesn't work (I should have said in my original post that I had found that KB entry and tried it already, both through PowerShell and by directly editing the registry). I did try it again following your suggestion, in case I had done something wrong before, but it still makes no difference. So has anyone any other ideas, please?
Also, could someone take the "Answered" mark off this question, please? Thanks.
There are no stupid rats, only misguided students
- Edited by seglea Wednesday, February 13, 2013 10:49 AM