+ Post New Thread
Page 1 of 2 12 LastLast
Results 1 to 15 of 24
Windows Server 2008 R2 Thread, No logon servers available to process logon request in Technical; I am seeing this on my network a lot more than I should. 90% of my clients are wireless and ...
  1. #1

    RabbieBurns's Avatar
    Join Date
    Apr 2008
    Location
    Sydney
    Posts
    5,512
    Thank Post
    1,320
    Thanked 469 Times in 306 Posts
    Blog Entries
    6
    Rep Power
    199

    No logon servers available to process logon request

    I am seeing this on my network a lot more than I should. 90% of my clients are wireless and i have been putting massive resources into resolving any possible wireless issues, but Im seeing these on a few too many desktops now which is starting to raise concerns.

    I have the FSMO PDC which is a physical box, and I have 2 virtual DC's which are on the same SAN but on 2 different hosts.

    What would i be looking for on my network which would cause a client to be unable to authenticate with either 3 of the DCs ?

  2. #2

    FN-GM's Avatar
    Join Date
    Jun 2007
    Location
    UK
    Posts
    15,828
    Thank Post
    875
    Thanked 1,675 Times in 1,458 Posts
    Blog Entries
    12
    Rep Power
    444
    I would start looking at DNS. Does everything look healthy there?

  3. Thanks to FN-GM from:

    RabbieBurns (28th May 2012)

  4. #3
    soveryapt's Avatar
    Join Date
    Jan 2009
    Location
    Lancashire
    Posts
    2,402
    Thank Post
    648
    Thanked 277 Times in 244 Posts
    Rep Power
    78
    I had this for a while. I found out it was our AV software (Sophos) that was temporarily disabling the network cards on boot up which mean if you logged on too quickly, it didn't see the servers and reported that problem, but you waited another minute then it was able to log on.

    When this happens now, it only seems to be on laptops when someone has disable the wireless, so I don't know if that was the only issue, but it just seemed to be a time thing.

  5. Thanks to soveryapt from:

    RabbieBurns (28th May 2012)

  6. #4

    SYNACK's Avatar
    Join Date
    Oct 2007
    Posts
    11,072
    Thank Post
    853
    Thanked 2,676 Times in 2,270 Posts
    Blog Entries
    9
    Rep Power
    769
    Yea, check the network stack. It's likely to be IP based due to drivers taking too long to resolve an initial IP connection. With wireless make sure that the wireless profiles are machine based not using user credentials.

    You could also try something like this although it may have some side effects:
    Quote Originally Posted by MaximusR View Post
    Hi There,
    We had the same issues.
    This link might have the answer - /var/log/metasplo.it: Windows 7 wireless NIC not initializing before netlogon service

  7. #5

    RabbieBurns's Avatar
    Join Date
    Apr 2008
    Location
    Sydney
    Posts
    5,512
    Thank Post
    1,320
    Thanked 469 Times in 306 Posts
    Blog Entries
    6
    Rep Power
    199
    Quote Originally Posted by soveryapt View Post
    I had this for a while. I found out it was our AV software (Sophos) that was temporarily disabling the network cards on boot up which mean if you logged on too quickly, it didn't see the servers and reported that problem, but you waited another minute then it was able to log on.

    When this happens now, it only seems to be on laptops when someone has disable the wireless, so I don't know if that was the only issue, but it just seemed to be a time thing.
    We use sophos. I haven't bothered updating the Enterprise Console in a while (4.7 i think atm) as the plan is to go with SCCM 2012 as soon as I get time. And as you say, the problem isn't consistent, a few tries after the machine starts up and it logs in OK. I wonder if it could be the same here. Do you have any other anecdotal evidence
    @FN-GM, DNS is fine, Ive made sure the 3 DC's are the only DNS servers.
    @SYNACK thanks, I will test that out. Not sure what would cause that on a wired client altough I will check to see if there are any startup scripts happening.

  8. #6

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,262
    Thank Post
    242
    Thanked 1,568 Times in 1,250 Posts
    Rep Power
    340
    Other factors as well as DNS could be the number of WAPs you have as well as the amount of memory in workstations. It's not difficult to do on wireless clients (if you're too quick to logon), but it's exceptionally rare on Ethernet connections in my experience.

    Wireless is slower than wired and of course a lack of memory just means clients have to work harder until it dynamically receives an IP from DHCP Server.

    I suppose other things to check are your servers. Are they replicating correctly? Opening up Active Directory Sites and Services and you can manually force them to replicate.

  9. #7

    SYNACK's Avatar
    Join Date
    Oct 2007
    Posts
    11,072
    Thank Post
    853
    Thanked 2,676 Times in 2,270 Posts
    Blog Entries
    9
    Rep Power
    769
    Quote Originally Posted by RabbieBurns View Post
    Not sure what would cause that on a wired client altough I will check to see if there are any startup scripts happening.
    If you have STP turned on in the switches this is more likely and should be set to RSTP/Portfast. Also if you have intel GB NICs there is an advanced setting "Wait for Link" which should be set to "on" as otherwise the driver will not wait for IP connectivity at all by default. The default setting is 'auto' which is wrong and causes issues. Some other cards have simmilar settings and these can help hugely with initial network issues. The other thing to check is that the drivers are up to date and also if the machines have AMT/vPro you may need/want to upgrade the BIOS to the latest version as sometimes the managment stuff gets in the way of the network sensing at the exact wrong time.

  10. Thanks to SYNACK from:

    psydii (28th May 2012)

  11. #8
    Pete10141748's Avatar
    Join Date
    Nov 2007
    Posts
    1,365
    Thank Post
    106
    Thanked 220 Times in 130 Posts
    Rep Power
    86
    I see this sometimes as well, having mostly wireless laptop here.

    I've had problems with laptop wireless cards not picking up a signal until after logon creating all kinds of logon problems.
    Sophos can cause issues, another thing I've had to deal with here.
    It mght also help to make netlogon service in Win7 not dependant on user login;

    Code:
    sc config netlogon depend= wlansvc/lanmanworkstation
    Run that as a batch file, or just type it into CMD while logged on as someone with admin rights.
    It seems to have helped here!

  12. #9

    RabbieBurns's Avatar
    Join Date
    Apr 2008
    Location
    Sydney
    Posts
    5,512
    Thank Post
    1,320
    Thanked 469 Times in 306 Posts
    Blog Entries
    6
    Rep Power
    199
    Ive just ordered another 30 Aps to pretty much do 1 AP per classroom at the moment its 2 APs for every 3 classrooms. Ive also recently just audited all the channels as our system doesn't seem to adjust the channels of each AP automatically depending on the surroundings, even when set to channel "auto", and have removed hopefully some interderence from AP channel overlap.

    Regarding @Michael how would I check if they are replicating correctly ? Is SCOM something i should be looking at to help me audit the event logs of all my servers?
    @SYNACK thanks I have tried this method on a couple of troublesome devices, eg. our Dell Latitude ST slates which are up to date with the latest driver on the dell website. STP is enabled on all of our switches, I have not heard of RSTP/Portfast I dont think. The desktops experinecing issues seem to mainly be Dell Optiplex which are GBE but Im unsure of the chipet off the top of my head

  13. #10
    bondbill2k2's Avatar
    Join Date
    Jan 2011
    Location
    West Midlands
    Posts
    1,013
    Thank Post
    80
    Thanked 66 Times in 51 Posts
    Blog Entries
    2
    Rep Power
    42
    Quote Originally Posted by soveryapt View Post
    I had this for a while. I found out it was our AV software (Sophos) that was temporarily disabling the network cards on boot up which mean if you logged on too quickly, it didn't see the servers and reported that problem, but you waited another minute then it was able to log on.

    When this happens now, it only seems to be on laptops when someone has disable the wireless, so I don't know if that was the only issue, but it just seemed to be a time thing.
    Had the same problem here now only occurs when disabling the wireless so I normly tell people who find their wireless turned off to flick it on the reboot.

  14. #11
    soveryapt's Avatar
    Join Date
    Jan 2009
    Location
    Lancashire
    Posts
    2,402
    Thank Post
    648
    Thanked 277 Times in 244 Posts
    Rep Power
    78
    Nothing more anecdotal to add sadly. It was something I found out in a conversation with our LEA Technical Team who (until next week) look after the admin machines in the school, so I was trying to resolve an issue where the deputy head was logging on but not getting network drives, and this was because Sophos was doing the whole "lets turn the network cards off for this check" at startup, but left an extra 30seconds or so and it worked fine.

    Generally, by the time the staff member calls me up and I go to check on their laptop or the trolley laptops in question, I walk into the room and Sophos has done it's thing and they work when I log on with the test student / test staff account (I avoid using mine simply through the fact, for a majority I have logged on previously during deployment, so I have a few test accounts that I rotate to be sure they're not in the cache of the machine somewhere).

    I think the only other thing that caused this for me was when I had one laptop in particular that had simply decided it didn't want to take the GPO settings from the server anymore, but with a quite gpupdate /force, it rectified itself.

    It's quite rare that I do get the logon servers unavailable message, and it is more with the staff and students who can type quickly.

  15. #12

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,262
    Thank Post
    242
    Thanked 1,568 Times in 1,250 Posts
    Rep Power
    340
    Quote Originally Posted by RabbieBurns View Post
    Regarding @Michael how would I check if they are replicating correctly ? Is SCOM something i should be looking at to help me audit the event logs of all my servers?
    On your either of your DCs open Active Directory Sites and Services > Default-First-Site-Name > Servers.

    Expand SERVERNAME, then click on NTDS Settings. To the right, it should display <automatically generated>. Right click this and select 'Replicate Now'.

    You should receive the message 'Active Directory Domain Services has replicated the connections.'

    Repeat this for all listed DCs, so you know it works both ways.

    If one of your replications fail (for whatever reason) the odds are it is DNS related. DNS rules everything in Windows Server.

  16. #13

    Join Date
    Jul 2006
    Location
    London
    Posts
    1,254
    Thank Post
    111
    Thanked 242 Times in 193 Posts
    Blog Entries
    1
    Rep Power
    74
    I think what you really need is this hotfix:
    Event ID 5719 and event ID 1129 may be logged when a non-Microsoft DHCP Relay Agent is used


    While you are at it try deploying the hotfixes listed here Disabling Offline files Server 2008 & Win 7 pro (you probably wont need to disable offline files once this lot are installed - but you will want to stop automatic caching of redirected folders)

    Pick a group of laptops first as a control and monitor user happiness.
    Last edited by psydii; 28th May 2012 at 06:44 PM.

  17. #14

    witch's Avatar
    Join Date
    Nov 2005
    Location
    Dorset
    Posts
    11,109
    Thank Post
    1,367
    Thanked 2,374 Times in 1,671 Posts
    Rep Power
    703
    Quote Originally Posted by SYNACK View Post
    Yea, check the network stack. It's likely to be IP based due to drivers taking too long to resolve an initial IP connection. With wireless make sure that the wireless profiles are machine based not using user credentials.

    You could also try something like this although it may have some side effects:
    I had the same issue on my network and I followed the first part of these instructions - "Fixing the netlogon Service"
    It worked like a charm and has almost eradicated the problem.I have not seen any side effects of any kind and I did this about 3 weeks ago. Give it a go!

  18. Thanks to witch from:

    RabbieBurns (29th May 2012)

  19. #15
    sister_annex's Avatar
    Join Date
    Jan 2009
    Location
    Wolverhampton
    Posts
    593
    Thank Post
    99
    Thanked 135 Times in 119 Posts
    Rep Power
    49
    You're not using DeepFreeze by any chance?

SHARE:
+ Post New Thread
Page 1 of 2 12 LastLast

Similar Threads

  1. No Logon Servers Available to service the logon request
    By Niall in forum Windows Server 2008 R2
    Replies: 15
    Last Post: 27th October 2011, 02:32 PM
  2. no logon servers available
    By cheeseslice in forum Windows Server 2008 R2
    Replies: 6
    Last Post: 16th May 2011, 10:34 AM
  3. Replies: 3
    Last Post: 12th February 2010, 02:42 PM
  4. No logon servers available
    By steve_nfi in forum Windows Server 2000/2003
    Replies: 0
    Last Post: 7th December 2009, 10:09 AM
  5. Not enough server storage is available to process this command?
    By googlemad in forum Windows Server 2000/2003
    Replies: 7
    Last Post: 9th April 2009, 09:22 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •