Results 1 to 2 of 2

Thread: Control time limit of cached credentials

  1. #1
    Join Date
    Oct 2005
    Posts
    78

    Control time limit of cached credentials

    There are some users on your network which uses laptop. They are configured in AD. They carry the laptop with them, so to some extent the laptop stays on the network for few time. When there are not on the network and when the login in back the login credential does not work. It looks when they are disconnected from the network the login credential are wiped out. I want to remove this thing. Is there some timeout settings which wipe out the information of AD on those system or it is happening on the server side. What should we do know.

  2. #2
    Join Date
    Sep 2004
    Posts
    208
    I do not think this is some kind of cache expiration issue. I had also noticed the same kind of issue on my network. There are some remote connection where when a system is moved from the network the server no longer recognize the same. If you had enabled password expiration settings on it then you must wipe out that put it on permanent remember. If those things are not expired then user will be able to still login. This can be issue with profile also.

Similar Threads

  1. Replies: 3
    Last Post: 05-09-2011, 10:05 PM
  2. Windows 7 Time limit
    By Ryder in forum Operating Systems
    Replies: 7
    Last Post: 17-04-2009, 10:20 AM
  3. Cached Credentials stop working all of a sudden
    By HarryH in forum Active Directory
    Replies: 5
    Last Post: 16-07-2008, 07:22 PM
  4. cached domain credentials not working
    By Nadeem in forum Windows XP Support
    Replies: 2
    Last Post: 02-07-2008, 02:05 AM
  5. VPN with Vista - cached credentials
    By Damien25 in forum Windows Vista Network
    Replies: 2
    Last Post: 20-04-2008, 05:59 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,714,002,592.00561 seconds with 17 queries