This is the code which is returning the uSAMAccountName which is pre-win2k
name of the user.
char *ads_pull_username(ADS_STRUCT *ads, TALLOC_CTX *mem_ctx,
LDAPMessage *msg)
{
#if 0 /* JERRY */
char *ret, *p;
/* lookup_name() only works on the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Felipe Augusto van de Wiel wrote:
Imagining that Samba3 is not as good as Samba4 with AD
and that Samba3 gives preference to NT4-style domains, probably
it is using the pre-win2k names. If you create a user without
all the options that AD
Actually in this case userPrincipalName and sAMAccountname are different.
Is it possible that Samba only displays the sAMAccountname?
Also if those differ, is it possible that Samba will have problem
authenticating against AD using win2k name of the user?
On current version of samba that's whats
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Kaustubh Chaudhari wrote, On 19-07-2007 08:24:
Hi All,
I create a user in windows2k3 AD server whose Name is test Logon name
is win2k3test and Pre-win2k name is testprewin2k (You get all this
options when you create user in AD)
My samba
Hi All,
I create a user in windows2k3 AD server whose Name is test Logon name
is win2k3test and Pre-win2k name is testprewin2k (You get all this
options when you create user in AD)
My samba is connected with this AD every thing works fine but when i Do
wbinfo -u i can see the prewin2kname
