Compartilhar via

How fast can you authenticate users (part2) ? .. not very.

  • Artigo

Marginally related to my other post..

 

This could be an important hotfix for you - as it will impact your 2k3 Sp1 servers and DC's.

https://support.microsoft.com/?kbid=905700

You may receive an "RPC server is too busy to complete this operation" error message when you try to log on to a computer that is running Windows Server 2003 with Service Pack 1

Netlogon logs will show...

<timestamp> [CRITICAL] WW001: NlSessionSetup: Session setup: cannot I_NetServerReqChallenge 0xc0020018
<timestamp> [MISC] Eventlog: 5719 (1) "<domain>" 0xc0020018 c0020018 ....
<timestamp> [SESSION] <domain>: NlSetStatusClientSession: Set connection status to c000005e

C:\WINDOWS\system32>err c0020018
# for hex 0xc0020018 / decimal -1073610728 :
  RPC_NT_SERVER_TOO_BUSY                                        ntstatus.h
# The RPC server is too busy to complete this operation.
# 1 matches found for "c0020018"

C:\WINDOWS\system32>err c000005e
# for hex 0xc000005e / decimal -1073741730 :
  STATUS_NO_LOGON_SERVERS                                       ntstatus.h
# There are currently no logon servers available to service
# the logon request.
# 1 matches found for "c000005e"

This is on any server running 2k3 SP1. Basically, the problem is that we inadvertantly limited the maximum number of concurrent RPC call requests that the netlogon interface can accept.  But we limited it to 10.  No need to explain why thats bad..

spat

Comments

  • Anonymous
    May 20, 2006
    heya, bombur :)