Odd laptop issue, after "sleeping"..."No logon servers available..."

[YeOldeStonecat]

Dell Latty e5530 Win7p x64 i5 8 gigs rammage

Member of a domain
Has been properly setup on the clients local network. ..joined to the domain, many times the domain Administrator and some of the users have logged into it.
Users member of local admin group.

So when this laptop is taken out of their office (like on my desk at my office here)...I boot up from a cold start...log in fine, it behaves fine.
I can reboot...and log in fine. Both of these show that the cached credential are all in good shape.

But if I let it sit and doze off for a few minutes, and go wake it up...I'm presented with the locked workstation...as expected, but I go to log in, and I get the "There are no login servers available to service the logon request". Can't log in with any account. However...if I reboot the computer, I can log in no problem.

Have turned off the wireless switch. No diffy.

I actually went onsite to this client this past Friday, saw this error..and I unjoined the domain, cleared the computer account on the server, rejoined the domain, logged in many times...using ethernet cable.

Computer has shown no signs of malware, ran some checks anyways. Really clean computer, less than 9 months old.

Thinking a bug in the wireless NIC drivers.
TCP/IP set to obtain auto. No hard coded DNS.

Fired up local policy and enabled "wait for wireless network before login" setting...to no avail.

Gonna disable "allow Windows to power down this NIC" setting for the wireless....shouldn't have to do that though.

 

[smashedbotatos]

I suspect the NIC driver as well. In my experience Windows 7 sleep and hibernation can make drivers act strange.

Disable the power options for WLAN and LAN. Make sure it is set to sleep not hibernate. Hibernate causes more issues for me than sleep.

 

[FremontPC]

Any chance the A/V could be walking on it?

What model of NIC?

 

[ohio_grad_06]

I'd guess at the power setting for Wi-Fi, and the computer probably doesn't have network when waking up, hence the message.

 

[YeOldeStonecat]

I suspect the NIC driver as well. In my experience Windows 7 sleep and hibernation can make drivers act strange.

Disable the power options for WLAN and LAN. Make sure it is set to sleep not hibernate. Hibernate causes more issues for me than sleep.

Confirmed that disabling power management for the wireless NIC was done, and it did not have any positive effects.

Power management for the onboard wired NIC a bit limited, just the Intel "energy efficient ethernet" setting..I just disabled that and will reboot and let it sit.

Is set to rest after 15 minutes. Confirmed that no Hibernate is allowed, only Sleep.

 

[YeOldeStonecat]

Any chance the A/V could be walking on it?

What model of NIC?

Well...that's an odd answer (antivirus)....yet strangely intriguing. I posed this laptops issue to our main tech, and just a month ago...he had the same exact model Latitude for a town's office we take care of. With N-Ables recent change of antivirus from Panda to BitDefender...that one laptop model, the Latitude e5530, he spent a long time on. Windows would not boot up when BitDefender was pushed out to it. Uninstall..(manual system restore of the reg files)..it ran fine. Reinstall..hang at bootup at the Windows logo (no HDD activity..just a hard stop there)
Did a format/rebuild...same issue. Was a new machine (1x month) before BitDefender was pushed to it.
Ended up sticking a different AV product on that rig just to get it back to him.
This laptop did have an issue after flipping them to BitDefender...but I fully uninstalled it, cleaned it out, all other stuff running fine. (well, had to repair Windows update).

...may be a pave 'n nuke is in order....grrr....

 

[YeOldeStonecat]

After disabling power management on the gigabit NIC...she fell alseep, I woke her up...and "unable to logon..."

 

[altrenda]

do you have a USB nic you can use and disable the internal. At least to localize the problem to the NIC.

 

[FremontPC]

An issue along these lines with an Intel nic and Win8, should there be some bleedover to Win7:

https://downloadcenter.intel.com/De...Id=3299&DwnldID=22026&keyword=82579v&lang=eng

In any case, I wonder where along the line it's getting stopped?

 

[YeOldeStonecat]

do you have a USB nic you can use and disable the internal. At least to localize the problem to the NIC.

Used to..haven't seen it in months..or maybe years, couldn't find it.

 

[YeOldeStonecat]

An issue along these lines with an Intel nic and Win8, should there be some bleedover to Win7:

https://downloadcenter.intel.com/De...Id=3299&DwnldID=22026&keyword=82579v&lang=eng

In any case, I wonder where along the line it's getting stopped?

Will check on that tomorrow...thanks.

Won't be too hard to pave ' nuke...really just had Office, Applied Systems (insurance software), joined domain, printers, a handful of user profiles.
It's just one of those bugs that drives me nuts until I find the cause, and fix. One of those "I refuse to admit defeat" situations...that even though you're 12+ hours into trying to fix it, you can't give in! (no I'm not 12 hours into it...just sayin' )

 

[FremontPC]

"One of those "I refuse to admit defeat" situations..."

I can dig it.

Does the message pop up immediately or does it act like it's actually making an attempt, getting turned down, etc?

 

[YeOldeStonecat]

Does the message pop up immediately or does it act like it's actually making an attempt, getting turned down, etc?

It's fairly quick...wanna say consistently within 3 seconds of typin' the password 'n hitting <enter>

 

[FremontPC]

Hmm. Maybe set up another profile, connect to your shop network (guest, whatever) and see if it does the same thing?

I'm wondering if it even gets past the nic. If so, the server/edge device/etc. must have some record of the attempt?

 

[Laplandz]

Anything in Event viewer?
Also, did you run rsop.msc to see if the interactive logon: require DC auth to unlock... (Computer config>Windows>security>local>security options)

seems odd its after being locked but ok after reboot.

cant agree more on the 12+ hours, the need to solve the puzzle, the "one last try" or "just 5 more minutes" after a couple of hours of colourful language.

 

[YeOldeStonecat]

cant agree more on the 12+ hours, the need to solve the puzzle, the "one last try" or "just 5 more minutes" after a couple of hours of colourful language.

LOl..."colourful language" is right!
I'm out onsite all day today so unable to try things on the laptop, but will be at my office in the morning with a sledgehammer in my left hand, and a blow torch or chain saw in my right hand!

I'll try a few more things before format c:

 

[Majestic]

I had this issue for 2 different reasons.

1) I had a machine that had the same name on the network and I had to change it they were conflicting.
2) The Server did not have a POINTER in the reverse dns (check NSLOOKUP on the workstation and see if it says non-existent domain or not and if it does add a reverse dns entry)

you can also update to the latest network drivers and see if that makes a difference.

I would also put the domain controller as the primary dns and the router as the secondary.

Majestic

Dell Latty e5530 Win7p x64 i5 8 gigs rammage

Member of a domain
Has been properly setup on the clients local network. ..joined to the domain, many times the domain Administrator and some of the users have logged into it.
Users member of local admin group.

So when this laptop is taken out of their office (like on my desk at my office here)...I boot up from a cold start...log in fine, it behaves fine.
I can reboot...and log in fine. Both of these show that the cached credential are all in good shape.

But if I let it sit and doze off for a few minutes, and go wake it up...I'm presented with the locked workstation...as expected, but I go to log in, and I get the "There are no login servers available to service the logon request". Can't log in with any account. However...if I reboot the computer, I can log in no problem.

Have turned off the wireless switch. No diffy.

I actually went onsite to this client this past Friday, saw this error..and I unjoined the domain, cleared the computer account on the server, rejoined the domain, logged in many times...using ethernet cable.

Computer has shown no signs of malware, ran some checks anyways. Really clean computer, less than 9 months old.

Thinking a bug in the wireless NIC drivers.
TCP/IP set to obtain auto. No hard coded DNS.

Fired up local policy and enabled "wait for wireless network before login" setting...to no avail.

Gonna disable "allow Windows to power down this NIC" setting for the wireless....shouldn't have to do that though.