If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Try to reset the password on the ADS (for administrator and one of the users you are testing with) and logon from the NAS XSR SMB server again.
Can you add a new user in the ADS (with access rights to the shares) and does this show up on the NAS server. If it does go to that system where the user resides and try to logon.
Check the Account Policies and Kerberos Policy because changing to PDC to ADS now uses Kerberos. Check to see if there is any possible deviation of the FQDN that happened recently with this change. Also was there any changes in Windows to the NAS storage with "\\computer_name" on the share change in the ACL rights in the Windows Server?

I have two rapidNAS Systems with open-e here. Both are connected to the LAN. Now I configured one with Windows (PDC) and the other with Windows (ADS). After this I created a new user "temp" in AD. This new user was listed on both NAS after a short time.

But it's the same for this new user: When use this "temp" user account to log on a client and try to open \\172.16.1.100 an error appears which tell me the ressource is not available. So I logged off and used "administrator" to login on the same client.
When using \\172.16.1.100 with the "administrator" account, all shares are listed fine and I have access!

Once again: user "temp" is also member of group "domänen-benutzer". Is this not enough to give access to member users?

By default new active directory users can only access specific hosts. The NAS devices were not in this list. Only administrator can access all devices. I changed the configuration for the users and now they can use the NAS devices also.

So it's an active directory configuration issue and not a problem with the NAS. Sorry.