Microsoft KB Archive/185081

From BetaArchive Wiki
Knowledge Base


No Domain Controllers Found When Logging on Using RAS

Article ID: 185081

Article Last Modified on 11/1/2006



APPLIES TO

  • Microsoft Windows NT Server 4.0, Terminal Server Edition
  • Microsoft Windows NT Workstation 4.0 Developer Edition
  • Microsoft Windows NT Server 4.0 Standard Edition



This article was previously published under Q185081


SYMPTOMS

When you log on to a Windows NT computer after just logging off and selecting the Logon using Dial-up Networking option, you may receive the following error:

A domain controller for your domain could not be contacted. You have
been logged on using cached account information. Changes to your profile
since you last logged on may not be available.

CAUSE

If you have just logged off from another remote access session (RAS) within the last 30 seconds, the logoff process may not have finished fully, thus causing the error to occur.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734 How to Obtain the Latest Windows NT 4.0 Service Pack



WARNING: Using Registry Editor incorrectly can cause serious, system- wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.

Use RegEdt32.exe to add the following information to the Rdr service parameter:

  1. Open to the registry entry:

\HKLM\System\CurrentControlSet\Services\RDR\Paramete

  1. From the Edit Menu, select "Add Value".
  2. Enter FailedConnectTimeout as the Value Name.
  3. Set the Data Type to REG_DWORD, select OK.
  4. Enter 0 (zero) as the data.
  5. Exit Regedt32 and reboot the system for the change to take effect.


STATUS

Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.

Keywords: kbhotfixserver kbqfe kbbug kbfix kbqfe KB185081