While using FreeNAS as a DC, my domain account broke.

[TremorAcePV]

Vague title, I know.

Basically, after upgrading my FreeNAS system's hardware, I needed to reinstall the OS fresh. This meant I had to re-add my computer to the Domain. Well after I did this, my domain account continued to work fine.

Then I needed to do it again, so I did. However, after doing it again, my domain account won't work.

That's the TL;DR version. The detailed version is here:

Show

1. Upgrade to 9.1.5 from 9.1.2.1
2. Upgrade FreeNAS' hardware
3. Plugins stop working (Treemenu missing issue), based on the console, it appears to be looking for the old NIC.
4. Reinstall FreeNAS 9.1.5 on the USB drive, leave the storage discs alone.
5. Setup DC functionality of FreeNAS as well as importing volumes and installing plugins. Remove Desktop PC from the domain. Add it back to the Domain.
   
   Note: The DC is always set to 2008 R2 functionality.
6. Plugins still won't work after reinstalling them. Still getting the treemenu missing issue.
   
   I figure it has something to do with the config files in the Jails and/or the system dataset pool.
7. Reinstall FreeNAS 9.1.5 again, wipe storage discs after moving the data.
8. Setup DC functionality again, configure all other usual settings in FreeNAS. Remove Desktop PC from the domain. Add it back to the Domain.
   
   The Domain's name did not change from what it was at the start. Neither did FreeNAS' NetBIOS name or the User account's username and password.
   
   So I figured it would work as it did after the first reinstall+setup. It didn't. It gives me a new account. In the User's folder (Windows 8.1), there are 2 Users.
   
   User.Domain (My old domain account that I want access to.)
   User.Domain.000 (The new account it makes.)
9. I figured it was because I configured a Home Directory for that account to try out that functionality. I disable that (switch it back to /nonexistent). Doesn't fix it.
10. I notice this in the console:
    
    
    Code:

    Apr 27 03:58:28 FREENAS samba[2674]: /usr/local/sbin/samba_dnsupdate: RuntimeError: kinit for FREENAS$@DOMAIN.COM failed (Cannot contact any KDC for requested realm)
    Apr 27 03:58:28 FREENAS samba[2674]: [2014/04/27 03:58:28.525622, 0] ../lib/util/util_runcmd.c:317(samba_runcmd_io_handler)
    Apr 27 03:58:28 FREENAS samba[2674]: /usr/local/sbin/samba_dnsupdate: 

    
    
    And it locks up there at dnsupdate: with nothing after the :.
11. I have Windows Remote Server Administration Tools on this machine which I successfully used to see and edit Users and Groups on the FreeNAS DC before I upgraded the hardware & OS. The settings between then and now are identical.
    
    I try to open Users and Groups. It basically says it can't give me access since the user/pass is incorrect. I click "Change Domain Controller". It says under "Current Directory Server" a flashing |. Effectively, it says my current directory server is (Null). Even though I was added to the domain correctly (AFAIK) using the administrator password I had set up when configuring FreeNAS' Domain Controller settings.
12. I ping domain.com to see if it returns FreeNAS' IP. It does.

So yeah. Something is not right. It's almost like FreeNAS doesn't consider itself the Primary DC of the domain. It can't find itself (the "can't find KDC for domain" error in the console). Yet pinging the domain returns the right IP.

I figure that problem and my login issues for my domain account are linked somehow.

I have a task set up in Task Scheduler on Windows by my domain account which lists it's domain and username from before the upgrades which are identical to what they are now.

What really confuses me is that it worked after the first reinstall but not after the second. It's important to note that I didn't import any configurations so as to avoid whatever issue was causing the plugins to not work. All settings were manually done and double checked.

Any help anyone can offer is appreciated.

Edit:

Not to bring a (possibly) separate (but probably related) issue into this thread, but I just wanted to point out that my plugins still aren't working correctly. Specifically this is happening:

Code:

Apr 27 05:13:24 FREENAS manage.py: [freeadmin.navtree:526] Couldn't retrieve http://10.0.0.98/plugins/transmission/1/_s/treemenu: timed out
Apr 27 05:13:24 FREENAS manage.py: [freeadmin.navtree:526] Couldn't retrieve http://10.0.0.98/plugins/plexmediaserver/2/_s/treemenu: timed out

And looking at the end of the plugin's PBI under Installed Plugins, it says this: [plugin]-[version]-amd64

Note the AMD64 at the end of that. That's what the old hardware had (2 installations of FreeNAS ago). Now I have dual Xeons. I don't get it. :|

 

[dlavigne]

Code:

Apr 27 05:13:24 FREENAS manage.py: [freeadmin.navtree:526] Couldn't retrieve http://10.0.0.98/plugins/transmission/1/_s/treemenu: timed out
Apr 27 05:13:24 FREENAS manage.py: [freeadmin.navtree:526] Couldn't retrieve http://10.0.0.98/plugins/plexmediaserver/2/_s/treemenu: timed out

And looking at the end of the plugin's PBI under Installed Plugins, it says this: [plugin]-[version]-amd64

Note the AMD64 at the end of that. That's what the old hardware had (2 installations of FreeNAS ago). Now I have dual Xeons. I don't get it. :|

Regarding this part, it looks like a DNS error.

The amd64 simply indicates that it is a 64-bit app, not that it is amd.

 

[TremorAcePV]

Regarding this part, it looks like a DNS error.

The amd64 simply indicates that it is a 64-bit app, not that it is amd.

Thank you very much for the clarification and taking the time to respond to this post.

Before I upgraded my hardware, FreeNAS was my Domain Controller. So it was also my DNS server. Even now, it keeps throwing these out constantly:

Code:

May  1 14:39:54 FREENAS samba[2675]: [2014/05/01 14:39:54.466340,  0] ../lib/util/util_runcmd.c:317(samba_runcmd_io_handler)
May  1 14:39:54 FREENAS samba[2675]:  /usr/local/sbin/samba_dnsupdate: Traceback (most recent call last):
May  1 14:39:54 FREENAS samba[2675]: [2014/05/01 14:39:54.466518,  0] ../lib/util/util_runcmd.c:317(samba_runcmd_io_handler)
May  1 14:39:54 FREENAS samba[2675]:  /usr/local/sbin/samba_dnsupdate:  File "/usr/local/sbin/samba_dnsupdate", line 510, in <module>
May  1 14:39:54 FREENAS samba[2675]: [2014/05/01 14:39:54.466586,  0] ../lib/util/util_runcmd.c:317(samba_runcmd_io_handler)
May  1 14:39:54 FREENAS samba[2675]:  /usr/local/sbin/samba_dnsupdate:    get_credentials(lp)
May  1 14:39:54 FREENAS samba[2675]: [2014/05/01 14:39:54.466639,  0] ../lib/util/util_runcmd.c:317(samba_runcmd_io_handler)
May  1 14:39:54 FREENAS samba[2675]:  /usr/local/sbin/samba_dnsupdate:  File "/usr/local/sbin/samba_dnsupdate", line 123, in get_credentials
May  1 14:39:54 FREENAS samba[2675]: [2014/05/01 14:39:54.466692,  0] ../lib/util/util_runcmd.c:317(samba_runcmd_io_handler)
May  1 14:39:54 FREENAS samba[2675]:  /usr/local/sbin/samba_dnsupdate:    raise e
May  1 14:39:54 FREENAS samba[2675]: [2014/05/01 14:39:54.466746,  0] ../lib/util/util_runcmd.c:317(samba_runcmd_io_handler)
May  1 14:39:54 FREENAS samba[2675]:  /usr/local/sbin/samba_dnsupdate: RuntimeError: kinit for FREENAS$@DOMAIN.COM failed (Cannot contact any KDC for requested realm)
May  1 14:39:54 FREENAS samba[2675]: [2014/05/01 14:39:54.466806,  0] ../lib/util/util_runcmd.c:317(samba_runcmd_io_handler)
May  1 14:39:54 FREENAS samba[2675]:  /usr/local/sbin/samba_dnsupdate: 

And it just cuts off there but re-occurs every 10 minutes or so. It IS the KDC for the realm, so how it can't find itself, I don't know. Check below.

After reinstalling FreeNAS, I made it a DC again with the exact same everything. Domain name, IP address, Gateway, NetBIOS name, etc. So I'm not sure what that issue is.

It's also throwing these out:

Code:

May  1 18:53:17 FREENAS manage.py: [freeadmin.navtree:526] Couldn't retrieve http://10.0.0.98/plugins/couchpotato/4/_s/treemenu: HTTP Error 502: Bad Gateway
...
May  1 18:53:17 FREENAS manage.py: [freeadmin.navtree:526] Couldn't retrieve http://10.0.0.98/plugins/sickbeard/5/_s/treemenu: HTTP Error 502: Bad Gateway

But it's the same gateway my PC is using and it's working fine. It didn't do this before I set the IPv4 gateway manually and removing it doesn't change things.

And after checking my Nameserver settings, I had [stupidly] put my router's IP as a Nameserver. Why? Not sure. Probably got copy/paste happy while reconfiguring for the 2nd time. However, removing the setting then rebooting FreeNAS did not change it:

Code:

May  1 19:08:51 FREENAS smbd[2664]: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
May  1 19:08:52 FREENAS smbd[2664]: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
May  1 19:08:53 FREENAS smbd[2664]: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
May  1 19:08:54 FREENAS smbd[2664]: dnssd_clientstub ConnectToServer: connect() failed Socket:40 Err:-1 Errno:2 No such file or directory
May  1 19:08:55 FREENAS mDNSResponder: mDNSResponder (Engineering Build) (Apr 23 2014 17:17:29) starting
May  1 19:08:55 FREENAS mDNSResponder:  8: Listening for incoming Unix Domain Socket client requests
May  1 19:08:55 FREENAS mDNSResponder: Unable to parse DNS server list. Unicast DNS-SD unavailable
May  1 19:08:56 FREENAS mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C2FD60 FREENAS.local. (Addr) that's already in the list
May  1 19:08:56 FREENAS mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C30180 98.0.0.10.in-addr.arpa. (PTR) that's already in the list
...
May  1 19:12:04 FREENAS manage.py: [freeadmin.navtree:526] Couldn't retrieve http://10.0.0.98/plugins/plexmediaserver/2/_s/treemenu: timed out
May  1 19:12:04 FREENAS manage.py: [freeadmin.navtree:526] Couldn't retrieve http://10.0.0.98/plugins/transmission/3/_s/treemenu: timed out
May  1 19:12:04 FREENAS manage.py: [freeadmin.navtree:526] Couldn't retrieve http://10.0.0.98/plugins/couchpotato/4/_s/treemenu: timed out
May  1 19:12:04 FREENAS manage.py: [freeadmin.navtree:526] Couldn't retrieve http://10.0.0.98/plugins/sickbeard/5/_s/treemenu: timed out

Directory Services is running, so why it's trying to register FREENAS.local, I don't know. Although it did fix the KDC issue mentioned above as that isn't coming up this time.

Plugins, however, are still as they were. They won't start, and loading the Plugins GUI element takes forever and some are usually missing in the sidebar though it seems random which ones. Trying to start them manually causes this and nothing else:

Code:

May  1 19:19:43 FREENAS manage.py: [plugins.utils:92] Couldn't retrieve http://10.0.0.98/plugins/plexmediaserver/2/_s/status: HTTP Error 504: Gateway Time-out
May  1 19:19:43 FREENASmanage.py: [plugins.utils:92] Couldn't retrieve http://10.0.0.98/plugins/transmission/3/_s/status: HTTP Error 504: Gateway Time-out
May  1 19:19:43 FREENASmanage.py: [plugins.utils:92] Couldn't retrieve http://10.0.0.98/plugins/couchpotato/4/_s/status: HTTP Error 504: Gateway Time-out
May  1 19:19:43 FREENASmanage.py: [plugins.utils:92] Couldn't retrieve http://10.0.0.98/plugins/sickbeard/5/_s/status: HTTP Error 504: Gateway Time-out

I did the same thing with them as I did with FreeNAS' network configs. Added my router's IP as the gateway, then removed it as it started causing the plugins issues. It's like it doesn't update the gateway. Weird. I checked them again and there's nothing in the IPv4 Default Gateway field on the Jails, so not sure about that.

Anyway, I think I'm just going to nuke the install from orbit (delete everything but my media then move it elsewhere), salvage what I can from my Domain account, then switch back to a local account on my PC and start from scratch. I figure that's my best option, both to fix the Plugins issue and my Domain issues.

 

[dlavigne]

Anyway, I think I'm just going to nuke the install from orbit (delete everything but my media then move it elsewhere), salvage what I can from my Domain account, then switch back to a local account on my PC and start from scratch. I figure that's my best option, both to fix the Plugins issue and my Domain issues.

Yeah, something looks really funky. Was this 9.2.1.5? If not, try that version when you reinstall as it has a lot of CIFS/AD fixes.

 

[TremorAcePV]

Yeah, something looks really funky. Was this 9.2.1.5? If not, try that version when you reinstall as it has a lot of CIFS/AD fixes.

I believe it was. I'm using it now at least.

I've reinstalled FreeNAS from scratch and did the basics (i.e. config network settings, aggregated 2 ethernet ports in Load Balance mode, set up storage locations, and the like).

However, now I have a different issue (there's always one). When I click Plugins > Available, the list says "No entry has been found." I checked the repository it's checking and it's the default one under Plugins > Configuration: http://www.freenas.org/downloads/plugins/9/x64/pbi-meta/pbi-repo.rpo

If I click that link, it downloads the .rpo file to my computer.

This is what I did next:

Code:

[root@FREENAS ~]# ping google.com                                       
PING google.com (74.125.196.138): 56 data bytes                         
64 bytes from 74.125.196.138: icmp_seq=0 ttl=45 time=66.456 ms           
64 bytes from 74.125.196.138: icmp_seq=1 ttl=45 time=67.084 ms           
64 bytes from 74.125.196.138: icmp_seq=2 ttl=45 time=66.154 ms           
64 bytes from 74.125.196.138: icmp_seq=3 ttl=45 time=66.708 ms           
^C                                                                       
--- google.com ping statistics ---                                       
4 packets transmitted, 4 packets received, 0.0% packet loss             
round-trip min/avg/max/stddev = 66.154/66.601/67.084/0.341 ms 

So it's not an internet connection issue for FreeNAS. This user is having the same issue on a different version of FreeNAS (9.1.2.3).

I'm going to look for a different repository if I can, and if I can't find one, I'll try installing them manually.

I'd make a new thread for this issue, but I'm not sure how you guys feel about forum clutter and such.