Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
Cached Domain Credentials not working on Windows Server 2003

Unanswered Cached Domain Credentials not working on Windows Server 2003

  • Friday, January 04, 2013 5:55 PM
     
     
    Sign In to Vote
    0

    We have some remote sites without DCs that occasionally experience a network outage, preventing users and computers at those sites from authenticating with a DC. My understanding is that with cached credentials users still ought to be able to log into local servers using RDP from their desktops and thin clients. I tested this scenario in our test lab and was able to RDP into Windows Server 2008 boxes from both thin clients and desktops just fine; however, whenever I tried to RDP into a Windows Server 2003 box I got this error: 

    The System cannot log you on due to the following error:
    The specified domain either does not exist or could not be contacted.

    Please try again or consult your system administrator.

    I have verified that the Local Security Policy on these servers is set to cache the default 10 logins.

    Any suggestions?

    Matthew

     

All Replies

  • Saturday, January 05, 2013 3:32 AM
     
     
    Sign In to Vote
    0

    This sounds more like an issue where there was no DNS resolution. You might try RDP to IP address instead of name.

     

     

     

    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

     
  • Saturday, January 05, 2013 7:27 AM
     
     
    Sign In to Vote
    1

    go to your server and manually check this registry entries and if possible increase to 30 or 20 more than 10

    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current Version\Winlogon\ 
    ValueName: CachedLogonsCount 
    Data Type: REG_SZ 
    Values: 20       (  0 – 50)<.....  can be between 0-50

    http://www.arabitpro.com

     
  • Monday, January 07, 2013 3:55 PM
     
     
    Sign In to Vote
    0
    RDP has no problem finding the server by DNS name. The login prompt comes up and it is after I enter my credentials that I get this error. Could that still be a DNS issue? Will RDPing using a IP address vs a DNS name make any difference on how Windows treats a login?
     
  • Monday, January 07, 2013 5:27 PM
     
     
    Sign In to Vote
    0

    Logging on to a desktop with cached credentials should be no problem, but logging on to RDP session may be a different senario requiring some level of dns name resolution. You might consider these as possibilities.

    http://technet.microsoft.com/en-us/library/cc772234(v=ws.10).aspx

    http://support.microsoft.com/kb/167234

     

     

     

    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

     
  • Monday, January 07, 2013 5:52 PM
     
     
    Sign In to Vote
    0
    We use QIP, not Microsoft's DNS server for DNS resolution. Do you know how the mechanism for logging in via a RDP session using a cached login may have changed between Server 2003 and Server 2008? Whatever is preventing logging into a 2003 box doesn't exist with 2008 as RDP works just fine without DNS in that scenario.
     
  • Monday, January 07, 2013 6:05 PM
     
     
    Sign In to Vote
    1

    They may know that over here.

    http://social.technet.microsoft.com/Forums/en-US/winserverTS/threads

     

     

     

    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.