1803 not sharing folder

G'day...Yes 17XX and prior were all very good in establishing connections between devices whether domain or workgroup or homegroup. But since 1803, EVERYTHING (yes yelling) changed. Now M$ wants us to use their cloud features but I simply will not and my customers will not also simply because that is leaving everything open to anyone regardless of the bogus securities any cloud has. Okay enough of that...sorry.


So in 1803 basically in order to maintain some of the environment scenarios we need to change our approach and use some Domain type workarounds. No longer is it possible just to connect to another device without jumping through a bunch of hoops.


@DrSysop...I'm almost done with the conversion and setup I was working on for a customer so I should be back to you shortly. Thanks. Cheers!

I can see the PC on my other machine though network in windows explorer but not the shared folders on there if i click it says windows cannot access:\\(Name of PC) & also on the PC i am sharing the folder I can see the shared folders but if i try to open it in windows explorer on it says same message as other PC. I do not see the public shared folders on main PC also as well as other PC.

This is a different error than you were getting originally (The device or resource (xx-xxx) is not set up to accept connections on port "The File and printer sharing (SMB)")

Windows Cannot Access:\\(Name of PC) is a Sharing & NTFS Permission issue. You need to add Everyone to both Sharing and NTFS Permissions.
1. Right click on the shared folder > Properties
2. Sharing Tab > Advanced Sharing > Permission > Add > Type in Everyone
3. Security Tab > Edit > Add > Type in Everyone

I was thinking of rolling back to 1709 have the iso for it still.

@Eagle51...I agree that it could be a Sharing/Permissions issue but I always shutdown the FW just to make sure it's not a FW issue. Once the FW is down and you still cannot connect then it's definitely not a Sharing/Permissions issue. However, if you can connect with the FW down then it is a Sharing/Permissions issue. Cheers!


@DrSysop...You can roll back to 17xx but FYI, M$ will not support it any longer. Cheers!

G.day here is some more information I was writing up while working. Hope this helps. Cheers!

I reinstalled 1709 on my other 2 pc's with iso & all is dandy with them now & my homegroup was back. I been searching other sites as there is no fix for this yet its an 1803 OS bug. I can not connect 1803 machine to them either but my 1709 can connect to my Windows 7 & Linux Machines :)

DrSysop I was able to get file sharing to work between two computers running Windows 10 1803 by doing the following:

On each computer, go to Control Panel, then Credentials Manager. Click on Windows Credentials and you should see the name of the other computer listed. Remove the credential of the other computer and then add the credential back in (do not Restore the info/ type in the name). For User name and password use an account and password from the other computer. Restart the computer.

This worked for me.

jmx said:

DrSysop I was able to get file sharing to work between two computers running Windows 10 1803 by doing the following:

On each computer, go to Control Panel, then Credentials Manager. Click on Windows Credentials and you should see the name of the other computer listed. Remove the credential of the other computer and then add the credential back in (do not Restore the info/ type in the name). For User name and password use an account and password from the other computer. Restart the computer.

This worked for me.

Didn't work says windows cannot access \\name of pc error code 0x80070035

jmx said:

DrSysop I was able to get file sharing to work between two computers running Windows 10 1803 by doing the following:

On each computer, go to Control Panel, then Credentials Manager. Click on Windows Credentials and you should see the name of the other computer listed. Remove the credential of the other computer and then add the credential back in (do not Restore the info/ type in the name). For User name and password use an account and password from the other computer. Restart the computer.

This worked for me.

This sort of worked for me...

Adding the UID/PWD from the other computer still resulted in an error, when trying to browse the network:



Connecting to the network share manually did get around this error:

Code:

C:\Users\UID>net use \\Other PC\share name

Once the command executed, all shares on the other PC showed up in "Explorer\Network\Other PC". Every time either of the computers are rebooted, the "net use" command needs to run again.

Since I don't really know what MS does with the UID/PWD in "Credential Manager", local and/or uploaded to the cloud, I deleted the other PC from the credential manager. I know, it might be too late...

Doing so the "net use" command required to enter the credential:

Code:

C:\Users\UID>net use \\Other PC\shared name
Enter the user name for 'Other PC': UID on Other PC
Enter the password for Other PC name: **********
The command completed successfully.

This is also temporary in its nature, reboot either of the PCs requires connecting to the network share manually again.

In W10 1709, sharing files and folder had been really easy. In W10 1803 it's cumbersome to state mildly, there are certainly better words for it.

I cannot believe that this has not been fixed in an update and makes me wonder. Is there going to be even more cumbersome process in the fall update for enabling network sharing for workgroups?

Cr00zng said:

This sort of worked for me...

Adding the UID/PWD from the other computer still resulted in an error, when trying to browse the network:



Connecting to the network share manually did get around this error:

Code:

C:\Users\UID>net use \\Other PC\share name

Once the command executed, all shares on the other PC showed up in "Explorer\Network\Other PC". Every time either of the computers are rebooted, the "net use" command needs to run again.

Since I don't really know what MS does with the UID/PWD in "Credential Manager", local and/or uploaded to the cloud, I deleted the other PC from the credential manager. I know, it might be too late...

Doing so the "net use" command required to enter the credential:

Code:

C:\Users\UID>net use \\Other PC\shared name
Enter the user name for 'Other PC': UID on Other PC
Enter the password for Other PC name: **********
The command completed successfully.

This is also temporary in its nature, reboot either of the PCs requires connecting to the network share manually again.

In W10 1709, sharing files and folder had been really easy. In W10 1803 it's cumbersome to state mildly, there are certainly better words for it.

I cannot believe that this has not been fixed in an update and makes me wonder. Is there going to be even more cumbersome process in the fall update for enabling network sharing for workgroups?

.... or will it EVER be fixed at ALL ???????? This is taking an incredibly long time to fix.... it IS THEIR software.............