Error code 1326
-
@Whitespire-tech said in Error code 1326:
1326
That error usually correlates to a bad username/password used. I’d try clearing out the AD account information under fog settings/Active Directory Defaults and re-entering. Make sure you enter the domain in the top box(AD DEFAULT DOMAINNAME) and not by the username in (AD DEFAULT USER).
Also make sure the password you enter in (AD DEFAULT PASSWORD) is not encrypted. The legacy password field is the one that requires encryption and is only for legacy clients.
After you make this change please update the AD settings under the individual host or host group(Click clear fields then uncheck/recheck the “Join Domain after deploy” box so it gets the new settings.
-
I have tried this and it hasn’t made a difference I have double checked the username and password it all appears to be correct.
-
@Whitespire-tech I remember we had an issue with some special character that was never resolved: https://forums.fogproject.org/topic/12407/active-direcory-join-fail-bad-password-1-5-4
-
@Sebastian-Roth The password doesn’t contain any special characters so I didn’t think it was that changed the password to use all lowercase letters and still had the same problem any ideas ?
-
@Whitespire-tech Did you try to manually join the domain with exactly the same credentials? Please give it a try and see if that works.
-
The domain join manually from the computer with the same credentials works fine the only difference is with the manual install I have server.local\username but I am assuming that fog takes the default domain and puts it in front of the username.
-
@Whitespire-tech Are you sure you have the right OU set as well? Password un-encrypted!?
-
As far as i can tell this should all be right I have tried with empty ou aswell
image url)
-
Check your OU Settings.
In our systems it looks like this:
OU=Computers,OU=COMPANY,DC=company,DC=local
Not sure if that is the problem, but since its different from our working setup …
-
We have managed to fix this for some reason the username needs the domain name in front of it and it then works fine so in AD default user we have now white_spire\fog and then password and appears to be working now
-
Interesting, we do not need the Domain name in front
Anywho, great that you solved it
-
@Whitespire-tech @Taspharel Yeah, this is kind of strange. I checked to fog-client code and it definitely uses the domain information and shouldn’t need “domain/username” notation. Hmmmmmm. Maybe that depends on the OS you have? Which client OS is this?