Windows 7 share folder with specific PC on network
I have small office network having 5 PCs running Windows 7 ultimate edition. All PCs are on same work-group named "WGXYZ" and connected to same home-group created by PC1.
PC1 has printer which is shared and used by all computers thus all PCs are on same home-group.
I'm looking to share a folder on PC3 with read/write permission for PC4 without password protection as the file store will be used by PC4 & PC3 simultaneously however no other PC should have access to the said folder.
This is supposed to be simple stuff and I can't determine that it is possible in windows 7 environment.
I have tried to find answer but almost all threads I've seem lead to dead end so I'm open to alternates to accomplish this task.
Thanks!
windows-7 windows networking file-transfer file-permissions
asked Jan 2 at 9:26
LEOLEO
135
add a comment |
I have small office network having 5 PCs running Windows 7 ultimate edition. All PCs are on same work-group named "WGXYZ" and connected to same home-group created by PC1.
PC1 has printer which is shared and used by all computers thus all PCs are on same home-group.
I'm looking to share a folder on PC3 with read/write permission for PC4 without password protection as the file store will be used by PC4 & PC3 simultaneously however no other PC should have access to the said folder.
This is supposed to be simple stuff and I can't determine that it is possible in windows 7 environment.
I have tried to find answer but almost all threads I've seem lead to dead end so I'm open to alternates to accomplish this task.
Thanks!
windows-7 windows networking file-transfer file-permissions
asked Jan 2 at 9:26
LEOLEO
135
File sharing and permission is set for the user, not for the computer. We can try to allow only the IP address of PC4 to access the shared port of PC3 through the firewall. Windows shares use these ports, such as 135, 136, 137, 138, 139, 445.
– Daisy Zhou
Jan 2 at 11:54
@DaisyZhou Could you please elaborate
– LEO
Jan 2 at 11:58
add a comment |
I have small office network having 5 PCs running Windows 7 ultimate edition. All PCs are on same work-group named "WGXYZ" and connected to same home-group created by PC1.
PC1 has printer which is shared and used by all computers thus all PCs are on same home-group.
I'm looking to share a folder on PC3 with read/write permission for PC4 without password protection as the file store will be used by PC4 & PC3 simultaneously however no other PC should have access to the said folder.
This is supposed to be simple stuff and I can't determine that it is possible in windows 7 environment.
I have tried to find answer but almost all threads I've seem lead to dead end so I'm open to alternates to accomplish this task.
Thanks!
windows-7 windows networking file-transfer file-permissions
asked Jan 2 at 9:26
LEOLEO
135
I have small office network having 5 PCs running Windows 7 ultimate edition. All PCs are on same work-group named "WGXYZ" and connected to same home-group created by PC1.
PC1 has printer which is shared and used by all computers thus all PCs are on same home-group.
I'm looking to share a folder on PC3 with read/write permission for PC4 without password protection as the file store will be used by PC4 & PC3 simultaneously however no other PC should have access to the said folder.
This is supposed to be simple stuff and I can't determine that it is possible in windows 7 environment.
I have tried to find answer but almost all threads I've seem lead to dead end so I'm open to alternates to accomplish this task.
Thanks!
windows-7 windows networking file-transfer file-permissions
windows-7 windows networking file-transfer file-permissions
asked Jan 2 at 9:26
LEOLEO
135
asked Jan 2 at 9:26
LEOLEO
135
asked Jan 2 at 9:26
LEOLEO
135
asked Jan 2 at 9:26
LEOLEO
135
asked Jan 2 at 9:26
LEOLEO
135
135
File sharing and permission is set for the user, not for the computer. We can try to allow only the IP address of PC4 to access the shared port of PC3 through the firewall. Windows shares use these ports, such as 135, 136, 137, 138, 139, 445.
– Daisy Zhou
Jan 2 at 11:54
@DaisyZhou Could you please elaborate
– LEO
Jan 2 at 11:58
add a comment |
File sharing and permission is set for the user, not for the computer. We can try to allow only the IP address of PC4 to access the shared port of PC3 through the firewall. Windows shares use these ports, such as 135, 136, 137, 138, 139, 445.
– Daisy Zhou
Jan 2 at 11:54
@DaisyZhou Could you please elaborate
– LEO
Jan 2 at 11:58
File sharing and permission is set for the user, not for the computer. We can try to allow only the IP address of PC4 to access the shared port of PC3 through the firewall. Windows shares use these ports, such as 135, 136, 137, 138, 139, 445.
– Daisy Zhou
Jan 2 at 11:54
File sharing and permission is set for the user, not for the computer. We can try to allow only the IP address of PC4 to access the shared port of PC3 through the firewall. Windows shares use these ports, such as 135, 136, 137, 138, 139, 445.
– Daisy Zhou
Jan 2 at 11:54
@DaisyZhou Could you please elaborate
– LEO
Jan 2 at 11:58
@DaisyZhou Could you please elaborate
– LEO
Jan 2 at 11:58
add a comment |
1 Answer
1
active
oldest
votes
The proper solution is to use Active Directory to grant PC4 permission to use this share so that anybody who logs in to PC4 can use it. This is the way Microsoft intends to support this type of security. You probably don't have have active directory. It was correctly pointed out that while you can give the permissions of a folder to a computer, you cannot authenticate as a computer over the network; you must authenticate as a user. Therefore this is pointless.
In lieu of this,
You should set up a faceless user account on PC3, set the folder permissions to allow this user to R/W, deny 'Everyone', and direct people using PC4 to use these credentials when prompted to login to the shared folder. Regrettably, this requires a password.
answered Jan 2 at 23:04
AndyAndy
33114
1
This does not sound right even for AD. As far as I know, if the SMB client authenticates as a user account, it only gets the permissions assigned to that user account – the machine account is not involved in the process at all. (It is only used for connections made by system services where there's no user.)
– grawity
Jan 2 at 23:09
You are correct, my mistake.
– Andy
Jan 2 at 23:16
@Andy faceless user account is services account? plz explain steps
– LEO
Jan 3 at 10:55
A faceless account is a just a normal user account. Faceless implies that the name on the account isn't a person. For example, my windows account is 'andy', but I might use a faceless account 'share_user' on a shared machine. Just create a new unprivileged user in windows and grant the user access to any needed shares.
– Andy
Jan 3 at 17:48
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1389720%2fwindows-7-share-folder-with-specific-pc-on-network%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The proper solution is to use Active Directory to grant PC4 permission to use this share so that anybody who logs in to PC4 can use it. This is the way Microsoft intends to support this type of security. You probably don't have have active directory. It was correctly pointed out that while you can give the permissions of a folder to a computer, you cannot authenticate as a computer over the network; you must authenticate as a user. Therefore this is pointless.
In lieu of this,
You should set up a faceless user account on PC3, set the folder permissions to allow this user to R/W, deny 'Everyone', and direct people using PC4 to use these credentials when prompted to login to the shared folder. Regrettably, this requires a password.
answered Jan 2 at 23:04
AndyAndy
33114
1
This does not sound right even for AD. As far as I know, if the SMB client authenticates as a user account, it only gets the permissions assigned to that user account – the machine account is not involved in the process at all. (It is only used for connections made by system services where there's no user.)
– grawity
Jan 2 at 23:09
You are correct, my mistake.
– Andy
Jan 2 at 23:16
@Andy faceless user account is services account? plz explain steps
– LEO
Jan 3 at 10:55
A faceless account is a just a normal user account. Faceless implies that the name on the account isn't a person. For example, my windows account is 'andy', but I might use a faceless account 'share_user' on a shared machine. Just create a new unprivileged user in windows and grant the user access to any needed shares.
– Andy
Jan 3 at 17:48
add a comment |
The proper solution is to use Active Directory to grant PC4 permission to use this share so that anybody who logs in to PC4 can use it. This is the way Microsoft intends to support this type of security. You probably don't have have active directory. It was correctly pointed out that while you can give the permissions of a folder to a computer, you cannot authenticate as a computer over the network; you must authenticate as a user. Therefore this is pointless.
In lieu of this,
You should set up a faceless user account on PC3, set the folder permissions to allow this user to R/W, deny 'Everyone', and direct people using PC4 to use these credentials when prompted to login to the shared folder. Regrettably, this requires a password.
answered Jan 2 at 23:04
AndyAndy
33114
1
This does not sound right even for AD. As far as I know, if the SMB client authenticates as a user account, it only gets the permissions assigned to that user account – the machine account is not involved in the process at all. (It is only used for connections made by system services where there's no user.)
– grawity
Jan 2 at 23:09
You are correct, my mistake.
– Andy
Jan 2 at 23:16
@Andy faceless user account is services account? plz explain steps
– LEO
Jan 3 at 10:55
A faceless account is a just a normal user account. Faceless implies that the name on the account isn't a person. For example, my windows account is 'andy', but I might use a faceless account 'share_user' on a shared machine. Just create a new unprivileged user in windows and grant the user access to any needed shares.
– Andy
Jan 3 at 17:48
add a comment |
The proper solution is to use Active Directory to grant PC4 permission to use this share so that anybody who logs in to PC4 can use it. This is the way Microsoft intends to support this type of security. You probably don't have have active directory. It was correctly pointed out that while you can give the permissions of a folder to a computer, you cannot authenticate as a computer over the network; you must authenticate as a user. Therefore this is pointless.
In lieu of this,
You should set up a faceless user account on PC3, set the folder permissions to allow this user to R/W, deny 'Everyone', and direct people using PC4 to use these credentials when prompted to login to the shared folder. Regrettably, this requires a password.
answered Jan 2 at 23:04
AndyAndy
33114
The proper solution is to use Active Directory to grant PC4 permission to use this share so that anybody who logs in to PC4 can use it. This is the way Microsoft intends to support this type of security. You probably don't have have active directory. It was correctly pointed out that while you can give the permissions of a folder to a computer, you cannot authenticate as a computer over the network; you must authenticate as a user. Therefore this is pointless.
In lieu of this,
You should set up a faceless user account on PC3, set the folder permissions to allow this user to R/W, deny 'Everyone', and direct people using PC4 to use these credentials when prompted to login to the shared folder. Regrettably, this requires a password.
answered Jan 2 at 23:04
AndyAndy
33114
edited Jan 2 at 23:16
answered Jan 2 at 23:04
AndyAndy
33114
answered Jan 2 at 23:04
AndyAndy
33114
answered Jan 2 at 23:04
AndyAndy
33114
33114
1
This does not sound right even for AD. As far as I know, if the SMB client authenticates as a user account, it only gets the permissions assigned to that user account – the machine account is not involved in the process at all. (It is only used for connections made by system services where there's no user.)
– grawity
Jan 2 at 23:09
You are correct, my mistake.
– Andy
Jan 2 at 23:16
@Andy faceless user account is services account? plz explain steps
– LEO
Jan 3 at 10:55
A faceless account is a just a normal user account. Faceless implies that the name on the account isn't a person. For example, my windows account is 'andy', but I might use a faceless account 'share_user' on a shared machine. Just create a new unprivileged user in windows and grant the user access to any needed shares.
– Andy
Jan 3 at 17:48
add a comment |
1
This does not sound right even for AD. As far as I know, if the SMB client authenticates as a user account, it only gets the permissions assigned to that user account – the machine account is not involved in the process at all. (It is only used for connections made by system services where there's no user.)
– grawity
Jan 2 at 23:09
You are correct, my mistake.
– Andy
Jan 2 at 23:16
@Andy faceless user account is services account? plz explain steps
– LEO
Jan 3 at 10:55
A faceless account is a just a normal user account. Faceless implies that the name on the account isn't a person. For example, my windows account is 'andy', but I might use a faceless account 'share_user' on a shared machine. Just create a new unprivileged user in windows and grant the user access to any needed shares.
– Andy
Jan 3 at 17:48
1
1
This does not sound right even for AD. As far as I know, if the SMB client authenticates as a user account, it only gets the permissions assigned to that user account – the machine account is not involved in the process at all. (It is only used for connections made by system services where there's no user.)
– grawity
Jan 2 at 23:09
This does not sound right even for AD. As far as I know, if the SMB client authenticates as a user account, it only gets the permissions assigned to that user account – the machine account is not involved in the process at all. (It is only used for connections made by system services where there's no user.)
– grawity
Jan 2 at 23:09
You are correct, my mistake.
– Andy
Jan 2 at 23:16
You are correct, my mistake.
– Andy
Jan 2 at 23:16
@Andy faceless user account is services account? plz explain steps
– LEO
Jan 3 at 10:55
@Andy faceless user account is services account? plz explain steps
– LEO
Jan 3 at 10:55
A faceless account is a just a normal user account. Faceless implies that the name on the account isn't a person. For example, my windows account is 'andy', but I might use a faceless account 'share_user' on a shared machine. Just create a new unprivileged user in windows and grant the user access to any needed shares.
– Andy
Jan 3 at 17:48
A faceless account is a just a normal user account. Faceless implies that the name on the account isn't a person. For example, my windows account is 'andy', but I might use a faceless account 'share_user' on a shared machine. Just create a new unprivileged user in windows and grant the user access to any needed shares.
– Andy
Jan 3 at 17:48
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1389720%2fwindows-7-share-folder-with-specific-pc-on-network%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
File sharing and permission is set for the user, not for the computer. We can try to allow only the IP address of PC4 to access the shared port of PC3 through the firewall. Windows shares use these ports, such as 135, 136, 137, 138, 139, 445.
– Daisy Zhou
Jan 2 at 11:54
@DaisyZhou Could you please elaborate
– LEO
Jan 2 at 11:58