Jump to content

Recommended Posts

Posted

Hi guys,

Im getting a random problem when users are logging on.

All machines and laptops are windows 7 enterprise with server 2008 R2.

I get the error message no logon servers ??

Anyone else experience this?

Posted

It's when the computers can't get to the servers. This could be a lot of things. Wireless dropping out? Switches dropping out? Disconnected cables? etc etc Any thoughts as to when it occurs, or how often?

 

Steve

Posted

Have you enabled the "wait for network" setting in Group Policy?

 

See here:http://www.edugeek.net/forums/windows-7/102325-no-logon-servers-available.html

Posted

The wait for network setting has been enabled, not only is it a wireless issue, but also a wired one aswell.

Looking at a similar thread I will try to rejoin the culprit machines to the domain, next time I am there, as it seems to resolve the issue.

Posted
We get this frequently where patch cables between wall and pc get stretched / bent to much. Replace the lead reboot the pc n problem solved
Posted

Are the clients actually getting an IP address?

Depending on your GP settings (wait for network etc) and locally cached profiles everything could be in place for the connection but you fail to obtain an address.

Check your DHCP lease tables for BAD_ADDRESS entries, this can be a tell tale sign of a network configuration issue.

Delete them and find out why they are being generated.

I have seen so many times where Reservations have been set up wrong or a static address has been entered into a client/device but not excluded from DHCP scope.

In the latter DHCP tries to assign an IP that already exists! This results in DHCP failures, IP conflicts at issue and random errors of this nature.

 

In the most recent of these incidents it was traced to a DHCP configuration error. Yet the symptoms were an intermittent broadcast storm.

During a storm we captured stats indicating the DHCP server was accounting for a high level of ARP requests, on unplugging the DC the Broadcast storm stopped immediately.

A quick check of the server revealed a number of BAD_ADDRESS entries (turned out to be an incomplete reservation assignment by the sysadmin) this was enough to disrupt the entire network as the school still runs a single flat collision domain!

Its amazing how many Sysadmins quick to blame the wifi/switchgear in a blackout when 95% of the the time we find a user error is to blame!

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...