[WIN9926] \\sharename is not accessible.

I'm seeing this now with my connections to my samba server. Also the 'Windows insider' forum has a thread about this, so it looks like workgroup networking could be completely broken in this build.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You may didn't need Workgroup, just the IP is enough!

In Windows Explorer' Addressbar you type 2 backslash followed by the IP of the NAS Drive. Let say those ip is 192.168.1.65 you type in addressbar: \\192.168.1.65 following by press enter That should open the Log On Screen of your NAS Drive.

 

As I replied above, a number of people seem to be encountering this error with network connections in build 9926. In my case, I'm using a Samba server - others have seen the error with connections to shares on other Windows machines. In all cases, the connections were working before the upgrade.

Personally I'm aware that it's possible to try either the \\machinename or \\ip_address. Both are giving this error. If I open the \\machinename only, I can actually see the shares but trying to open them gives this error again.

 

Ok, thanks to a reply on Technet I have a workaround for this that seems to work !



Using REGEDIT it's necessary to create a DWORD value called 'AllowInsecureGuestAuth' in HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters and set this new value to 1. A reboot will also be necessary.

 

Check the Windows internal Firewall! The whole is simply an Config Problem!

Right click on the Start Buttom and chose Control Panel, go the Windows Firwall and chek all settings. You'll need to allow in- and out going Traffic, even if those runs within your LAN! Also check on the same place that the Private Network is enabled and configured! It's Not an problem of windows, it's just an problem of configuration and security of your network!

 

If you see my more recent reply, someone posted a workaround on Technet when I asked there about the issue. It seems to be about 'Guest' type shares, and apparently the latest build of Win10 deals differently with them. Nothing to do with the Networking side.

 

It simply has a lot to do with Network and Network Security! Network is much more than just connect some computers together using an wired or wireless connection! Proper configuration is the A & O (Alpha & Omega/Start & End) of an network.

 

Yes, it's the security side of it. Apparently the latest build handles things slightly differently, in a way that breaks 'guest' type connections sometimes.

 

@Pisthai, If you re-read all the posts of @farmers carefully, his problem isn't in his configuration(network or firewall) but in the latest build(how can many others have same issue if the problem is not with the latest build). And he also posted a fix for the issue(registry workaround) that is given on the technet thread.

He(OP, to whom you replied) clearly mentioned that he intentionally a network drive Z: to connect to NAS because he couldn't connect directly or normally. And as far as I know, you can make a network drive from any share(whether it's NAS or folder or whole drive shared on the network), so it isn't something to be surprised.

And @farmers, thanks for posting the fix, it will certainly help others.

 

Had the same problem this morning, Spent hours pulling my hair out.
Finally fixed it by..

1) Go to Credential Manager, typed Credential in search
2) Click on Windows Credentials
3) Clicked 'Add a Windows Credential'
4) Typed in the name of my NAS in. Did try the ip address but did not work. If it is already there, Delete it and re add.
5) Added user name and password for the admin account of the NAS

It now works for both username/pass and guest accounts where it worked for neither before. you may need to restart PC.
Hope this works for you too..

 

just to let you know I tried for hours to sort it too but your method works like a charm perfect and so easy thank you for the post

 

Glad it worked for you mate