Article ID: 814686 - Last Review: March 31, 2003 - Revision: 1.2 Password Expires Without Notification Over Remote Access Connection to Windows NT 4.0 Domain
IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that you
understand how to restore the registry if a problem occurs. For information
about how to back up, restore, and edit the registry, click the following
article number to view the article in the Microsoft Knowledge Base: 256986
(http://support.microsoft.com/kb/256986/EN-US/
)
Description of the Microsoft Windows Registry SYMPTOMSWhen you use the Remote Access Service (RAS) to log on to a
Microsoft Windows NT 4.0 domain, your password may expire although you have not
received the expected password expiry notification. CAUSE This problem occurs because in Microsoft Windows XP, your
cached credentials are used initially to log you on. A routine then runs in the
background to examine the attributes of your credentials and it may detect that
your password is going to expire. If the current date is in the limit that is
set for password expiry notification, the routine sets a value in the registry
to prevent you from logging on with cached credentials. The next time that you
log on to the domain, the password expiry notification dialog appears.
However, Netlogon tries to log the user on to the Windows NT 4.0 domain before a new transport is available for use. The default time for this procedure is 3000 milliseconds. This seems to be too quick for the Transport Driver Interface (TDI) to return the new transport to Netlogon with the result that background authentication fails. RESOLUTION To resolve this problem, edit the registry to extend the
time that Windows XP waits for a new transport to 10,000 milliseconds. To do
this, follow these steps. WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
STATUS Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
| Other Resources Other Support Sites
CommunityGet Help NowArticle Translations
|






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top
