LostInIgnorance
Dabbler
- Joined
- Jul 22, 2012
- Messages
- 25
I am currently running a 2008 r2 server with freenas 9.1.1 x64. I took the liberty to backup my settings on both machines before trying this ;)
The FreeNAS box is nothing special. an old server chassis I received from a friend who sells backup equipment. It is a Supermicro board and 12 bay (8bays populated) chassis with 8GB ram, a Intel Pentium Dual CPU E2180 @ 2.00GHz, and a sata RAID card (RAID 5 on 2TB drives). Nothing really special. It is joined to the DC via the AD integration. DC is running virtualized on a different server physical server.
I am stating here, everything in the above configuration is running fine. No issues to speak of.
I decided to try out the new 9.2 on a gui upgrade. Update went well, no errors. Took a bit longer to boot, but that was expected. It first asked me to set up the root password. Set that up. Then tried accessing the server via network discover. No server exists. Try the manual server name. Can't find it.
At this point I am thinking its just something simple, the AD integration service didn't start. Sure enough, it wasn't. Tried starting it. "Cannot start service." Looked at the time and resynced just to be safe. Pinged the dns entry of my server. Everything I am doing is showing no errors. Tried flushing from the DC with netdom and a kdestroy on the NAS thinking something was out of sync. Still can't get the service to start after multiple reboots. I was pretty much getting the same errors as described in this thread. It was pretty much giving me errors like I never was joined. Messed around with the tests described in the documentation. It was showing that no users were on the system. Tried resyncing from the web gui (settings > advanced > rebuild ldap\ad cache). Could not get it to sync what-so-ever.
Decided to tackle it the next day. Didn't change anything on the DC. Downloaded an ISO of 9.1.1 x64. Reinstalled it on the NAS box. Recovered from the backup I took of the config. BAM, back up and running.
What changed or has changed in the handling of AD on 9.2?
The FreeNAS box is nothing special. an old server chassis I received from a friend who sells backup equipment. It is a Supermicro board and 12 bay (8bays populated) chassis with 8GB ram, a Intel Pentium Dual CPU E2180 @ 2.00GHz, and a sata RAID card (RAID 5 on 2TB drives). Nothing really special. It is joined to the DC via the AD integration. DC is running virtualized on a different server physical server.
I am stating here, everything in the above configuration is running fine. No issues to speak of.
I decided to try out the new 9.2 on a gui upgrade. Update went well, no errors. Took a bit longer to boot, but that was expected. It first asked me to set up the root password. Set that up. Then tried accessing the server via network discover. No server exists. Try the manual server name. Can't find it.
At this point I am thinking its just something simple, the AD integration service didn't start. Sure enough, it wasn't. Tried starting it. "Cannot start service." Looked at the time and resynced just to be safe. Pinged the dns entry of my server. Everything I am doing is showing no errors. Tried flushing from the DC with netdom and a kdestroy on the NAS thinking something was out of sync. Still can't get the service to start after multiple reboots. I was pretty much getting the same errors as described in this thread. It was pretty much giving me errors like I never was joined. Messed around with the tests described in the documentation. It was showing that no users were on the system. Tried resyncing from the web gui (settings > advanced > rebuild ldap\ad cache). Could not get it to sync what-so-ever.
Decided to tackle it the next day. Didn't change anything on the DC. Downloaded an ISO of 9.1.1 x64. Reinstalled it on the NAS box. Recovered from the backup I took of the config. BAM, back up and running.
What changed or has changed in the handling of AD on 9.2?