I am attempting to join my slackware 12.2 server to a winodws 2003 domain. I get the following error.

net join -S myserver -W CORP.mydomain.COM -U admin

[2009/05/12 15:39:15, 0] utils/net_rpc_join.c:net_rpc_join_newstyle(393)
Error in domain join verification (credential setup failed): NT_STATUS_INVALID_COMPUTER_NAME

Unable to join domain CORP.


krb5.conf output

[libdefaults]
default_realm = CORP.mydomain.COM

[realms]
CORP.mydomain.COM = {
kdc = myserver.CORP.mydomain.COM
}

[domain_realms]
.CORP.mydomain.COM = CORP.mydomain.COM
.kerberos.server = myserver.CORP.mydomain.COM

smbd.conf out put


[global]
# realm = CORP.mydomain.COM
workgroup = CORP.mydomain.COM
security = domain
# encrypt passwords = yes
password server = myserver
domain master = No
winbind gid = 10000-60000
winbind use default domain = yes
wins server = myserver
wins support = Yes
netbios name = newserver
interfaces = eth0


Any help is always apreciated.

on the machine that you want to join to domain, do:

Thank you for the reply however I get the same result.

Ok I have played with the commands abit and I get a different error.


root@mylinuxbox:/etc/samba# net rpc join -S server -n myname -U admin "Server/OU/TST"
Enter p1723646's password:
[2009/05/13 08:17:08, 0] rpc_client/cli_pipe.c:get_schannel_session_key_common(2449)
get_schannel_session_key: could not fetch trust account password for domain 'CORP'
[2009/05/13 08:17:08, 0] utils/net_rpc_join.c:net_rpc_join_ok(87)
net_rpc_join_ok: failed to get schannel session key from server CDC-ENT-04 for domain CORP. Error was NT_STATUS_CANT_ACCESS_DOMAIN_INFO
Unable to join domain CORP.

Not sure what I am doing wrong. I have also attempted to put this in with the account not created but it tells me that I dont have permissions. I can creat the account in the AD users and computers mmc.

This issue is now resolved. I had to make a few changes to my config and then it worked
one was I removed the fdnq from the workgroup and then removed the wins server name. worked like a charm.

Thanks for this post! I was having the same issue and would have never thought of taking out the FQDN from my workgroup entry!! Saved me a ton of time!!