After some arguing with the ReadyNAS, I was finally able to get it to join the domain. Under users and groups in the readyNAS I am able to see my AD users and groups. But, it seems like those user accounts are now "local" to the nas.
When a user logs in to a windows computer with their domain credentials they have to re-authenticate to the ReadyNAS share they want to access. Windows by default will try their domain\username credentials that they are logged in as. In order for me to get a share open I have to try to authenticate to the ReadyNAS without the domain\ in front of the username. This makes for a problem when trying to mount user home directories or shares via login script since they are essentially two different accounts.
Yea, I know that and like I said its my next project.
I had a user back up their entire 3TB usb drive to my existing NAS which doesn't have nearly that space so I was hoping I could get moved to the ReadyNAS first then upgrade Windows / Active Directory.
Are there compatiblility issues with Windows 2003?
What is the reason for the double authentication issue?
The authentication is working, but users have to remove the domain name when they are prompted for authentication in order to connect since they technically aren't authenticating against the domain, they are authenticating against the local user database (which was imported to the ReadyNAS).
I'm really hoping this isn't the way these actually work, or I'll be doing FreeNAS on a VM via NFS for proper AD authentication.
