Setting up shared folder on Windows server 2012 R2

[Blackterror25]

So the shared folder is on a Windows server 2012 R2 and in my home network I've got a windows 7 ultimate, windows 8.1 laptop and windows Vista home premium.

 

I want certain folders to have full read/write permission by these PC's but only read permission for others (for instance if guests connect to the network and want to get something from these folders)

Then I want certain folders that only have read/write for these PC's but no permission for others.

Any thought on how I could go about and configure this, I'm guessing I need to put the IP's in some sort of group and add the correct permissions to them but where can I confugre these groups?
 

Thanks for the Help

 

 

***EDIT***

 

I don't wan't to use user accounts an log in every time I boot my PC. It should use the IP or something like that.

[SMURG]

Well in order to use the IPs you'd have to configure the router to always give those PCs those IP addresses, which can be done but might cause issues for the 'guests' you speak of if you can't also set it so that other connections are randomly assigned.

Surely with the user accounts you just tick "remember my credentials" and then whenever you access the shared folder it logs you in?

[Blackterror25]

Well the problem with that is that that vista machine is my dad's PC and teaching him to work with excel has already been a big pain and I don't think I'm ready to deal with the login problems.

[SMURG]

Well the problem with that is that that vista machine is my dad's PC and teaching him to work with excel has already been a big pain and I don't think I'm ready to deal with the login problems.

Log him in yourself the first time, click remember credentials and it should make it so he never has to worry about it though?

[Blackterror25]

Log him in yourself the first time, click remember credentials and it should make it so he never has to worry about it though?

 

Let me just say it never stops to amaze me how he manages to screw some things up.

Somehow once managed to get his boot drive out of the start-up list.

[SMURG]

Let me just say it never stops to amaze me how he manages to screw some things up.

Somehow once managed to get his boot drive out of the start-up list.

Right O_o

Well, best of luck then lol. My suggestion would be to use the accounts system though. Can't really see a way in which he could properly mess that up.

[r3bify]

Are you using the server to run Active Directory? Because that would make your life so much easier. Just make accounts for anyone who is going to be connected to your network, have their machines join your domain, and then you can segregate who has what permissions that way. And it will require nothing from end users expect using the account you made to sign in on their machines.

 

If you're not running AD and would like to, I'd be glad you help you get everything set up.

[JohnnyP]

Using AD will not work unless you have pro versions on all the pcs. Create local accounts on the server and then map a network drive. Have it save the credentials.

[r3bify]

hmm didn't read the end of the first line. Vista HP, and then I'm assuming the Win8.1 laptop is core?

Could always spend a day upgrading. 

Local accounts does seem to be the best way, otherwise. You can set a local account on the server with matching credentials as the local machines to cause less grief.

Wish you could use AD, though. It would make your life easier in the long run.

[Blackterror25]

Ok, I saw that as well after posting this thread and might just add a different shared folder that goes to his PC until my dad needs a new one (avoid changing stuff and having him re-learn stuff un neccesary) and just use accounts for my PC and laptop.

But my question now is will I run into any problems when I connect my laptop to a different network?
Of course I won't be able to access that NAS but will it cause any other issues?

[r3bify]

If you're mapping a network drive, when you move networks, the drive will just be unable to connect. It shouldn't cause any other issues.

[Blackterror25]

If you're mapping a network drive, when you move networks, the drive will just be unable to connect. It shouldn't cause any other issues.

Yes but if the laptop belongs in a active directory domain group where it log's in to?

if it does I just remove it, it doesn't really matter if I couldn't write to those folder, as long as I could read from them.

[JohnnyP]

It keeps a local copy of the password so when it can not reach the server it will verify against the copy.

[JohnnyP]

When it can't connect to the mapped drive you just get a notification that it couldn't connect.

[r3bify]

Yes but if the laptop belongs in a active directory domain group where it log's in to?

if it does I just remove it, it doesn't really matter if I couldn't write to those folder, as long as I could read from them.

Are you asking what happens when your AD-joined laptop connects to a different network and can't contact the domain?

If yes, then it depends on how you log in. If your credentials are on the server, then..

It keeps a local copy of the password so when it can not reach the server it will verify against the copy.

^This

 

If you just join your laptop to the domain, and use your local account to sign in, then nothing will be different.

If that isn't what you were asking, then sorry for the misunderstanding. 

[Blackterror25]

Are you asking what happens when your AD-joined laptop connects to a different network and can't contact the domain?

If yes, then it depends on how you log in. If your credentials are on the server, then..

^This

 

If you just join your laptop to the domain, and use your local account to sign in, then nothing will be different.

If that isn't what you were asking, then sorry for the misunderstanding. 

 

I'll probably won't add the laptop to the AD just to avoid any issues later down the line when I really need them to work.

As long as I could read the files that should be fine.

I'm starting to think this al isn't worth the effort. I'd just want to configure this a little more to avoid when I have friends over for a lanparty or something (which doesn't really happen that often) I won't have to worry about the deleting all my series and other stuff.

[r3bify]

It's obviously up to you. The way I have my setup at home, I can connect my laptop to my domain and I just use my local credentials (no extra accounts on the server).

You can leave the domain whenever, and just use the network normally. Maybe that's what you want to do?

[Blackterror25]

I fixed it, I went to advanced sharing and added a new share name where everyone just have read permissions, if I ever want anyone to just read the folder I just have to give them the second share name for that folder.

[r3bify]

That's what I was going to suggest from the beginning, but you said that you wanted permission based sharing. Glad you've got everything working (more or less) how you want it!

[macpro622776]

Are you using the server to run Active Directory? Because that would make your life so much easier. Just make accounts for anyone who is going to be connected to your network, have their machines join your domain, and then you can segregate who has what permissions that way. And it will require nothing from end users expect using the account you made to sign in on their machines.

 

If you're not running AD and would like to, I'd be glad you help you get everything set up.

 

Using AD will not work unless you have pro versions on all the pcs. Create local accounts on the server and then map a network drive. Have it save the credentials.

 

Using AD would work as you could just authenticate as firstname@lastname, then your password, and login, if you set the domain name up as the surname of the household.

 

Non-pro versions on the PC's can still login using an AD login, they just can't join the domain. You don't have to join the domain to authenticate as a domain user.

[peaking duck]

sounds like you need to set up a workgroup

give all users a username and password.

recreate these same accounts on every machine each user wants to use and also on the server as local accounts

if each user only ever uses one pc, create the user account anyway. there are ways to stop the computers from prompting for a password.

as a user tries to access a shared resource, the server with the resource is authenticate the logged on user on that machine against its authorised list of users.

if match exists, permission will be granted to whatever level you specified for the resource

 

all this is better handled with AD, but would cause administrative overhead and complexity that you dont need

 

dont forget about Windows Licensing; CALs