Windows 10: Win 10 File Sharing Not working after 17134 update

I've got a mixed network - a few Win 10 machines and a few Linux Mint 18.x machines. Ten machines in all.
File sharing has been working fine, for the most part.

After the recent update, some of the Win10 systems can't see any of the other computers, but there is something odd.

Some of the Linux systems can see the Win10 system with no problem. For example, I copy Images from a Windows 10 machine to a Small linux box that acts as a Picture frame with a 32" monitor. No problem. This continues to work as it has for a long time. Drive shared read-only from Win 10 system. Reach over from Linux box to get images. Still works after 17134 update on Win 10.

But this same Win 10 machine only sees itself. It can't even see - using the file browser - the machine that can see it, even right after the Linux machine copied files from it.

And another thing. A Linux machine that is mostly off the net could not see any of the Win 10 machines. But it could see the Linux machines. I found this,

[SOLVED] Error connecting windows share (SMB, UFW kernel 4.8) - Linux Mint Forums

and applied the fix to the linux box mentioned at the end of this post. And voila. It can see the win 10 boxes. But this same win 10 system mentioned above cannot see it.

So do we know that Win 10 SMB is basically broken. Not only for Linux, but also for Win 10 itself?
Anybody know a fix that does not involve renaming all the computers? That is nonsense and I will carry thumb drives before I change all the names of my 10 computers. Win 10 will eventually make this work with the same computer names.

BTW, I have not "Joined any HOMEGROUPS" or whatever that bad idea was called now that it's out of the system. And all my machines are on the WORKGROUP network.

Thanks so much,
wg

:)

 

Win 10 File Sharing Not working after 17134 update


I've got a mixed network - a few Win 10 machines and a few Linux Mint 18.x machines. Ten machines in all.
File sharing has been working fine, for the most part.

After the recent update, some of the Win10 systems can't see any of the other computers, but there is something odd.

Some of the Linux systems can see the Win10 system with no problem. For example, I copy Images from a Windows 10 machine to a Small linux box that acts as a Picture frame with a 32" monitor. No problem. This continues to work as it has for a long time. Drive shared read-only from Win 10 system. Reach over from Linux box to get images. Still works after 17134 update on Win 10.

But this same Win 10 machine only sees itself. It can't even see - using the file browser - the machine that can see it, even right after the Linux machine copied files from it.

And another thing. A Linux machine that is mostly off the net could not see any of the Win 10 machines. But it could see the Linux machines. I found this,

[SOLVED] Error connecting windows share (SMB, UFW kernel 4.8) - Linux Mint Forums

and applied the fix to the linux box mentioned at the end of this post. And voila. It can see the win 10 boxes. But this same win 10 system mentioned above cannot see it.

So do we know that Win 10 SMB is basically broken. Not only for Linux, but also for Win 10 itself?
Anybody know a fix that does not involve renaming all the computers? That is nonsense and I will carry thumb drives before I change all the names of my 10 computers. Win 10 will eventually make this work with the same computer names.

BTW, I have not "Joined any HOMEGROUPS" or whatever that bad idea was called now that it's out of the system. And all my machines are on the WORKGROUP network.

Thanks so much,
wg

 

Win 10 File Sharing Not working after 17134 update


Yep... Those services were part of it... Sigh... Discovery Publication was stopped. duh.

Also the SMB 1 client was off and things showed up, including other Windows 10 machines, when I turned on the SMB 1.0 client.
I thought SMB 1 was deprecated, but apparently not.
More checking to do, but things appear to be working a lot better now.

Here are some relevant screen shots for how to turn things on:

Fix File Sharing on Windows 10 after 17134 Update - Album on Imgur

Thanks,
wg

 

Win 10 File Sharing Not working after 17134 update


I have similar problems with my 4 computers:
3 of them are under W10-64 version 17134
the last one has not been update to 17134 yet (stil in 16xxx)
When I open Network with the file explorer, I see the icons of the other computers where I have shared directoiries and I also see the icon for my internet box.
However, on the 2 first computer I am only able to open my own icon and the box. The 3 other computers are seen but when I click on them I get an error message (Windows cannot access \\xxx error x8077035)
on the 3rd computer, in addition I can access the 4th computer an reciprocally.
I have done all what is suggested in this forum and other forums to solve this problem but nothing wotks.
I change the function do discover publication service ressources to automatic.
I tried to change the name of one computer (both name in system folder and network name in internet folder)
I set SMB1 to automatic (both client and server)
I tried to restart network connection
Nothing works.

Can you help me, please, since I cannot send any data from my development machine to my real-time machines.

Thank you in advance