profile not cached

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Kelnic (anonymous_at_discussions.microsoft.com)
Date: 03/02/04 

Date: Tue, 2 Mar 2004 05:01:06 -0800

Hi Everyone,

  Have a situation, when a machine is connected to a
domain and then the machine is taken off the domain, they
should be able to logon to the domain even if they don't
have an network connection. I am finding some of my
machines can do this and some of them cannot. Any insight
would be greatly appreciated. There is not a policy in
place that would restrict this either.

thanks
kelnic

Relevant Pages

  • Re: Remote Client Configuration
    ... Thanks for quickly updates. ... Just as I know, if you only logon the domain with cache credential, the ... group policy will not be updates, instead it will use the old policy that ... dial up VPN connection to logon SBS domain once-in-a-while for the group ...
    (microsoft.public.windows.server.sbs)
  • Re: APPN Connection z/os - AHHC / LLC2.
    ... The sequence of logon is: Normally we have, after the initial logon screen from TSO: ... The connection is not dropped after the "hung", I cancel the user P390A, logon again, the same results. ... established, specifically a TSO session. ... For IBM-MAIN subscribe / signoff / archive access instructions, ...
    (bit.listserv.ibm-main)
  • Re: Permit only one network logon per user
    ... intend to prevent a second local login. ... allow a second connection to it using the same creds. ... network logon per user. ... logoff event is not signalled and the ref count never decreases. ...
    (microsoft.public.windows.server.security)
  • Re: Permit only one network logon per user
    ... intend to prevent a second local login. ... allow a second connection to it using the same creds. ... network logon per user. ...
    (microsoft.public.windows.server.security)
  • Re: Cached Credentials causing problems with shares?
    ... logon to the machine locally and then connect to the shares over the ... is almost like the cached credentials are interfering in some way. ... does have a connection with the DC. ... it sounds like the tickets ...
    (microsoft.public.windows.server.active_directory)