Reply to thread

Message

<blockquote data-quote="Jean-Christophe" data-source="post: 1089466" data-attributes="member: 13248">Your answer was correct anyway. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />The Synology NAS is integrated in the Active Directory. I can use NAS ressources with my AD account. From the client point of view, the fact it is a Synology NAS instead of a Windows file server is not visible.What is strange is the fact I don't have to authenticate on the NAS using the domain name. I guess the Synology is smart enough to lookup in the AD if the username is not in it's local users database... I never noticed that before.My problem was I used to use DOMAIN\USER or user@domain or <a href="mailto:user@domain.tld">user@domain.tld</a> in the MPExtended config tool (all except DOMAIN\USER gave me a successful connection TEST using the test button but failed to acces de file).</blockquote>

[QUOTE="Jean-Christophe, post: 1089466, member: 13248"] Your answer was correct anyway. :-) The Synology NAS is integrated in the Active Directory. I can use NAS ressources with my AD account. From the client point of view, the fact it is a Synology NAS instead of a Windows file server is not visible. What is strange is the fact I don't have to authenticate on the NAS using the domain name. I guess the Synology is smart enough to lookup in the AD if the username is not in it's local users database... I never noticed that before. My problem was I used to use DOMAIN\USER or user@domain or [email]user@domain.tld[/email] in the MPExtended config tool (all except DOMAIN\USER gave me a successful connection TEST using the test button but failed to acces de file). [/QUOTE]

Verification