search for: connect5

...'s password: rpcclient $> chgpasswd2 test Password01! Password02! result was NT_STATUS_ACCESS_DENIED Also when using rpcclient client with another account which is a domain user (i.e : Test2) and calling 'chgpasswd2' on the user 'Test' this is working fine ! (Indeed the Connect5 worked and thus 'ChangePasswordUser2 get called) Commands: rpcclient -U "CORP.LOCAL\TEST2" 10.10.10.2 Enter CORP.LOCAL\TEST2's password: rpcclient $> chgpasswd2 test Password01! Password02! rpcclient $> I tried to dig into the code on github on the cli_samr.c / pas...

...etc.. on the DC with this session(if not allowed) but you're allowed to change your password. Nevertheless my problem do not lie here since the first connection to the IP$ is established but rather on the inner working of rpcclient vs smbpasswd. My question is why do rpcclient perform a 'Connect5/4/2' before performing the 'ChangeUserPassword' is performed in contrary of smbpasswd. In the end this is perfectly working with smbpasswd but the behavior of rpcclient over this method piqued my curiosity Best regards, Jerem ________________________________ From: Jeremy Brousseau &lt...