Clients Cannot Log On by Using Kerberos over TCP

This article was previously published under Q320903
This article has been archived. It is offered "as is" and will no longer be updated.
Clients cannot log on to the domain if the clients use Kerberos over Transport Control Protocol (TCP). Clients that use Kerberos over User Datagram Protocol (UDP) can log on correctly.
Kerberos may stop accepting connections over TCP. This condition is temporary; Kerberos recovers and begins accepting connections again after approximately two minutes.

Service Pack Information

To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack

Hotfix Information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.The English version of this fix should have the following file attributes or later:
Date         Time   Version        Size       File name--------------------------------------------------05-Jun-2002  10:16  5.0.2195.5781    123,664  Adsldp.dll05-Jun-2002  10:16  5.0.2195.5781    131,344  Adsldpc.dll05-Jun-2002  10:16  5.0.2195.5781     62,736  Adsmsext.dll05-Jun-2002  10:16  5.0.2195.5801    358,160  Advapi32.dll05-Jun-2002  10:16  5.0.2195.5265     42,256  Basesrv.dll05-Jun-2002  10:16  5.0.2195.5855     49,424  Browser.dll05-Jun-2002  10:16  5.0.2195.5595    135,952  Dnsapi.dll05-Jun-2002  10:16  5.0.2195.5595     96,016  Dnsrslvr.dll05-Jun-2002  10:16  5.0.2195.5722     45,328  Eventlog.dll05-Jun-2002  10:16  5.0.2195.5684    222,480  Gdi32.dll05-Jun-2002  10:16  5.0.2195.5859    145,680  Kdcsvc.dll04-Jun-2002  14:31  5.0.2195.5859    199,952  Kerberos.dll05-Jun-2002  10:16  5.0.2195.4928    708,880  Kernel32.dll04-Jun-2002  14:32  5.0.2195.5859     71,024  Ksecdd.sys04-Jun-2002  14:32  5.0.2195.5859    504,080  Lsasrv.dll04-Jun-2002  14:32  5.0.2195.5859     33,552  Lsass.exe04-Jun-2002  14:31  5.0.2195.5859    107,792  Msv1_0.dll05-Jun-2002  10:16  5.0.2195.5855    307,472  Netapi32.dll05-Jun-2002  10:16  5.0.2195.5723    360,208  Netlogon.dll05-Jun-2002  10:16  5.0.2195.5839    916,752  Ntdsa.dll05-Jun-2002  10:16  5.0.2195.5585    386,832  Samsrv.dll05-Jun-2002  10:16  5.0.2195.5837    128,784  Scecli.dll05-Jun-2002  10:16  5.0.2195.5757    299,792  Scesrv.dll05-Jun-2002  10:16  5.0.2195.4314    402,192  User32.dll25-Jun-2001  19:17        47,808  User.exe05-Jun-2002  10:16  5.0.2195.5644    369,936  Userenv.dll05-Jun-2002  10:16  5.0.2195.5859     48,912  W32time.dll04-Jun-2002  14:32  5.0.2195.5859     57,104  W32tm.exe31-May-2002  10:26  5.0.2195.5840  1,642,192  Win32k.sys03-May-2002  11:31  5.0.2195.5731    178,960  Winlogon.exe05-Jun-2002  10:16  5.0.2195.4602    243,472  Winsrv.dll05-Jun-2002  10:16  5.0.2195.5737    125,712  Wldap32.dll					

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.
For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:
265173 The Datacenter Program and Windows 2000 Datacenter Server Product
For additional information about how to install multiple hotfixes with only one reboot, click the article number below to view the article in the Microsoft Knowledge Base:
296861 Use QChain.exe to Install Multiple Hotfixes with One Reboot

Artikel-id: 320903 - Laatst bijgewerkt: 02/27/2014 21:12:41 - Revisie: 2.10

Microsoft Windows 2000 Server SP1, Microsoft Windows 2000 Service Pack 3, Microsoft Windows 2000 Server SP2, Microsoft Windows 2000 Advanced Server SP1, Microsoft Windows 2000 Advanced Server SP2, Microsoft Windows 2000 Advanced Server SP3, Microsoft Windows 2000 Professional SP1, Microsoft Windows 2000 Professional SP2, Microsoft Windows 2000 Service Pack 3

  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbsecurity kbwin2ksp4fix kbbug kbfix kbwin2000presp4fix KB320903
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)