Windows 10: Update 1709 -- cannot now access W10 shares from Non Windows devices

Hi there
I KNOW this must be a 1709 update -- I have several Windows machines with earlier releases than 1709 and they all work.

With 1709 my NON Windows devices cannot access Windows shares even though they see the computer and can ping it. Connecting via IP also doesn't work.

I read somewhere that Ms has now disabled SMB or SAMBA access from Non Windows devices --thanks Ms !!!! now half the planets devices won't work any more !!!

Why on earth does Ms do things like this --break perfectly good functioning systems --or at least give some sort of warning so people can look for alternatives.

I certainly don't want to manually mount a whole slew of CIF partitions on each android / linux / NAS device I'm using.

Anybody got this stuff working

I tried also accesssing via CIFS -- still not working

screenshot below





somebody mentioned something about re-install "certificate" bit I haven't got a clue what that means or how to do it.

Note Windows TO Windows is fine as is Window TO the android / Linux devices. It's the Android / linux devices TO Windows that's the problem.

I have a load of media files on a Windows share which I want my media server (KODI) on the non Windows device to stream. It's an amazon fire stick (the small one) so I can't locally attach the media files !!! - In any case the whole point is to stream over a network anyway.

Cheers
jimbo

:)

 

File sharing won't work after latest big update

It works now, the update was Windows 10 1709. Fixed with Windows 10 1709 Cannot Access SMB2 Share Guest Access - Techblog

 

Home Group Problems

This might be related to changes in networking with the Windows 10 1709 release. You should check your Public folder sharing settings in Windows 10. See some steps you can try to enable that:

https://appuals.com/fix-cannot-access-network-s...

 

Something odd is going on.

I cannot see C drive but can see others.

Oddly I can see public folders.

Cannot access C drive from android devices since upgraded to 16299 - Windows 10 Forums

MS have not stopped network access but something is not working. I get an error message from ES File Explorer PRO saying login failed when trying to access C drive which is silly as I have no password.

 

Just done more testing. If you set pc so it requires passwords for network access, it just refuses to accept username and password from popup menu.

I tried to cheat by symlinking a directory on c drive to a folder in public folders. That failed.

I created a second partition on C drive - I cannot access that but can access other physical drives.

So it seems you can now only access files on physical drive with OS if they are in public folder!

 

Hi there

still not working trying other drive D or even public folder with guest / anon login.

Going to abandon 1709 version of windows for any sort of Networking until they fix Networking (I think this will be the world's FIRST Y3K Project !!!!!)

Meanwhile re-formatting 8TB for XFS - Linux file system and attaching it to NAS server. NTFS is not so good on Linux if you can use a native file system.

The strange thing is Windows can access the Linux / Android files so why is it only working ONE WAY !!!!!.

My build BTW is 16299.64

My phone (Samsung S8) can't even SEE the 1709 computer --other Windows machines and non Windows devices -- all OK.

(Running W10 Pro x64 ENG (GB) on all windows machines).

Cheers
jimbo

 

Check this out

 

I also run 1709/16299.64 on Windows 10 Pro, but from Linux Mint 18 (3.0.7) I can still access documents on the Win 10 PC. For me nothing has changed following the latest update. In Windows Features I had previously selected SMB 1.0/CIFS and that is still the case.