drzoidberg33
Cadet
- Joined
- Aug 15, 2013
- Messages
- 6
Hi All,
I have had a very rough week. Bought a new NAS box, installed FreeNAS 9.1 on it and all was well. Until that is I tried activating Directory Services on the FreeNAS box to connect to our local Windows Server box.
I followed this guide: http://doc.freenas.org/index.php/Directory_Services
After many attempts and setting changes to try to get it to work (kept on failing at "active directory: ad join domain: failed") I discovered that I could no longer log in to my Windows box due to some trust issues. At this time, not realising it was the FreeNAS box causing the issue, I Googled everything to try and sort out the issues with no success. I actually managed to basically destroy the box completely after many attempts to try and recover it.
So thinking the issue was related to something else (we had just had issues the previous day with low disk space and Exchange errors), I restored from a backup image of Windows Server and we were back up. Now still unaware that the FreeNAS integration to AD caused the previous issue (I mean really, how could it?) I tried again to get it working, this time fully managing to break the DNS server on the Windows box and thus subsequently everything reliant on this (including Exchange, again!).
Only after getting errors for the second time after attempting this did I realise it must have something to do with the FreeNAS install as I found a few similar reports on my Google searches on the DNS issue.
TL;DR version: I completely managed to destroy two Windows Server 2008 R2 AD installs while attempting to activate Directory Services on FreeNAS.
Does anyone have a better step by step guide on how to do this as I really don't feel like going through for a third time. Also, there should be some kind of warning on the guide page I used mentioning that "incorrect" setups could cause issues with your Active Directory.
If I cannot get this working, is there another similar opensource NAS solution with AD integration?
Thanks in advance.
I have had a very rough week. Bought a new NAS box, installed FreeNAS 9.1 on it and all was well. Until that is I tried activating Directory Services on the FreeNAS box to connect to our local Windows Server box.
I followed this guide: http://doc.freenas.org/index.php/Directory_Services
After many attempts and setting changes to try to get it to work (kept on failing at "active directory: ad join domain: failed") I discovered that I could no longer log in to my Windows box due to some trust issues. At this time, not realising it was the FreeNAS box causing the issue, I Googled everything to try and sort out the issues with no success. I actually managed to basically destroy the box completely after many attempts to try and recover it.
So thinking the issue was related to something else (we had just had issues the previous day with low disk space and Exchange errors), I restored from a backup image of Windows Server and we were back up. Now still unaware that the FreeNAS integration to AD caused the previous issue (I mean really, how could it?) I tried again to get it working, this time fully managing to break the DNS server on the Windows box and thus subsequently everything reliant on this (including Exchange, again!).
Only after getting errors for the second time after attempting this did I realise it must have something to do with the FreeNAS install as I found a few similar reports on my Google searches on the DNS issue.
TL;DR version: I completely managed to destroy two Windows Server 2008 R2 AD installs while attempting to activate Directory Services on FreeNAS.
Does anyone have a better step by step guide on how to do this as I really don't feel like going through for a third time. Also, there should be some kind of warning on the guide page I used mentioning that "incorrect" setups could cause issues with your Active Directory.
If I cannot get this working, is there another similar opensource NAS solution with AD integration?
Thanks in advance.