kenalker wrote:

For option one this means adding my credentials to machines that belong to other people, which would give them access to my home share, right (not good, if so)?...

But I can tell you with all certainly that I've been logging into Z: and saving files that end up owned by ken.users and logging into Y: and saving files that end up owned by guest.guest (all from one computer). Not sure how I managed for years or why it suddenly stopped (maybe that is different than what you are saying).

Whether it's "good" or not depends on what data you put in the home share. Personally I don't use the home shares at all. As far as the past goes, the rules here are changing. WannaCry is one reason, as it exposed the dangers of allowing open access to network shares.

That said, it is certainly possible to reset the file access rights on the public shares to allow both guest and "ken" to write to the share. You could start with using the reset control on the file access page, and see if that solves it.

Also, one way to "fake" multiple credentials is to use the NAS IP address when mapping Z and the NAS name when mapping Y. Windows treates the IP address and the hostname as two different devices. Then you can just create a NAS credential for ken on the machines that access the ken home share, and always use guest for public shares.

You could also create a second account, and use its credentials on the other PCs to access the public shares (avoiding guest, and allowing you to be selective on whom you let access the public shares).

Forum Discussion

C6250 Issues