3.2 Samba4 (File Sharing)

[BrettonWoods]

New clean install of 3.2 and finally connected a client.

Win7 64 Zentyal 3.2 64.

This bit is prob voodoo but set the clock to update from the zentyal server address (kerb is very time sensitive).

In 3.2 the user you created on install isn't listed in the directory. So after failing with that user and administrator I created a user winadmin. Then added that to the domain admins group.

Then after a lot of attempts I added the domain in upper case as a FQDN in my case it was DOMAIN.LAN.

Hey presto managed to connect win7 after a lot of head scratching.

This has the new Samba update (was it released last night?)

Just some questions. Why isn't the install user a domain admin?

What is happening with Administrator as it exists in the logs? (Internal only?)
 

[robb]

The install user is a local user because at time of install there is no samba yet... (well at least, that's my best educated guess)

[christian]

and this account is local account, not LDAP account on which Samba relies on 

[BrettonWoods]

Yeah prob.

I wasn't sure if adding to the directory would cause any problems with anything else.
So I created another domain administrator of another name.

I will get back to you if adding the install user to the directory causes any probs.

[BrettonWoods]

Your post came after I had started.

Christian,

The install logon should that be left alone and another user name user for domain admins?

Or is it OK just to add that to the LDAP, prob problematic only if you have ldap=pam

[christian]

Or is it OK just to add that to the LDAP, prob problematic only if you have ldap=pam

No sure yo can add in LDAP entry that exist in /etc/passwd
I never tried but hope you can't because it would conflict at some time, e.g. if you look at nsswitch where you have LDAP + files