search

shahilendra / hashing-password-filter

Automatically exported from code.google.com/p/hashing-password-filter
0 stars 0 forks source link

'real time' update error of 'Error during LOgonUserEx: Logon failure: unknown user name or bad password.' #18

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?

1.Installed latest version of product as per instructions on both AD DC's. 
(Twin site AD setup running on 2003 x64 DC's)
2. Change a users password. The correct entry is added to AD and running the 
Google Apps Directory Sync tool sees the users password correctly changed in 
Google Apps to match the AD password. 
3.The 'real time' updating of the password fails and produces the log entry:

[2010/09/01 13:45:43:011]:Changed password for user "dave.smith"
[2010/09/01 13:45:43:058]:Error during LOgonUserEx: Logon failure: unknown user 
name or bad password.

[2010/09/01 13:45:43:058]:Error during Unload User profile: The parameter is 
incorrect.

The .ini file looks like below:

[Main]
;name of you google apps
appsDomain=glassesdirect.com
;name and password of an administrator account of google apps
appsAdmin=nameofadminaccount
appsPasswd=adminaccountspassword
;DN and password of an AD user that can write the “hashedPassword” field
ldapAdminBindDn="CN=syncAppUser,OU=Admin,DC=pe,DC=local"
ldapAdminPasswd=*********
;LDAP query to find your AD users
ldapSearchBaseDn="OU=Google,DC=pe,DC=local"
;path of sync application executable (GoogleHashUpdater.exe)
processPath=C:\windows\GoogleHashUpdater.exe
;name and password of a local account to use to run the sync application
processUser=PE\syncAppUser
processPasswd=********
;settings for the proxy to use to connect to google apps
;leave blank if not needed
proxyAddress=
proxyUser=
proxyPassword=

The accounts have been setup with the correct authority and appear to be able 
to logon correctly - would you be able to help me out with the specific error 
I'm getting so I can get 'real time' password syncing working?

Thanks for your help - and for taking the time to work on a solution to get AD 
passwords syncing!

Original issue reported on code.google.com by and...@myoptiquegroup.com on 22 Sep 2010 at 3:22

GoogleCodeExporter commented 8 years ago 
I am getting the same issue on a 2003 64 server.  Any resolution?

Original comment by ja...@bestlives.net on 10 Aug 2011 at 6:04

GoogleCodeExporter commented 8 years ago 
Sadly no, still the same. Although I'm going to check now to see if there's 
been an new version since I last updated!
I'm just using a scheduled job to run once a day and manually update the Google 
passwords.

Original comment by and...@myoptiquegroup.com on 10 Aug 2011 at 8:09

GoogleCodeExporter commented 8 years ago 
The issue has to do with the processUser, Try without PE\

Original comment by m...@mosheldon.com on 17 Nov 2011 at 10:13

GoogleCodeExporter commented 8 years ago 
...it's the same with or without the PE\ I'm afraid.
You can logon to the server OK with the syncAppUser account which has full 
domain admin rights, it just doesn't seem to want to use it...

Original comment by and...@myoptiquegroup.com on 21 Nov 2011 at 11:34

GoogleCodeExporter commented 8 years ago 
And as I'm setting up some new servers I've found out what it was!
for the 
appsAdmin
I'd put in 
accountname@domainname.com
realising that the @domainname.com probably wasn't needed as it was stated 
earlier I just tried it as
accountname

and it started working! Only taken me 1.5 years to work that one out ;-)

Original comment by and...@myoptiquegroup.com on 21 Mar 2012 at 9:35