samba domain integration

[plegrand]

@Tom-Elliott
Join Domain after image task : checked
Domain name : samba_domain
Domain Username : 192.168.39.237\admin_samba
Domain Password : password
No success
on the same computer here is the result with netdom command wich works :
C:\Documents and Settings\Administrateur>netdom.exe JOIN %ComputerName% /Domain:samba_domain /UserD:admin_samba /PasswordD:“password” /REBoot:60
The command completed successfully.

[plegrand]

@Tom-Elliott
is there a way to downgrade to the svn version wich worked before ? Just to test ?

[Tom Elliott]

@plegrand Yes, but have you tried joining domain with the username set as \admin_samba?

[plegrand]

@Tom-Elliott oups no .
I test now
Join Domain after image task : checked
Domain name : samba_domain
Domain Username : \admin_samba
Domain Password : password

http://192.168.39.243/fog/service/hostname.php?mac=00:21:85:71:bd:8e
#!ok=gim-127-13 #AD=1 #ADDom=samba_domain #ADOU= #ADUser=samba_domain\\admin_samba #ADPass=
No more success
In fog.log :
The parameter is incorrect, code = 87

[plegrand]

@Tom-Elliott is it possible to downgrade to a svn version for example 4058 then test all svn version to 4065 to see which version worked ?

[Tom Elliott]

Yes.

Use the command svn up -r REVYOUWANTTOTRY while in the trunk root directory

[plegrand]

@Tom-Elliott and then
cd bin
./installfog.sh

?
i test that thanks

[ch3i]

@plegrand yep

[EAHarvey]

@Tom-Elliott This only works going forward in version correct? Not downgrade.?

[ch3i]

@EAHarvey yep too

[Tom Elliott]

@EAHarvey I don’t know what you mean.

@plegrand is trying to find out when samba domain joining started failing. It is believed to have worked at some point in the past, so to test he is downgrading and going to try finding out exactly when it started.

[plegrand]

@Tom-Elliott in fact i just begin to wonder if it worked once
I cant understand why it works with netdom command and not with fog client

Do i have to uninstall and reinstall client to ?

[Tom Elliott]

@plegrand Well can you provide a teamviewer session (in chat) with me and I can try to help narrow down exactly where the problem lies? I’m going to guess it has to do with the user having the domain as a part of the field.

[plegrand]

@Tom-Elliott Eureka !!
I made some tests, and i know why i said it worked before : it works with the legacy client and
“Domain Password Legacy” field filled
without problem.
Then i uninstalled legacy client and install new client but now there is an other error

29/09/2015 16:39 Client-Info Version: 0.9.5
 29/09/2015 16:39 HostnameChanger Running...
 29/09/2015 16:39 Middleware::Communication URL: http://192.168.39.243/fog/service/servicemodule-active.php?moduleid=hostnamechanger&mac=00:21:85:71:BD:8E|&newService=1
 29/09/2015 16:39 Middleware::Communication Response: Success
 29/09/2015 16:39 Middleware::Communication URL: http://192.168.39.243/fog/service/hostname.php?moduleid=hostnamechanger&mac=00:21:85:71:BD:8E|&newService=1
 29/09/2015 16:39 Middleware::Communication Response: Invalid host certificate
 29/09/2015 16:39 Middleware::Communication URL: http://192.168.39.243/fog/management/other/ssl/srvpublic.crt
 29/09/2015 16:39 Data::RSA CA cert found
 29/09/2015 16:39 Middleware::Authentication Cert OK
 29/09/2015 16:39 Middleware::Communication POST URL: http://192.168.39.243/fog/management/index.php?sub=authorize
 29/09/2015 16:39 Middleware::Communication Response: Invalid security token

[Tom Elliott]

So does that seem to indicate a difference in the passwords?

[plegrand]

@Tom-Elliott it’s the same password used
i put the “real” password into “Domain Password” field
and same password encrypted with FogCrypt into “Domain Password Legacy” field

[plegrand]

@Tom-Elliott May be i didn’t understand your question?
Do you need more information ?
I think legacy client and new client doesn’t use the same method to join domain. Am i wrong ?
Just to be clear
join domain works fine with legacy client and doesn’t works with the new client
I made the tests with the same domain user and the same password
clear for new client
and encrypted with Fog Crypt for the legacy client

[plegrand]

@Tom-Elliott Hello Tom, do you think my problem come from a bug in the new client, or from me and my configuration?
Do you want i make some other tests ?
Thanks

[Sebastian Roth]

I guess @Jbob would know…

[Tom Elliott]

I would ask if you have updated again.

See, I’ve tested what I can, but I don’t have a logical answer as to why it’s not working for you. It should be.