New
#230
strange though as the Samba Firmware Version 2.12.127 says it supports SMB 2/3 and is set by default. However, this does not show until SMB 1.0 is enabled.
I do have a new ReadyNAS 422 and this works without SMB 1.0.
This at least proves my configuration.
Thanks for sharing...
In my case all the computers are smb2/3 compatible using "Get and Set" but if I disable smb1 I can't see my Network drive (even though) the system is OpenWRT smb3.6.25.
Reading at microsoft (if I understood it correctly) it is that Windows 10 are not supporting Linux based smb.
Any idea/comment?
No, I haven't given completely up on your suggestion. What I might do, is just use one of my other drives to setup another sys disk for a dual boot system, and do a clean install of 18312 on that disk. Do you have an iso of this build?
Also, yeah, the first thing I checked was connections and cables. Then temperatures. But you are right. sometimes problems do linger between builds if we are only upgrading. So it will be interesting to see how this new clean install works out. Thanks as always for helping me search for a solution. Always appreciated.
I made an ISO of 18312. If you or anyone else is interested, I've put it up on my OneDrive:
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
One question to the board before I setup another drive on my system to also have a windows 10 system partition. I have not setup a dual boot Win10 sys in quite a while. So considering I am using a completely different drive for each system disk, is there any worries about the boot manager getting corrupted or having any problems in recent builds? Do I need to take any particular precautions to preserve the boot manager software before loading another instance of Win10 Pro on another drive? Thanks in advance.
I dual boot mainline and Insiders builds, on the same physical drive, and haven't had much problem. If I were you, I'd make sure to have a Macrium rescue USB on hand. If you boot with that, under 'restore' is an option to 'fix Windows boot problems'. This has never failed to straighten things out for me.
If your new instance of Windows takes over the boot process, and you don't want that, you can always fix it in options at the boot screen.