No logon servers available to deal with your request....

[Little-Miss]

or something like that.

 

I fixed it by removing the machine from the domain and adding it again. Simple.

 

But now im left with why? Why did it happen? What exactly did removing and adding it again do?!

[Domino]

See anything in the event log relating to an Schannel error?

[Davit2005]

I had this a few months ago, turned out to be a dodgy Patch cable. Basic testing of pings were ok, I re-imaged was still having same issue and didn't realise cause till I moved machine to another location.

[Little-Miss]

Ooh ok. Yeah i think there were SChannel errors actually....

[unixman_again]

We get this quite regularly on some machines. I've found if I login as local admin and then logoff it's all fixed and there is no need to re-add it to the domain. Why does this fix the problem while rebooting the box doesn't? Dunno. Just one of the strange quirks of W7. We had no problems when the same boxes ran XP.

[SYNACK]

We get this quite regularly on some machines. I've found if I login as local admin and then logoff it's all fixed and there is no need to re-add it to the domain. Why does this fix the problem while rebooting the box doesn't? Dunno. Just one of the strange quirks of W7. We had no problems when the same boxes ran XP.

 

If that works it's probably just not picking up an IP properly at the initial logon screen until a session is started. This is usually drivers or weird firewalls getting in the way, older AV software was terrible for stuff like this.

[Domino]

Ooh ok. Yeah i think there were SChannel errors actually....

 

you can run

netdom reset 'machinename' /domain:'domainname

 

to reset the secure channel to the domain, basically what you're doing with the remove/add anyway.

 

we have them every now and again, but if its a particular machine over and over it's likely indicative of a greater issue.

[witch]

We get this quite regularly on some machines. I've found if I login as local admin and then logoff it's all fixed and there is no need to re-add it to the domain. Why does this fix the problem while rebooting the box doesn't? Dunno. Just one of the strange quirks of W7. We had no problems when the same boxes ran XP.

We get it quite often too, particularly on our wireless netbooks (or any wired machine that has been moved)

Making sure the machines wait for the network helped but it still happens occasionally

[psydii]

To expand on SynAck and Witch's oberservations:

 

Update your BIOS/firmware

Update the NIC Drivers

Install the latest TCP/IP drivers

1) Event ID 5719 and event ID 1129 may be logged when a non-Microsoft DHCP Relay Agent is used

2) TCP SACK option is always set to "true" after you enable the TCP/IP Offloading feature in Windows 7 or in Windows Server 2008 R2

( both required to get the latest stack)

 

Also check that your LAN ports on the switch are set to edge as this ensures that they come up quickly rather that wait for STP to confirm there is no loop.

 

HTH