First a bit of background:
In order to share files with my housemates at uni, I've set up a second user account (called NetworkUser) on my PC (Win7), and set security permissions so it can only access one drive on my computer.
Access to C drive is also permitted so everything works, but with my account in the users folder being blocked. D:/, with my personal stuff, is not viewable by NetworkUser, while E:/ is accessible.
With two accounts on my PC (Admin/me, and NetworkUser, both passworded appropriately), the idea is that I can give the NetworkUser account name and password to my flatmates who can then access over the network my shared files. I've gone about it this way so that other people in the building can't access these files, and so that my flatmates can contribute through read and write permissions, where applicable.
If I log into NetworkUser on my PC, D:/ is not accessible, and C:/Users/Kev is also not accessible, while E:/ is accessible. Which is exactly what I wanted. Permissions and security setting worked fine, it seems.
I've just set up the network drive on my flatmate's PC. Read/write permissions are fine, and the only thing viewable through Run>"\\nameofmyPC\", and logging in using NetworkUser, is the E:/ drive, which is good.
However, and this is where the issue is, typing "\\nameofmyPC\D$" into run and hitting enter takes you straight to the root of D:/, which NetworkUser does not have privileges to read/write/access in any way.
The same applies to "\\nameofmyPC\C$" and navigating to the C:/Users/Kev" - it lets you straight in.
Granted, I don't think anyone in my flat is technically minded enough to even figure out how to use run to access my files, and those outside of the flat don't stand a chance without the password for NetworkUser, but it still makes me uncomfortable.
So my questions:
1) Why are the permissions working when logging in using NetworkUser on my PC, but not when connecting to my PC from another PC, using the very same account?
2) How can I properly secure C:/Users/Kev and D:/ so that NetworkUser, when used to connect from another PC on the local network, can't view/access/change the contents of those two locations?
So far, google's not throwing up anything useful - just stuff I've already done that has worked locally, but not from another PC. Maybe my google-fu is weak
If anyone has any insights into this, I'd really appreciate hearing! Many thanks!
Kev
In order to share files with my housemates at uni, I've set up a second user account (called NetworkUser) on my PC (Win7), and set security permissions so it can only access one drive on my computer.
Access to C drive is also permitted so everything works, but with my account in the users folder being blocked. D:/, with my personal stuff, is not viewable by NetworkUser, while E:/ is accessible.
With two accounts on my PC (Admin/me, and NetworkUser, both passworded appropriately), the idea is that I can give the NetworkUser account name and password to my flatmates who can then access over the network my shared files. I've gone about it this way so that other people in the building can't access these files, and so that my flatmates can contribute through read and write permissions, where applicable.
If I log into NetworkUser on my PC, D:/ is not accessible, and C:/Users/Kev is also not accessible, while E:/ is accessible. Which is exactly what I wanted. Permissions and security setting worked fine, it seems.
I've just set up the network drive on my flatmate's PC. Read/write permissions are fine, and the only thing viewable through Run>"\\nameofmyPC\", and logging in using NetworkUser, is the E:/ drive, which is good.
However, and this is where the issue is, typing "\\nameofmyPC\D$" into run and hitting enter takes you straight to the root of D:/, which NetworkUser does not have privileges to read/write/access in any way.
The same applies to "\\nameofmyPC\C$" and navigating to the C:/Users/Kev" - it lets you straight in.
Granted, I don't think anyone in my flat is technically minded enough to even figure out how to use run to access my files, and those outside of the flat don't stand a chance without the password for NetworkUser, but it still makes me uncomfortable.
So my questions:
1) Why are the permissions working when logging in using NetworkUser on my PC, but not when connecting to my PC from another PC, using the very same account?
2) How can I properly secure C:/Users/Kev and D:/ so that NetworkUser, when used to connect from another PC on the local network, can't view/access/change the contents of those two locations?
So far, google's not throwing up anything useful - just stuff I've already done that has worked locally, but not from another PC. Maybe my google-fu is weak

If anyone has any insights into this, I'd really appreciate hearing! Many thanks!
Kev
Last edited: