Intermittent directory access issue

-

we are recieving error intermitently below. @ least once week, @ present on 2 of our dc's. ideas? our dc's hardware is old (7 years old) and lsass.ese average 60-70% . 

win_evt_c_000001 domainname\servername win_evt_c_000001 msexchangeal_8026_e: ldap bind unsuccessful on directory dcservername distinguished name ''. directory returned error:[0x55] timeout.


also

'directory service unavailable on dcname'

its seems though gc , ldap lookups failing on server

 

hi,

 

based on error message, seems exchange server not use ldap connect gc , error timeout. notice cpu usage of process lsass.exe average 60-70%, there may not resource available if 1 or 2 more applications run @ same time on dc. result, 1 of possible cause there no resource available on dc when exchange server attempt bind it. after resource released, issue disappears. if case, may need upgrade hardware of dc.

 

since there several possible causes , issue occurs intermittently, please understand forum not best resource identify issue. confirm if issue causes production impact. if so, i’d recommend contact microsoft customer support service. can enable performance monitor , debug log trace issue.

 

to obtain phone numbers specific technology request please take @ web site listed below:
http://support.microsoft.com/default.aspx?scid=fh;en-us;phonenumbers

 

additionally, can use microsoft exchange server best practices analyzer tool determine settings on exchange server.

 

description of microsoft exchange server best practices analyzer tool

http://support.microsoft.com/kb/892213/en-us



Windows Server  >  Directory Services



Comments

Post a Comment

Popular posts from this blog

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

-
looking options resolve error , prevent in future. thanks help. hardware: 2 node dell hv cluster running2012r2 dc 8 nic/ea in multiplex mode 4x hyper-v 4x hosts storage: 2x synology nas, accessed through iscsi hosts , cluster relevant logs: log name:      microsoft-windows-failoverclustering/diagnostic source:        microsoft-windows-failoverclustering date:          event id:      2050 task category: none level:         warning keywords:       user:          system computer:      l description: [dcm] filter wimmount found @ unsafe altitude 180700 log name:      system source:        microsoft-windows-failoverclustering date:         event id:      5125 task category: cluster shared volume level:         warning keywords:       user:          system computer: description: cluster shared volume 'volume1' ('cluster disk 1') has identified 1 or more active filter drivers on device stack interfere csv operatio
Read more

Failed to delete the test record dcdiag-test-record in zone test.com

-
ps c:\users\administrator.test> dcdiag /test:dns directory server diagnosis performing initial setup:    trying find home server...    home server = dc02    * identified ad forest.    done gathering initial info. doing initial required tests    testing server: default-first-site-name\dc02       starting test: connectivity          ......................... dc02 passed test connectivity doing primary tests    testing server: default-first-site-name\dc02       starting test: dns          dns tests running , not hung. please wait few minutes...          ......................... dc02 passed test dns    running partition tests on : forestdnszones    running partition tests on : domaindnszones    running partition tests on : schema    running partition tests on : configuration    running partition tests on : test    running enterprise tests on : test.com       starting test: dns          test results domain
Read more

Azure MFA with Azure AD and RDS

-
i have setup following lab in azure , need help. a server (domain controller) , remote desktop services. and server multi factor authentication server. i have setup following one http://www.rdsgurus.com/uncategorized/step-by-step-using-windows-server-2012-r2-rd-gateway-with-azure-multifactor-authentication/ and when im connecting got following error. the user "domain\username", on client computer "xxx.xxx.xxx.xxx", did not meet connection authorization policy requirements , therefore not authorized access rd gateway server. authentication method used was: "ntlm" , connection protocol used: "rpc-http". following error occurred: "23003". also on security log i've got following authentication details: connection request policy name: ts gateway authorization policy network policy name: - authentication provider: radius proxy authentication server: test.test.local authentication type: - eap t
Read more