A little networking permissions help please.

[Brendon 119]

I have been running my Emby on a WHS 2011 server for around 7yrs and it's been a dream but it was time to upgrade and expand to allow for more storage. Over easter i did a full rebuild into 2 rackmounted cases and everything is working fine except for write permissions on the network slave, i'll explain my current setup below and hopefully someone can steer me in the right direction.

So i now have 2 machines running Server 2016 Standard, the first we'll call the MASTER and the second the SLAVE.

• MASTER has emby server installed and running with 7 hard drives.
• SLAVE does not have emby server installed and running with 10 hard drives.
• BOTH machines run under Administrator (emby installed under admin on the master) with the same password on both
• Each machine also has a user account for me with admin rights which i only use to access the shared folders on my main desktop workhorse, this account has same user/password as the main desktop.

Everything runs smoothly and my family/friends can remotely access everything properly, all data restored as it should, the problem i am having is the MASTER cannot write nfo's or images to the SLAVE when adding new media or updating anything on the SLAVE drives.

 

I know this has to do with permissions but cannot work out how to grant the write access to the MASTER for the SLAVE drives could one of you networking genuises please steer me in the right direction, i know it would be something stupid i have missed but frankly my brain is burned out after 4 days of rebuilding everything lol

 

Cheers for any help,

Brendon

[pwhodges 2012]

Is write enabled for the admin user in the shares on Master?  This is additional to the settings on Slave.

 

Paul

[rbjtech 5284]

You don't mention if you are using AD/LDAP or WORKGROUP permissions but it's almost certainly a local NTFS or Share permission that is Read Only - as pwhodges has said above.    Just look at folder/share permissions, possibly inherited permissions somewhere.  ps - If you can 'see' the shares - the it's nothing to do with Networking - it's the next layer up - 'Access Control' that needs fixing.

Edited April 14, 2020 by rbjtech

[Brendon 119]

Thank you guys, solved the problem after some sleep and a clear minded approach.

 

Turns out Win Server 2016 needs the actual administrator account from the MASTER added to permissions on the SLAVE, apparently the administrators 'group' is not enough, had to add the actual Administrator account which is identical on both machines and bang, emby started writing to the drives

[rbjtech 5284]

Glad you got it working.

 

Just as a bit of 'best practice' - it's actually not a great idea to use 'Administrator' level access for these type of file shares - always try and use the minimum level of access you need via a 'service' account (ie a non-admin and locked to a specific task)

 

That way, if you get into trouble with viruses/ransomware or finger trouble (lol) then you (or the program) won't have the ability to do massive damage.

 

Something to think about.

Edited April 16, 2020 by rbjtech