pmsys
Cadet
- Joined
- May 13, 2014
- Messages
- 8
Hi all,
I had a domaincontroller running on a specific IP inside a VBox-instance on my FreeNas-instance.
I used the "DirectoryService" -> "Active Directory" functionality.
My problem was that everytime I rebooted the Nas I had to reconnect to that DC.
However, my FreeNas was connected to this AD and all was running fine.
A few weeks ago I moved the DC to a seperate machine outside my FreeNas-instance (with new IP).
Up from this point I was not able to connect the AD anymore.
Everytime time I tried to save the settings I always got this error-string: "{'info': 'invalid DN', 'desc': 'Invalid DN syntax'}."
I tried to set an incorrect Domain-name (as a test) and I got what I was expecting:"Unable to find domain controllers for lan.pm".
Now I don't know if this is a FreeNas-issue or if there is another problem.
I use the "Univention Corporate Server" as DC. The configuration is the same as in the old instance.
Thanks for advice.
I had a domaincontroller running on a specific IP inside a VBox-instance on my FreeNas-instance.
I used the "DirectoryService" -> "Active Directory" functionality.
My problem was that everytime I rebooted the Nas I had to reconnect to that DC.
However, my FreeNas was connected to this AD and all was running fine.
A few weeks ago I moved the DC to a seperate machine outside my FreeNas-instance (with new IP).
Up from this point I was not able to connect the AD anymore.
Everytime time I tried to save the settings I always got this error-string: "{'info': 'invalid DN', 'desc': 'Invalid DN syntax'}."
I tried to set an incorrect Domain-name (as a test) and I got what I was expecting:"Unable to find domain controllers for lan.pm".
Now I don't know if this is a FreeNas-issue or if there is another problem.
I use the "Univention Corporate Server" as DC. The configuration is the same as in the old instance.
Thanks for advice.