I have been having issues joining an ad domain with nv105 in a complex site- multiple dcs on different subnets.
I have two tests servers, both giving the same results. smbadm join -u will always fail to successfully complete. It will do some of the actions eg. sometimes the keytab is created, ad machine account is created, but it doesn't ever report success. If I run adjoin-s10u5, it does work every time, but smbadm list reports it is still in a workgroup. This is fixed by running smbadm join -u again and then it will succeed. After a complete reinstall I tested things before trying again. Kerberos checks out - I can kinit the Windows Admin account credentials. adjoin in dry run doesn't show anything obvious - it finds the dns info and locates all the AD servers. One thing I did find: it is common practice for the FQDN to be entered as the server name during install. This creates problems when trying to join a domain. Any ideas or suggestions would be gratefully accepted. -- This message posted from opensolaris.org _______________________________________________ cifs-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
