Win2KPro login with cached profile

Scenario: Windows 2000 Professional logs on a NT 4.0 domain
through a ISDN router (Cisco 803).

Problem: About 50% of each time the user logs on with cached user profile.
That means the login script does not run. Everything else seems okay.
It looks like the Win2K Pro times out too quickly and just logs on
with cached profile. I've tried Microsoft Q163204, but that didn't work.
The client uses WINS and DNS for name resolution.

Could anyone please give me some leads where to look for the solution?
ANY suggestions is VERY appreciated.

Frank Aune
Oslo, Norway
Who is Participating?
SpideyModConnect With a Mentor Commented:
per recommendation

Community Support Moderator @Experts Exchange
why not try to disable using the cached profile, thus enforce the workstation to use the domain, and thus make sure that your login scripts work ...

to disable using the cached profiles, you must edit the registry and do the following on each workstation:

1. Start the registry editor (regedit.exe)
2. Move to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
3. From the Edit menu select New - DWORD value
4. Enter a name of DeleteRoamingCache and press Enter
5. Double click the new value and set to 1
6. Click OK

Best Of Luck | Khaled
I am pretty certain that you can use the local policy under computer management in Win2kpro on an NT4 domain to prevent using cached profiles rather than editing the registry......there are many settings regarding optimising profiles there
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

sure, it does the same job ...

just you dont find the local security policy under the computer management tobyk... it's a stand alone MMC, you can find the local security polcy under the Administrative Tools.

and from the Security Options under Local Policies ... you can set [Number of previous logons to cache (in case domain controller is not available)] to [ 0 ] which means no logons cached... the default is set to 10 logons.

Best Regards | Khaled

ITproAuthor Commented:
Thank you for the suggestions so far.

The real problem is that the login process times out because it doesn't find a domain controller. The 64Kbit line doesn't give the client enough time to find a BDC.

If I disable the cached profile completely the user just doesn't get logged on at all. And that is a bigger problem.

Does anyone know any values to adjust in registry to make the client use longer time to search for a Domain Controller? The dialup router is up and running when the client tries the login and the network connection is working okay. So the BCD is there. I just need to force the client to find it.
have you tried Q207552?
Dear questionner/expert(s)

No comment has been added lately, so it's time to clean up this TA.
I'll leave a recommendation in the Cleanup topic area that this question is to be:

- PAQ'd and pts removed

Please leave any comments here within the next seven days.



Cleanup volunteer
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.