Displaying 4 results from an estimated 4 matches for "secret123".
Did you mean:
secret1
2019 Nov 06
2
NTLM refuses to work on a DC
...mba/shares.conf
[netlogon]
??? path = /var/lib/samba/sysvol/internal.company.com/scripts
??? browseable = no
??? read only = yes
[sysvol]
??? path = /var/lib/samba/sysvol
??? read only = no
When I run the following, I get no problems whatsoever:
radtest domainuser userpassword localhost 0 secret123
(To those who are not familiar, radtest is a tool for testing
authentication on FreeRADIUS)
Also when I run the following:
ntlm_auth --request-nt-key --domain=COMPANY --username=domainuser
--password=userpassword
NT_STATUS_OK: The operation completed successfully. (0x0)
Same with wbinfo -a...
2013 Nov 20
0
NTLM authentication in Thunderbird vs Outlook 2010.
...pe=subtree filter=(&(objectClass=nrPOPAccount)(uid=migration.test at network.id.au)) fields=uid,userPassword
Nov 19 18:14:53 dovecot-test-1 dovecot: auth: Debug: ldap(migration.test at network.id.au,203.30.252.5,<sI7Ga4LrOADLHvwF>): result: uid=migration.test at network.id.au userPassword=Secret123
All good.
Outlook 2010:
1) IP proxy.netregistry.net.47129 > dovecot-test-1.private.netregistry.net.pop3
E..3.. at .}..........)...n...Q..f9P..qOv..AUTH NTLM
2) IP dovecot-test-1.private.netregistry.net.pop3 > proxy.netregistry.net.47129
E..,.. at .@.P....).....n....f9...\P....W..+
3) IP pr...
2019 Nov 06
0
NTLM refuses to work on a DC
...samba/sysvol/internal.company.com/scripts
> ??? browseable = no
> ??? read only = yes
>
> [sysvol]
> ??? path = /var/lib/samba/sysvol
> ??? read only = no
>
> When I run the following, I get no problems whatsoever:
>
> radtest domainuser userpassword localhost 0 secret123
>
> (To those who are not familiar, radtest is a tool for testing
> authentication on FreeRADIUS)
>
> Also when I run the following:
>
> ntlm_auth --request-nt-key --domain=COMPANY --username=domainuser
> --password=userpassword
>
> NT_STATUS_OK: The operation co...
2006 Oct 17
0
lots of registrations, sip problem
...to register, when it has clearly already done so. Even sip show
registry shows that provider as registered. Please note the difference
in URI, first time it's sip1.provider.com, second time it's
sip:my-provider-link. This is my sip.conf (relevant parts of it):
register => 4221917293125:secret123@sip1.provider.com/4221917293125
[my-provider-link]
type=friend
username=4221917293125
secret=secret123
host=sip1.provider.com
nat=no
context=provider-in
canreinvite=no
insecure=very
qualify=no
It seems to me, that it tries to register also this
my-provider-link somehow, but I have no idea how...