There are currently no logon servers available to service the logon when unlocking a computer
Hello all, I got a new DELL Laptop with Windows 7 Ultimate 32Bit pre-installed. The laptop is part of a Windows AD environment with Server 2003 R2 DC's. The problem is: When I lock the computer and try to unlock it, with no network connection to a DC, Windows tells me that There are currently no logon servers available to service the logon. What I already did: - Boot with no network connection to a DC and try to login with a previously logged in domain user: works. So logon caching seems to be ok. - Delete and recreate user account: didn't fix it. - Delete and recreate computer account: didn't fix it. - Check policy settings interactive logon require domain controller authentication to unlock workstation set to deactivated: didn't fix it. - Check policy settings interactive logon number of previous logons to cache set to 50: didn't fix it. - Check above policy settings in GPO (and set them via GPO): didn't fix it. - Check HKLM\Software\Microsoft\Windows NT\Current Version\Winlogon\CachedLogonsCount set to 50 and ForceUnlockLogon set to 0: didn't fix it. BTW: The message appears immediately, so I suppose Windows doesn't even check for a DC - well it can't without network but I wanted to mention it. Since I don't want to give up and re-install the system any help would be really appreciated.
May 3rd, 2012 8:28am

When you go to control panel > user accounts > Manage user accounts Do you have the user name here and the Domain is the domain name of your AD?
Free Windows Admin Tool Kit Click here and download it now
May 3rd, 2012 8:50am

When you go to control panel > user accounts > Manage user accounts Do you have the user name here and the Domain is the domain name of your AD?
May 3rd, 2012 8:50am

Yes. Both, user and domain are visible and correct. The user is also part of the local admin group. I guess if this was wrong, I couldnt login either, when booting without network cable.
Free Windows Admin Tool Kit Click here and download it now
May 3rd, 2012 9:01am

Yes. Both, user and domain are visible and correct. The user is also part of the local admin group. I guess if this was wrong, I couldnt login either, when booting without network cable.
May 3rd, 2012 9:01am

whats the event id given in the event log?"
Free Windows Admin Tool Kit Click here and download it now
May 3rd, 2012 9:19am

whats the event id given in the event log?"
May 3rd, 2012 9:19am

I think the corresponding ID is 4625 FailureReason %%2304 LogonType 7
Free Windows Admin Tool Kit Click here and download it now
May 3rd, 2012 9:39am

have you tried disabling ipv6 in the network properties? http://www.ultimatewindowssecurity.com/securitylog/encyclopedia/event.aspx?eventid=4625 also check that out
May 3rd, 2012 10:03am

Yap. Is disabled. Also tried fixed ipv4 ip.
Free Windows Admin Tool Kit Click here and download it now
May 3rd, 2012 10:12am

Yap. Is disabled. Also tried fixed ipv4 ip.
May 3rd, 2012 10:12am

can you give me the other information in the event id. the extended info under it.
Free Windows Admin Tool Kit Click here and download it now
May 3rd, 2012 10:26am

can you give me the other information in the event id. the extended info under it.
May 3rd, 2012 10:26am

Sorry, I'm already out of office. Will post it tomorrow. Thank you for your hints so far!
Free Windows Admin Tool Kit Click here and download it now
May 3rd, 2012 11:13am

Sorry, I'm already out of office. Will post it tomorrow. Thank you for your hints so far!
May 3rd, 2012 11:13am

Not Working: Protokollname: Security Quelle: Microsoft-Windows-Security-Auditing Datum: 03.05.2012 18:24:33 Ereignis-ID: 4625 Aufgabenkategorie:Anmelden Ebene: Informationen Schlsselwrter:berwachung gescheitert Benutzer: Nicht zutreffend Computer: COMPUTER.CONTOSO.de Beschreibung: Fehler beim Anmelden eines Kontos. Antragsteller: Sicherheits-ID: SYSTEM Kontoname: COMPUTER$ Kontodomne: CONTOSO Anmelde-ID: 0x3e7 Anmeldetyp: 7 Konto, fr das die Anmeldung fehlgeschlagen ist: Sicherheits-ID: NULL SID Kontoname: AccountName Kontodomne: CONTOSO Fehlerinformationen: Fehlerursache: Bei der Anmeldung ist ein Fehler aufgetreten. Status: 0xc0a00002 Unterstatus:: 0x0 Prozessinformationen: Aufrufprozess-ID: 0x1d00 Aufrufprozessname: C:\Windows\System32\winlogon.exe Netzwerkinformationen: Arbeitsstationsname: COMPUTER Quellnetzwerkadresse: 127.0.0.1 Quellport: 0 Detaillierte Authentifizierungsinformationen: Anmeldeprozess: User32 Authentifizierungspaket: Wave Authentication Package bertragene Dienste: - Paketname (nur NTLM): - Schlssellnge: 0 Dieses Ereignis wird beim Erstellen einer Anmeldesitzung generiert. Es wird auf dem Computer generiert, auf den zugegriffen wurde. Die Antragstellerfelder geben das Konto auf dem lokalen System an, von dem die Anmeldung angefordert wurde. Dies ist meistens ein Dienst wie der Serverdienst oder ein lokaler Prozess wie "Winlogon.exe" oder "Services.exe". Das Anmeldetypfeld gibt den jeweiligen Anmeldetyp an. Die hufigsten Typen sind 2 (interaktiv) und 3 (Netzwerk). Die Felder fr die Prozessinformationen geben den Prozess und das Konto an, fr die die Anmeldung angefordert wurde. Die Netzwerkfelder geben die Quelle einer Remoteanmeldeanforderung an. Der Arbeitsstationsname ist nicht immer verfgbar und kann in manchen Fllen leer bleiben. Die Felder fr die Authentifizierungsinformationen enthalten detaillierte Informationen zu dieser speziellen Anmeldeanforderung. - Die bertragenen Dienste geben an, welche Zwischendienste an der Anmeldeanforderung beteiligt waren. - Der Paketname gibt das in den NTLM-Protokollen verwendete Unterprotokoll an. - Die Schlssellnge gibt die Lnge des generierten Sitzungsschlssels an. Wenn kein Sitzungsschlssel angefordert wurde, ist dieser Wert 0. Ereignis-XML: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" /> <EventID>4625</EventID> <Version>0</Version> <Level>0</Level> <Task>12544</Task> <Opcode>0</Opcode> <Keywords>0x8010000000000000</Keywords> <TimeCreated SystemTime="2012-05-03T16:24:33.692754600Z" /> <EventRecordID>114390</EventRecordID> <Correlation /> <Execution ProcessID="788" ThreadID="7592" /> <Channel>Security</Channel> <Computer>COMPUTER.CONTOSO.de</Computer> <Security /> </System> <EventData> <Data Name="SubjectUserSid">S-1-5-18</Data> <Data Name="SubjectUserName">COMPUTER$</Data> <Data Name="SubjectDomainName">CONTOSO</Data> <Data Name="SubjectLogonId">0x3e7</Data> <Data Name="TargetUserSid">S-1-0-0</Data> <Data Name="TargetUserName">AccountName</Data> <Data Name="TargetDomainName">CONTOSO</Data> <Data Name="Status">0xc0a00002</Data> <Data Name="FailureReason">%%2304</Data> <Data Name="SubStatus">0x0</Data> <Data Name="LogonType">7</Data> <Data Name="LogonProcessName">User32 </Data> <Data Name="AuthenticationPackageName">Wave Authentication Package</Data> <Data Name="WorkstationName">COMPUTER</Data> <Data Name="TransmittedServices">-</Data> <Data Name="LmPackageName">-</Data> <Data Name="KeyLength">0</Data> <Data Name="ProcessId">0x1d00</Data> <Data Name="ProcessName">C:\Windows\System32\winlogon.exe</Data> <Data Name="IpAddress">127.0.0.1</Data> <Data Name="IpPort">0</Data> </EventData> </Event> Working (with network connected): Protokollname: Security Quelle: Microsoft-Windows-Security-Auditing Datum: 04.05.2012 07:12:50 Ereignis-ID: 4624 Aufgabenkategorie:Anmelden Ebene: Informationen Schlsselwrter:berwachung erfolgreich Benutzer: Nicht zutreffend Computer: COMPUTER.CONTOSO.de Beschreibung: Ein Konto wurde erfolgreich angemeldet. Antragsteller: Sicherheits-ID: SYSTEM Kontoname: COMPUTER$ Kontodomne: CONTOSO Anmelde-ID: 0x3e7 Anmeldetyp: 7 Neue Anmeldung: Sicherheits-ID: CONTOSO\AccountName Kontoname: AccountName Kontodomne: CONTOSO Anmelde-ID: 0x2111590 Anmelde-GUID: {00000000-0000-0000-0000-000000000000} Prozessinformationen: Prozess-ID: 0x1d00 Prozessname: C:\Windows\System32\winlogon.exe Netzwerkinformationen: Arbeitsstationsname: COMPUTER Quellnetzwerkadresse: 127.0.0.1 Quellport: 0 Detaillierte Authentifizierungsinformationen: Anmeldeprozess: User32 Authentifizierungspaket: Wave Authentication Package bertragene Dienste: - Paketname (nur NTLM): - Schlssellnge: 0 Dieses Ereignis wird beim Erstellen einer Anmeldesitzung generiert. Es wird auf dem Computer generiert, auf den zugegriffen wurde. Die Antragstellerfelder geben das Konto auf dem lokalen System an, von dem die Anmeldung angefordert wurde. Dies ist meistens ein Dienst wie der Serverdienst oder ein lokaler Prozess wie "Winlogon.exe" oder "Services.exe". Das Anmeldetypfeld gibt den jeweiligen Anmeldetyp an. Die hufigsten Typen sind 2 (interaktiv) und 3 (Netzwerk). Die Felder fr die neue Anmeldung geben das Konto an, fr das die Anmeldung erstellt wurde, d. h. das angemeldete Konto. Die Netzwerkfelder geben die Quelle einer Remoteanmeldeanforderung an. der Arbeitsstationsname ist nicht immer verfgbar und kann in manchen Fllen leer bleiben. Die Felder fr die Authentifizierungsinformationen enthalten detaillierte Informationen zu dieser speziellen Anmeldeanforderung. - Die Anmelde-GUID ist ein eindeutiger Bezeichner, der verwendet werden kann, um dieses Ereignis mit einem KDC-Ereignis zu korrelieren. - Die bertragenen Dienste geben an, welche Zwischendienste an der Anmeldeanforderung beteiligt waren. - Der Paketname gibt das in den NTLM-Protokollen verwendete Unterprotokoll an. - Die Schlssellnge gibt die Lnge des generierten Sitzungsschlssels an. Wenn kein Sitzungsschlssel angefordert wurde, ist dieser Wert 0. Ereignis-XML: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" /> <EventID>4624</EventID> <Version>0</Version> <Level>0</Level> <Task>12544</Task> <Opcode>0</Opcode> <Keywords>0x8020000000000000</Keywords> <TimeCreated SystemTime="2012-05-04T05:12:50.148555600Z" /> <EventRecordID>115412</EventRecordID> <Correlation /> <Execution ProcessID="788" ThreadID="4908" /> <Channel>Security</Channel> <Computer>COMPUTER.CONTOSO.de</Computer> <Security /> </System> <EventData> <Data Name="SubjectUserSid">S-1-5-18</Data> <Data Name="SubjectUserName">COMPUTER$</Data> <Data Name="SubjectDomainName">CONTOSO</Data> <Data Name="SubjectLogonId">0x3e7</Data> <Data Name="TargetUserSid">S-1-5-21-682003330-1682526488-1343024091-3608</Data> <Data Name="TargetUserName">AccountName</Data> <Data Name="TargetDomainName">CONTOSO</Data> <Data Name="TargetLogonId">0x2111590</Data> <Data Name="LogonType">7</Data> <Data Name="LogonProcessName">User32 </Data> <Data Name="AuthenticationPackageName">Wave Authentication Package</Data> <Data Name="WorkstationName">COMPUTER</Data> <Data Name="LogonGuid">{00000000-0000-0000-0000-000000000000}</Data> <Data Name="TransmittedServices">-</Data> <Data Name="LmPackageName">-</Data> <Data Name="KeyLength">0</Data> <Data Name="ProcessId">0x1d00</Data> <Data Name="ProcessName">C:\Windows\System32\winlogon.exe</Data> <Data Name="IpAddress">127.0.0.1</Data> <Data Name="IpPort">0</Data> </EventData> </Event> I think the Wave Authentication Package is because of an installed onboard SmartCard/fingerprint reader. I already uninstalled DELL's prequisites, driver, middleware and application packages but the failure persisted. So I reinstalled the packages again.
Free Windows Admin Tool Kit Click here and download it now
May 4th, 2012 1:58am

Not Working: Protokollname: Security Quelle: Microsoft-Windows-Security-Auditing Datum: 03.05.2012 18:24:33 Ereignis-ID: 4625 Aufgabenkategorie:Anmelden Ebene: Informationen Schlsselwrter:berwachung gescheitert Benutzer: Nicht zutreffend Computer: COMPUTER.CONTOSO.de Beschreibung: Fehler beim Anmelden eines Kontos. Antragsteller: Sicherheits-ID: SYSTEM Kontoname: COMPUTER$ Kontodomne: CONTOSO Anmelde-ID: 0x3e7 Anmeldetyp: 7 Konto, fr das die Anmeldung fehlgeschlagen ist: Sicherheits-ID: NULL SID Kontoname: AccountName Kontodomne: CONTOSO Fehlerinformationen: Fehlerursache: Bei der Anmeldung ist ein Fehler aufgetreten. Status: 0xc0a00002 Unterstatus:: 0x0 Prozessinformationen: Aufrufprozess-ID: 0x1d00 Aufrufprozessname: C:\Windows\System32\winlogon.exe Netzwerkinformationen: Arbeitsstationsname: COMPUTER Quellnetzwerkadresse: 127.0.0.1 Quellport: 0 Detaillierte Authentifizierungsinformationen: Anmeldeprozess: User32 Authentifizierungspaket: Wave Authentication Package bertragene Dienste: - Paketname (nur NTLM): - Schlssellnge: 0 Dieses Ereignis wird beim Erstellen einer Anmeldesitzung generiert. Es wird auf dem Computer generiert, auf den zugegriffen wurde. Die Antragstellerfelder geben das Konto auf dem lokalen System an, von dem die Anmeldung angefordert wurde. Dies ist meistens ein Dienst wie der Serverdienst oder ein lokaler Prozess wie "Winlogon.exe" oder "Services.exe". Das Anmeldetypfeld gibt den jeweiligen Anmeldetyp an. Die hufigsten Typen sind 2 (interaktiv) und 3 (Netzwerk). Die Felder fr die Prozessinformationen geben den Prozess und das Konto an, fr die die Anmeldung angefordert wurde. Die Netzwerkfelder geben die Quelle einer Remoteanmeldeanforderung an. Der Arbeitsstationsname ist nicht immer verfgbar und kann in manchen Fllen leer bleiben. Die Felder fr die Authentifizierungsinformationen enthalten detaillierte Informationen zu dieser speziellen Anmeldeanforderung. - Die bertragenen Dienste geben an, welche Zwischendienste an der Anmeldeanforderung beteiligt waren. - Der Paketname gibt das in den NTLM-Protokollen verwendete Unterprotokoll an. - Die Schlssellnge gibt die Lnge des generierten Sitzungsschlssels an. Wenn kein Sitzungsschlssel angefordert wurde, ist dieser Wert 0. Ereignis-XML: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" /> <EventID>4625</EventID> <Version>0</Version> <Level>0</Level> <Task>12544</Task> <Opcode>0</Opcode> <Keywords>0x8010000000000000</Keywords> <TimeCreated SystemTime="2012-05-03T16:24:33.692754600Z" /> <EventRecordID>114390</EventRecordID> <Correlation /> <Execution ProcessID="788" ThreadID="7592" /> <Channel>Security</Channel> <Computer>COMPUTER.CONTOSO.de</Computer> <Security /> </System> <EventData> <Data Name="SubjectUserSid">S-1-5-18</Data> <Data Name="SubjectUserName">COMPUTER$</Data> <Data Name="SubjectDomainName">CONTOSO</Data> <Data Name="SubjectLogonId">0x3e7</Data> <Data Name="TargetUserSid">S-1-0-0</Data> <Data Name="TargetUserName">AccountName</Data> <Data Name="TargetDomainName">CONTOSO</Data> <Data Name="Status">0xc0a00002</Data> <Data Name="FailureReason">%%2304</Data> <Data Name="SubStatus">0x0</Data> <Data Name="LogonType">7</Data> <Data Name="LogonProcessName">User32 </Data> <Data Name="AuthenticationPackageName">Wave Authentication Package</Data> <Data Name="WorkstationName">COMPUTER</Data> <Data Name="TransmittedServices">-</Data> <Data Name="LmPackageName">-</Data> <Data Name="KeyLength">0</Data> <Data Name="ProcessId">0x1d00</Data> <Data Name="ProcessName">C:\Windows\System32\winlogon.exe</Data> <Data Name="IpAddress">127.0.0.1</Data> <Data Name="IpPort">0</Data> </EventData> </Event> Working (with network connected): Protokollname: Security Quelle: Microsoft-Windows-Security-Auditing Datum: 04.05.2012 07:12:50 Ereignis-ID: 4624 Aufgabenkategorie:Anmelden Ebene: Informationen Schlsselwrter:berwachung erfolgreich Benutzer: Nicht zutreffend Computer: COMPUTER.CONTOSO.de Beschreibung: Ein Konto wurde erfolgreich angemeldet. Antragsteller: Sicherheits-ID: SYSTEM Kontoname: COMPUTER$ Kontodomne: CONTOSO Anmelde-ID: 0x3e7 Anmeldetyp: 7 Neue Anmeldung: Sicherheits-ID: CONTOSO\AccountName Kontoname: AccountName Kontodomne: CONTOSO Anmelde-ID: 0x2111590 Anmelde-GUID: {00000000-0000-0000-0000-000000000000} Prozessinformationen: Prozess-ID: 0x1d00 Prozessname: C:\Windows\System32\winlogon.exe Netzwerkinformationen: Arbeitsstationsname: COMPUTER Quellnetzwerkadresse: 127.0.0.1 Quellport: 0 Detaillierte Authentifizierungsinformationen: Anmeldeprozess: User32 Authentifizierungspaket: Wave Authentication Package bertragene Dienste: - Paketname (nur NTLM): - Schlssellnge: 0 Dieses Ereignis wird beim Erstellen einer Anmeldesitzung generiert. Es wird auf dem Computer generiert, auf den zugegriffen wurde. Die Antragstellerfelder geben das Konto auf dem lokalen System an, von dem die Anmeldung angefordert wurde. Dies ist meistens ein Dienst wie der Serverdienst oder ein lokaler Prozess wie "Winlogon.exe" oder "Services.exe". Das Anmeldetypfeld gibt den jeweiligen Anmeldetyp an. Die hufigsten Typen sind 2 (interaktiv) und 3 (Netzwerk). Die Felder fr die neue Anmeldung geben das Konto an, fr das die Anmeldung erstellt wurde, d. h. das angemeldete Konto. Die Netzwerkfelder geben die Quelle einer Remoteanmeldeanforderung an. der Arbeitsstationsname ist nicht immer verfgbar und kann in manchen Fllen leer bleiben. Die Felder fr die Authentifizierungsinformationen enthalten detaillierte Informationen zu dieser speziellen Anmeldeanforderung. - Die Anmelde-GUID ist ein eindeutiger Bezeichner, der verwendet werden kann, um dieses Ereignis mit einem KDC-Ereignis zu korrelieren. - Die bertragenen Dienste geben an, welche Zwischendienste an der Anmeldeanforderung beteiligt waren. - Der Paketname gibt das in den NTLM-Protokollen verwendete Unterprotokoll an. - Die Schlssellnge gibt die Lnge des generierten Sitzungsschlssels an. Wenn kein Sitzungsschlssel angefordert wurde, ist dieser Wert 0. Ereignis-XML: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" /> <EventID>4624</EventID> <Version>0</Version> <Level>0</Level> <Task>12544</Task> <Opcode>0</Opcode> <Keywords>0x8020000000000000</Keywords> <TimeCreated SystemTime="2012-05-04T05:12:50.148555600Z" /> <EventRecordID>115412</EventRecordID> <Correlation /> <Execution ProcessID="788" ThreadID="4908" /> <Channel>Security</Channel> <Computer>COMPUTER.CONTOSO.de</Computer> <Security /> </System> <EventData> <Data Name="SubjectUserSid">S-1-5-18</Data> <Data Name="SubjectUserName">COMPUTER$</Data> <Data Name="SubjectDomainName">CONTOSO</Data> <Data Name="SubjectLogonId">0x3e7</Data> <Data Name="TargetUserSid">S-1-5-21-682003330-1682526488-1343024091-3608</Data> <Data Name="TargetUserName">AccountName</Data> <Data Name="TargetDomainName">CONTOSO</Data> <Data Name="TargetLogonId">0x2111590</Data> <Data Name="LogonType">7</Data> <Data Name="LogonProcessName">User32 </Data> <Data Name="AuthenticationPackageName">Wave Authentication Package</Data> <Data Name="WorkstationName">COMPUTER</Data> <Data Name="LogonGuid">{00000000-0000-0000-0000-000000000000}</Data> <Data Name="TransmittedServices">-</Data> <Data Name="LmPackageName">-</Data> <Data Name="KeyLength">0</Data> <Data Name="ProcessId">0x1d00</Data> <Data Name="ProcessName">C:\Windows\System32\winlogon.exe</Data> <Data Name="IpAddress">127.0.0.1</Data> <Data Name="IpPort">0</Data> </EventData> </Event> I think the Wave Authentication Package is because of an installed onboard SmartCard/fingerprint reader. I already uninstalled DELL's prequisites, driver, middleware and application packages but the failure persisted. So I reinstalled the packages again.
May 4th, 2012 1:58am

Hi, Do you find the message "There are currently no logon servers available to service the logon" from Event 5719 in System Event? If not, could you paste the full message here? Is it VPN related? Based on my experience, it usually happens when the netlogon service starts up while the lower level of network driver is still being initialized. In other words, the underlying network hasn't been ready before the netlogon service begins to start. After the network is fully ready, certainly everything is back to normal again and thus we may not notice any impacts at all. So, if users can logon and normally access network resources, we can safely ignore the event. Please try the following KB to do the optimization: http://support.microsoft.com/kb/938449 Thanks, BrianPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
May 8th, 2012 2:40am

Hi, Do you find the message "There are currently no logon servers available to service the logon" from Event 5719 in System Event? If not, could you paste the full message here? Is it VPN related? Based on my experience, it usually happens when the netlogon service starts up while the lower level of network driver is still being initialized. In other words, the underlying network hasn't been ready before the netlogon service begins to start. After the network is fully ready, certainly everything is back to normal again and thus we may not notice any impacts at all. So, if users can logon and normally access network resources, we can safely ignore the event. Please try the following KB to do the optimization: http://support.microsoft.com/kb/938449 Thanks, BrianPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
May 8th, 2012 2:40am

Hello Brian, sorry for the late reply. The problem is neither VPN nor timing related, since there is no VPN connection. I think timing also wasnt't the problem, because it worked when I connected an ethernet cable and didn't when I unplugged it (the network card was set not to disable, when the cable is unplugged). Finally I gave up. I formatted the DELL install and reinstalled. Now everything is working fine but it isn't really satisfying.
Free Windows Admin Tool Kit Click here and download it now
May 14th, 2012 1:56am

Hello Brian, sorry for the late reply. The problem is neither VPN nor timing related, since there is no VPN connection. I think timing also wasnt't the problem, because it worked when I connected an ethernet cable and didn't when I unplugged it (the network card was set not to disable, when the cable is unplugged). Finally I gave up. I formatted the DELL install and reinstalled. Now everything is working fine but it isn't really satisfying.
May 14th, 2012 1:56am

if you are in a domain, you have to be connected to the local network of the domain to log in to that account unless roaming profiles is enabled for that domain. Please make sure you push your ethernet cord in all the way, or you are connected to a wirelessly to the appropreiate network. Let me know if this helps.
Free Windows Admin Tool Kit Click here and download it now
May 14th, 2012 10:51pm

if you are in a domain, you have to be connected to the local network of the domain to log in to that account unless roaming profiles is enabled for that domain. Please make sure you push your ethernet cord in all the way, or you are connected to a wirelessly to the appropreiate network. Let me know if this helps.
May 14th, 2012 10:51pm

Hello The Moore, as stated in my first post: Boot with no network connection to a DC and try to login with a previously logged in domain user: works. So logon caching seems to be ok Logon caching is enabled for all user accounts in my domain, just didn't work on this notebook... Well until I reinstalled.
Free Windows Admin Tool Kit Click here and download it now
May 15th, 2012 12:37am

Hello The Moore, as stated in my first post: Boot with no network connection to a DC and try to login with a previously logged in domain user: works. So logon caching seems to be ok Logon caching is enabled for all user accounts in my domain, just didn't work on this notebook... Well until I reinstalled.
May 15th, 2012 12:37am

Thanks Christian, Sorry, it's worded differently than I would have written it. Did you reinstall the OS with the re-installation cd's from the computers manufacture, or was it a different CD, like an OEM, retail, or OA? Also did you reinstall all of the factory applications, and drivers that came with it after you reformatted the system, & it works now? Just curious. Did you run AV's on your laptop that was having issues? what AV's? Did you run a hard drive test to determine any hard drive errors or possible corruption? If you formatted, those bad sectors could have been over written unless its permanently damaged. I recommend the Hirens bootable Live CD, or bootable USB for testing hardware and diagnostics http://www.hiren.info/pages/bootcd did you run sfc /scannow in cmd? system restore? if it failed, did you manually reinstall the registry by finding the restore point in the windows folder, and manually copying and pasting it back into its original location? So was this a wireless connection you were attempting to connect through, because you said it worked while connecting through the Ethernet nic, right? Are you running RRAS on the server? Is EAP configured with the biometric scanner/smart card for another form of authentication? also was group policy implemented, and was the user account that couldn't log on in everyone else's group?
Free Windows Admin Tool Kit Click here and download it now
May 15th, 2012 2:04am

Finally I gave up. I formatted the DELL install and reinstalled. Now everything is working fine but it isn't really satisfying. I'm having the same issue with a new Dell laptop. Was anyone able to give you a better answer to this issue? I'd prefer to avoid reinstalling everything if I could.
July 18th, 2012 11:07am

Sorry to answer so late, but I was a little bit - lets say - frustrated: Thanks Christian, Sorry, it's worded differently than I would have written it. My English is really terrible, so I have to apologyze for making it so complicated for you to read my stuff. Did you reinstall the OS with the re-installation cd's from the computers manufacture, or was it a different CD, like an OEM, retail, or OA? I used the companies volume license Win 7 installation. Didn't want to mess around with the DELL install media anymore. Also did you reinstall all of the factory applications, and drivers that came with it after you reformatted the system, & it works now? Yup, did a complete install of all drivers from the DELL website like I did before Just curious. Did you run AV's on your laptop that was having issues? what AV's? We use TrendMicro OfficeScan company wide. Don't think its causing the problems because all other computers run it too . Did you run a hard drive test to determine any hard drive errors or possible corruption? If you formatted, those bad sectors could have been over written unless its permanently damaged. I didn't run a check but I only made a quick format. Don't know if that would also fix any corrupted sectors... or if it would have to since the HD was an SSD. I recommend the Hirens bootable Live CD, or bootable USB for testing hardware and diagnostics http://www.hiren.info/pages/bootcd I'll give it a try next time. did you run sfc /scannow in cmd? No. system restore? if it failed, did you manually reinstall the registry by finding the restore point in the windows folder, and manually copying and pasting it back into its original location? Did a system restore. No change. So was this a wireless connection you were attempting to connect through, because you said it worked while connecting through the Ethernet nic, right? I had no network connection at all. The problem was that Windows didn't let the user login without any kind of network connection to one of the DCs Are you running RRAS on the server? Is EAP configured with the biometric scanner/smart card for another form of authentication? No RRAS on the server. Problem consistet with and without DELL biometrics enabled. Infact I completely uninstalled all DELL biometrics software and drivers to test it. also was group policy implemented, and was the user account that couldn't log on in everyone else's group? We only have two policies (server / everything else). The laptop was in the everything else group.
Free Windows Admin Tool Kit Click here and download it now
July 19th, 2012 4:33am

Finally I gave up. I formatted the DELL install and reinstalled. Now everything is working fine but it isn't really satisfying. I'm having the same issue with a new Dell laptop. Was anyone able to give you a better answer to this issue? I'd prefer to avoid reinstalling everything if I could. Good luck man. I'd really appreciate if you find an answer. I tend to blame DELL for the trouble. What kind of laptop do you have? Latitude E Series with biometrics (fingerprint reader)? Mine was a DELL Latitude E6540.
July 19th, 2012 4:35am

I have a Dell Precision M4600 without biometrics. I just received it last week and started setting it up. I joined it to the domain like I have many others, but unlike those others it won't cache the domain logon info for more than 5 or 10 minutes. I keep having to log on as a local admin, connect the VPN, then switch users, log on as a domain user, switch back to the local admin, disconnect the VPN, quickly switch back to the domain user, and log on again (a delay is introduced here while it tries to authenticate the user). Other Dell Precisions and Latitudes I've purchased have not had this problem, but perhaps this is a recent issue as the previous purchases happened roughly 6 months ago or more. Installed on the laptop was Windows 7 Professional x64 SP1.
Free Windows Admin Tool Kit Click here and download it now
July 19th, 2012 1:19pm

I called Dell and worked with their tech support. I let them know that others were having this issue as well, even forwarding the support tech this thread. She thoroughly reviewed it and then asked if I had tried removing the computer from the domain and re-adding it because it wasn't mentioned as one of the methods attempted previously. I said I hadn't tried it. So I tried it. And, so far, it has worked. Previously I wouldn't be able to be disconnected for longer than 10 minutes and still log in... but just this evening I shut the machine down for over two hours and was able to boot it up and log in using my domain account without being connected to the network. Hope this helps someone in the future. :) Just remove the computer from the domain and add it back. chris.
July 19th, 2012 11:04pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics