Hot answers tagged network-share
When not using a domain, the LocalSystem account can access network resources only with anonymous credential. In other words, it will not present named credential to the remote samba server.
My personal recommendation would be to use NIC teaming, for a number of reasons. NIC teaming/boding will allow for link redundancy and/or load balancing, depending on which options you select and your hardware/OS choices. If you opt for a load-balanced configuration, traffic will be split across both links, effectively giving you a single, logical 2Gbps "...
To your original question: if you mount a filesystem "on top" of your current working directory, you will not see the contents of the mounted fs, nor will you be able to save content to that fs until you cd back to the parent directory and then enter the mounted fs again. When you write data, it consumes space on whatever filesystem it is written to. In ...
Your group policy is giving your users local admin rights to the server because the default domain policy applies to the server, unless you have made some other changes but it would appear you have not. Best practice - Leave the default polices alone (or at least don't add to them). Create a policy for groups of settings, so in this case you might make a ...
I figured it out. My problem was a missing special permission. The LIST groups need read extended attributes for ABE to work.
In WorkGroup mode all the local username of the remotes PC that connect to the server must be created locally on that server. (with same password off course) As when Explorer try to open the remote directory, it send the username/password, thus lead to the error you see. So if the account Bob with password Hello01 access the server, then Bob with password ...
I found the cause. This is because of EFS. If a user encrypt a file and if he does not have a roaming profile then a local profile is created on the server.
Only top voted, non community-wiki answers of a minimum length are eligible