search for: nileadmin

Hi I have a Samba AD-DC (on ubuntu) and I've created a user on it the DC called nileadmin. On the DC, 'pdbedit -w nileadmin' finds the entry and returns nileadmin:4294967295:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:6590718693B2E602D30F67B848E08AE9:[U ]:LCT-678A9897: I've joined a member (also a ubuntu host running samba) to the domain. The join is successful. But when I ru...

On Thu, 23 Jan 2025 16:14:43 -0800 Gopal Raman via samba <samba at lists.samba.org> wrote: > Hi > I have a Samba AD-DC (on ubuntu) and I've created a user on it the DC > called nileadmin. > On the DC, 'pdbedit -w nileadmin' finds the entry and returns > nileadmin:4294967295:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:6590718693B2E602D30F67B848E08AE9:[U > ]:LCT-678A9897: > > I've joined a member (also a ubuntu host running samba) to the > domain. The joi...

...c1.cn.lan" 3 Finally, the most important part is to pass the "--domain=cn.lan" option to ntlm_auth. Without this, winbindd complains that username is not found. This was the breakthrough that makes ntlm_auth work. ntlm_auth --allow-mschapv2 --domain=cn.lan --request-nt-key --username=nileadmin --challenge=eaea1458abf1a0b7 --nt-response=8f9ab8760a15cd40f2686c5a4c7954922ed17fb9f4cad7b3 GOTCHAS 1 I had a simple smb.conf on the DC but testparm would always report that it was a "ROLE_DOMAIN_MEMBER" instead of "ROLE_ACTIVE_DIRECTORY_DC". Finally, I had to delete the smb...

...ius server to validate the MSChapV2 Challenge-Response sent by the client by talking to the Samba DC ecosystem. I'm using the ntlm_auth program to talk to Samba and it works as expected when I run it on the DC host in a bash shell like so: ntlm_auth --allow-mschapv2 --request-nt-key --username=nileadmin --challenge=eaea1458abf1a0b7 --nt-response=8f9ab8760a15cd40f2686c5a4c7954922ed17fb9f4cad7b3 The above is OK for testing, but in practice, I won't be able to run shell commands on the DC ( it could be a windows server ) so I have to run ntlm_auth on a different host. So I added another Linux se...

...te the MSChapV2 Challenge-Response sent by the > client by talking to the Samba DC ecosystem. I'm using the ntlm_auth > program to talk to Samba and it works as expected when I run it on the DC > host in a bash shell like so: > ntlm_auth --allow-mschapv2 --request-nt-key --username=nileadmin > --challenge=eaea1458abf1a0b7 > --nt-response=8f9ab8760a15cd40f2686c5a4c7954922ed17fb9f4cad7b3 > > The above is OK for testing, but in practice, I won't be able to run shell > commands on the DC ( it could be a windows server ) so I have to run > ntlm_auth on a different host...