SOLVED FreeNas N00b

[Paul Clarke]

Hi.

I am new to FreeNas but looking at installing 9.3 in an AD environment.
Are there any issues I should be aware of?
We are a small office (<25 users) but I don't fancy rebuilding AD :)

 

[anodos]

Start in a test environment. Install a trial version of server / ad and join freenas. Test for yourself. I run freenas fine as ad member server, but that doesn't mean you should jump straight into production. :)

 

[Paul Clarke]

Hi.

Thanks for the reply - I will build it in VirtualBox and see what happens :)

Is there any pre-config I need to do or do I just link it to AD?

 

[Paul Clarke]

I have build in virtualbox now and as far as I can see it's linked to my AD, however I am not able to see any users/groups
When I run a wbinfo -t in the Shell I get this message:
checking the trust secret for domain xxxxxxx.LOCAL via RPC calls failed
error code was NT_STATUS_NO_SUCH_DOMAIN (0xc00000df)
failed to call wbcCheckTrustCredentials: WBC_ERR_AUTH_ERROR
Could not check secret

When I go to the AD page and click save I get 'Active Directory successfully updated'
I am sure it's something obvious I am missing but I can't see it

All help gratefully received :)

 

[anodos]

Hi.

Thanks for the reply - I will build it in VirtualBox and see what happens :)

Is there any pre-config I need to do or do I just link it to AD?

"Pre-config" is pretty much what you would expect. Set up a static IP address for FreeNAS, and configure DNS and NTP (both of which are required for configuring FreeNAS as a member server).

For testing I do physical for physical computers and vms for vms. Creating a separate testing network is not so difficult if you have an extra switch lying around, and a computer you can install a trial version of Windows server on.

Also, I know it's a bit late for this, but configuring a .local domain is not considered best practice.

 

[Paul Clarke]

I needed the .local domain in order to copy my current configuration.
I am now getting the error that my workgroup name is too long. Truncating to - but it doesn't say what it's truncating to

 

[Paul Clarke]

Update
I now have it linking to AD - Yay.
However users and groups are not showing in the GUI so I can't set permissions.
They do however show if I do a wbinfo -u and wbinfo -g in the shell.
Any ideas?

 

[Paul Clarke]

Nevermind - I was being impatient :)
All replicated now