Sign in
 
HomeWindows 8Windows 7Windows VistaWindows XPMDOPWindows IntuneLibraryForums
Windows Client >
> 
> 
There are currently no logon servers available to service the logon request with windows 7

Answered There are currently no logon servers available to service the logon request with windows 7

  • Tuesday, May 29, 2012 1:32 PM
     
     
    Sign In to Vote
    0

    We have 9 new Windows 7 systems and have installed Fiber cards in them. We have used Startech 1000Base-SX cards and Transtion Networks N-GSX-SC-01 cards.

    We get the same message when trying to logon to a system when the workstation has either been powerd off or has sat for a day with not being logged on.

    If you pull the fiber line out and put it back into the card or reboot you will be able to login. sometimes it take doing those 2 or 3 times.

    All computers have IP numbers assigned to them.

    Is this something that someone here has a fix for?

    The BIOS is upto date and the drivers are the newest.

    The same cards work in our XP systems without issues.

    Thanks for the help.

    Greg

     

All Replies

  • Tuesday, May 29, 2012 4:31 PM
     
     Answered
    Sign In to Vote
    0

    slidelltiger wrote:

    We have 9 new Windows 7 systems and have installed Fiber cards in
    them. We have used Startech 1000Base-SX cards and Transtion Networks
    N-GSX-SC-01 cards.

    We get the same message when trying to logon to a system when the
    workstation has either been powerd off or has sat for a day with not
    being logged on.

    If you pull the fiber line out and put it back into the card or
    reboot you will be able to login. sometimes it take doing those 2 or
    3 times.

    All computers have IP numbers assigned to them.

    Is this something that someone here has a fix for?

    The BIOS is upto date and the drivers are the newest.

    The same cards work in our XP systems without issues.



    Thanks for the help.



    Greg

    There is a group policy (Computer Config/Administrative
    Templates/System/Logon) "Always wait for the network at computer
    startup and logon". Enable this setting and see if that helps. If it
    does not helpm it's probably a driver/hardware issue.

    Wolfgang
     
  • Tuesday, May 29, 2012 4:48 PM
     
     Answered
    Sign In to Vote
    0

    First of all, I have not found this card among current type here

    1. Use drivers for Windows 7 (if not available, perhaps Windows 2008 R2 is a viable alternative). Are there any?

    2. Play with NIC parameters that may influence the card behaviour (jumbo packets, autotuning,...) and other protocols like SMB

    3. I have been surprized by missing forum or community of Transition web

    4. Catch and analyze network traffic.

    Regards

    Milos

     
  • Wednesday, May 30, 2012 5:50 AM
     
     
    Sign In to Vote
    0

    Under the network adapter properties - power management

    Uncheck "Allow computer to turn off this device to save power"

    Windows is probably turning off device to perserve the power.

     
  • Sunday, December 09, 2012 7:40 AM
     
     
    Sign In to Vote
    0

    I'm kind of embarrassed as to the cause, but I've had this problem recurring for over a year now and only just now figured it out - my domain controller did not have a static IP address. I had recently gotten things working again by re-adding my machine to the domain under a new name (and newly installed Win8) but didn't know why it worked. Then, my media server's share became unavailable due to this error (but I could still hit my DC shares by name). I removed my PC from the domain, but was getting a "DC not found" error when trying to re-add it. This set off alarms in my head, so I checked my DC's IP address, and lo and behold, it had a new IP address. It also explains why a few weeks ago, I lost internet access, which I was able to restore by adding my router's IP as a backup DNS...this solved the internet problem but let the DC error linger in the background.

    The moral of the story is when WinServer recommends a static IP address, set it to static IMMEDIATELY! (actually, what I had done when I first set things up a couple of years ago, I made the static setting in my router, so my DC had DHCP but was given the same IP by the router every time; at some point, I reset my router, leading to the DC getting different IPs)