I thought step 2 was done by the installer but I could be wrong.

Step 3 shouldn't be necessary if you enable dynamic DNS updates
prior to enabling the CIFS service:

        sharectl set -p ddns_enable=true smb
        svcadm enable -r smb/server

There appears to be a bug in BIND, which prevents it from making
dynamic DNS updates on ADS.  There is an open bug with ISC.
So we perform the updates from within the CIFS service.

We are looking into ways of handling the Kerberos situation more
elegantly.

Alan
--

On 12/01/08 06:36, Ross wrote:
> Just wanted to check if my experience of joining a domain with snv_103 is 
> correct.  Am I making any obvious mistakes here, and are there plans to 
> simplify any of these steps (2, 3 & 5 look to me like they could be covered 
> by the installer)?
> 
> 1. Install Solaris, configuring kerberos, DNS, etc.
> 
> 2. Configure a hostname, since this doesn't appear to be covered by the 
> install.
> edit /etc/hostname.e1000g0
> 
> 3. Load your AD DNS tool and add the hostname and IP address since Solaris 
> doesn't appear to register it's IP with the server.
> 
> 4. Synchronise time with the domain with:
> # ntpdate server
> 
> 5. Edit the krb5.conf file, since there appear to be settings missed here 
> too.  Ensure the default realm is in CAPS, and set [domain_realm] as .domain 
> = REALM, eg:
> [domain_realm]
> .domain.local = DOMAIN.LOCAL
> 
> 6. Start the service
> # svcadm enable -r smb/server
> 
> 7. Join the domain
> # smbadm join -u user domain

_______________________________________________
cifs-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/cifs-discuss

Reply via email to