Windows Forum

Ask something
Discussion Locked

Error when logged on with cached account

0 helpful
5 replies

by patrick.bisaillon

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hello

I have users running WinNT4 Workstation on their laptop. When they are offline (away from the office) and they log on using domain credentials (cached locally), the logon process waits for a Domain Controller to answer but it timeouts after1 minute. Then, they get the following message:

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 availableQuestion #1 (250 Points)
Using a registry hack, is there a way to change this Timeout so that it can be set to a smaller value?

Question #2 (250 Points)
Is there a registry hack available to get rid of the Error/Warning Message described below (my users know they are not connected and we do not use roaming profiles) so I'd like to find a way to prevent this message from showing?

Thanks very much
Patrick

5 replies

by erikdr

Workaround: make sure the local sw is installed for 'all users' and teach the user to logon with a local SAM account when disconnected. They can simply do this by selecting the machine name instead of the domain name in the dropdown box of logon screen...

HTH,

- The Netherlands

by patrick.bisaillon

I prefer not to do this because the next thing you know, they will use the local account when they will be back at the office. Also, neighter Windows 2000 Pro nor Windows XP users experience the issue. Thanks for your help Erik.

by patrick.bisaillon

I decided to use one of my support contract call at Microsoft. For the benefit of Techrepublic's database, here is the info I got for the two questions above.

==== Comments from Microsoft ====
I have searched our database about this behavior. Wecan try the following steps to disable the warning message box.
To do that:
1. Logon the computer with your domain user
2. Go to the registry key:
HKEY_CURRENT_USER\Software\Microsoft\WindowsNT\CurrentVersion\Winlogon
3. Under this key, add the following value:
Value Name: ReportDC
Data Type: REG_DWORD
Data Value: 0
After performing the above steps, let us reboot the computer and logon. You will not get the warning message box.

As to the timeout value, I found the following registry. I have tested it on my computers. However, the improvement is not significant. Currently, the logon time on my computer is about 50 seconds after I set the value as 1.

1. Start Registry Editor (Regedt32.exe) and go to the following subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
2. On the Edit menu, click Add Value.
Value Name: ExpectedDialupDelay
Data Type: Reg_Dword
Data Value is in seconds.
We can set the value as 1 to test.

Meanwhile, I have discussed this issue with our team members. The logon process is hard coded in the system. Though we cached logon, the system still tries to contact DC to logon.
==== Enf of comments from Microsoft ====

This discussion is closed to new replies.