H
Harpstein
I have AD setup on a Win2k3 system. It's all working and I can browse the
data from a LDAP client.
However, when I go to authenticate myself to the server, it works if I leave
the password blank.
I can send in the correct password, like "fred" and it works.
I can send in an empty password and it works.
It only fails if I send in a non-empty password that doesn't match the
actual password on the user record in AD.
Is there some sort of setting causing this? I'm new to AD and just really
want to try it out against my LDAP client but I don't see why binding would
work when I give it an empty password. Isn't this a big security hole?
Any help would be much appreciated.
Thanks,
harpstein
data from a LDAP client.
However, when I go to authenticate myself to the server, it works if I leave
the password blank.
I can send in the correct password, like "fred" and it works.
I can send in an empty password and it works.
It only fails if I send in a non-empty password that doesn't match the
actual password on the user record in AD.
Is there some sort of setting causing this? I'm new to AD and just really
want to try it out against my LDAP client but I don't see why binding would
work when I give it an empty password. Isn't this a big security hole?
Any help would be much appreciated.
Thanks,
harpstein