How to reliably share files and folders between Windows 10 PCs

You can have shortcuts created for sharing.


Map Network Drive no results when Browse selected

hi there

@MacNala

sometimes the login needs to be \\servername\user rather than just user.

If you don't want to plug in a USB disk to a router - the most reliable way bar none is to use a Linux NAS server -- any el-cheapo pc will work as a NAS server for Linux -- attach the disk, start samba up and then all your Windows machines should be able to connect without problem to the shared drive(s).

I know this is a Windows Forum - but Networking on Windows particularly for Home networks is so random that IMO this solution is the best one.

Try as a VM first to get experience -- attach the disk(s) to be shared to the VM and then try accessing from Windows.

Another probably not considered way is to use one of the free 180 day evaluation Windows server editions.

Windows server editions also work very well especially Windows 2019 and 2022 servers but they are hideously expensive for domestic consumers - unless you are lucky enough to get them as a "learning tool" from your work place.

You can download 180 day free evaluation which is really good -. At the end of 180 days just re-install again from the ISO -- if you are just wanting this as a reliable server to share files - time to install on Home computer is minimal. Uses less resources than W10 and you can also run in a VM if you want. - Install the standard desktop editions though.

You need to do about 6 things after installing to make them more "Friendly" as a workstation / desktop OS - but really simple and no special Windows or other Geekery wizardry required. I can post instructions on how to do that anyway.

Can post steps if required. I recommend W2022 rather than W2019 as its more up to date and more compatible with W10/W11.

100% legal and these are already pre-activated properly for the 180 day period .

Cheers
jimbo

[QUOTE=dalchina;2448833]Please confirm you do NOT have SMB1 enabled.

I have confirmed that my NAS (a Drobo 5N2) does not use SMB1, but SMB2 or SMB3 and is working correctly so I assume I am not using SMB1. I do not remember switching it off but I think recent MS updates have done that.

- - - Updated - - -

[QUOTE=jimbo45;2449129]hi there

@MacNala

sometimes the login needs to be \\servername\user rather than just user.

I am still not sure about windows credentials. When you say \\servername\user are talking about the remote machine name and user or the local machine name and user.

Thanks for the thoughts .

[QUOTE=MacNala;2449287][QUOTE=dalchina;2448833]Please confirm you do NOT have SMB1 enabled.

I have confirmed that my NAS (a Drobo 5N2) does not use SMB1, but SMB2 or SMB3 and is working correctly so I assume I am not using SMB1. I do not remember switching it off but I think recent MS updates have done that.

- - - Updated - - -

jimbo45 said:

hi there

@MacNala

sometimes the login needs to be \\servername\user rather than just user.

I am still not sure about windows credentials. When you say \\servername\user are talking about the remote machine name and user or the local machine name and user.

Thanks for the thoughts .

Can't remember exactly but try it both ways around.

Incidentally install Filezilla client (Free) on both the NAS and your Windows machines. At least that way it will be able to see all the shared directories. For file transfer -- simple - but if you want to transfer files FROM Windows TO NAS then ensure openssh-server is installed on the windows machines via add optional feature and enable the service via services to start automatically.

Cheers
jimbo

I have 3 win10 machines and a mac. I could not get them to connect reliably to each other. NAS is definitely the way to go. I would advise against WD MBL as I found they use hardward encryption on the drives making data recovery difficult. Go with Synology, QNAP or if you want to build one from scratch FreeNAS.

I have solved this problem by creating a local account as an administrator on all of the target PCs involved. I then changed the permissions of the folders/drives to be accessed to allow full control exclusively to the local account. Then I created Windows credentials for each of the target machines on the source machines. I ensured that passwords were required for the file sharing.
I changed the registry on the target machines to put the local account in a UserLlist in the SpecialAccounts key of the WinLogon in the WindowsNT/currentversion key in the HKLM/Software/Microsoft section. This last step removes the local account from the logon screen at startup. If you have to change any of the settings you need to a least restart the PCs in the link you are trying to establish. I am not sure if in the process of setting up a local account you have to logon to the account, but I did so.

I am still trying to find out why Windows does not publish the devices/resources at start up time despite the startup type being set to Automatic, if anyone knows why and how to fix it I would appreciate the data. I am using a Powershell administrator command Restart-Service FDResPub to force Windows to publish data which populates the network section of the file explorer.