LDP.exe - NULL authentication issue


as part of external audit, auditor used ldp.exe test null sessions. now, have null sessions below rootdse turned off (restrictanonymous=1,restrictanonymoussam=1 , everyoneincludesanonymous=0). test procedure used follows:

  1. fire ldp , connect localhost via port 389. connects fine , shows rootdse info.
  2. do bind without entering credentials (just click ok on bind screen).
  3. ldp shows 'authenticated dn:'null'

so far good. when went to view \ tree , select domain (ex: dc=<test>, dc=com) returns objects , ous below root. not good. wrote , manager jumped on me.

using adsiedit, verified null access rootdse. attempting access else produced error.

after doing testing, found out ldp using logon account directory access, not null. see access in security event log.

does have information on issue ldp? need show auditor (and manager) not using null.

thanks

per article:

http://technet.microsoft.com/en-us/library/cc731530.aspx

can simple bind in ldp and specify blank password anonymous credentials?

 


richard mueller - mvp directory services


Windows Server  >  Directory Services



Comments

Popular posts from this blog

Motherboard replacement

Cannot create Full Text Search catalog after upgrading to V12 - Database is not fully started up or it is not in an ONLINE state

Remote Desktop App - Error 0x207 or 0x607