General discussion

Locked

NT Cached Login Problems

By lorelli ·
We have users that take their Windows 2000 laptops out of the office for weeks at a time.

They login to an NT 4.0 Domain when they are in the office. They logon using cached account information when out of the office.

After a while (using the cahced account) they get an error message that states
"Domain Controller could not be found for the specified Domain" and they can't use their machine.

Is there any way to let them continue to use cached credentials?

Thanks for the help.

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

NT Cached Login Problems

by LEGJ1 In reply to NT Cached Login Problems

I found this on Technet for you. I think you will like it!

When you logon to Windows NT using cached logon information, if the domain
controller is unavailable to validate you account, you are unable to access
network resources that require domain validation. However, you are able to
access network resources that do not require domain validation.

Through the registry and a resource kit utility (Regkey.exe), you are able to
change the number of previous logon attempts that a server will cache. By
default, Windows NT will remember the 10 most recent logon attempts. The valid
range of values for this parameter is 0 to 50. A value of 0 disables logon
caching and any value above 50 will only cache 50 logon attempts.

WARNING: Using Registry Editor incorrectly can cause serious problems that may
require you to reinstall your operating system. Microsoft cannot guarantee that
problems resulting from the incorrect use of Registry Editor can be solved. Use
Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys And
Values" online Help topic in Registry Editor (Regedit.exe) or the "Add and
Delete Information in the Registry" and "Edit Registry Data" online Help topics
in Regedt32.exe. Note that you should back up the registry before you edit it.

Cached logon information is controlled by the following key:

HKLM\Software\Microsoft\Windows NT\Current Version\Winlogon\

ValueName: CachedLogonsCount
Data Type: REG_SZ
Values: 0 - 50

Any changes you make to this key require that you restart the computer for the
changes to take effect.

Collapse -

NT Cached Login Problems

by lorelli In reply to NT Cached Login Problems

The post sp2 rollup package seems to have fixed my problem (w2ksp2srp1).

thanks!!!

Collapse -

NT Cached Login Problems

by estebandelatorre In reply to NT Cached Login Problems

I HAVE READ SOMEWHERE THAT USING A CACHE ACCOUNT YOU WILL BE ABLE TO LOGIN A CERTAIN NUMBER OF TIMES.
YOU CAN:
A.- MAKE THE USERS NOT TO CLOSE THE CURRENT SESSION (USING WIN2K HIBERNATE FACILITY)
B.- DEFINE A LOCAL ACCOUNT JUST TO LET USERS USE THE MACHIME WHILE IN HOME.

HOPE IT HELPS-

Collapse -

NT Cached Login Problems

by lorelli In reply to NT Cached Login Problems

The post sp2 rollup package seems to have fixed my problem (w2ksp2srp1).

thanks!!!

Collapse -

NT Cached Login Problems

by lorelli In reply to NT Cached Login Problems

This question was closed by the author

Back to Windows Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums