Reply to thread

Message

<blockquote data-quote="CyberSimian" data-source="post: 1305210" data-attributes="member: 141969">I don't understand the security implications of different setups, but maybe try the following:<ul>
<li data-xf-list-type="ul">Define userids with logon passwords for each system (clients and server).</li>
<li data-xf-list-type="ul">Ensure that each client that is going to connect to the server has the same userid defined on the server, with the same password. The clients don't need to have the same userids as each other.</li>
</ul>The reason that I am suggesting this is based on an experience that I had with my Windows 7 HTPC. I resisted defining a logon password for the HTPC for several years, but my laptop could never access the HTPC, even though the laptop could see the HTPC on the network. I eventually got fed up having to use a USB memory stick to move files between the two systems, and defined a logon password for the HTPC, after which the laptop connected immediately. In the Windows settings, you can choose not to require a password when waking from sleep or hibernation. So the logon password is only required when you reboot the system. Will this make a difference to the problems that you are having? I don't know.No, that is not correct. With the correct authorisations, clients can delete files from the server.-- from CyberSimian in the UK</blockquote>

[QUOTE="CyberSimian, post: 1305210, member: 141969"] I don't understand the security implications of different setups, but maybe try the following: [LIST] [*]Define userids with logon passwords for each system (clients and server). [*]Ensure that each client that is going to connect to the server has the same userid defined on the server, with the same password. The clients don't need to have the same userids as each other. [/LIST] The reason that I am suggesting this is based on an experience that I had with my Windows 7 HTPC. I resisted defining a logon password for the HTPC for several years, but my laptop could never access the HTPC, even though the laptop could see the HTPC on the network. I eventually got fed up having to use a USB memory stick to move files between the two systems, and defined a logon password for the HTPC, after which the laptop connected immediately. In the Windows settings, you can choose [b]not[/b] to require a password when waking from sleep or hibernation. So the logon password is only required when you reboot the system. Will this make a difference to the problems that you are having? I don't know. No, that is not correct. With the correct authorisations, clients can delete files from the server. -- from CyberSimian in the UK [/QUOTE]

Verification