none
Win2008R2 DC - LanmanServer will not start - Evt 7023 and Error 1222 The network is not present or not started

    Question


  • Symptom description:

    I have a Windows 2008r2 Domain Controller which booted and recovered to "last known working configuration".

    Everything appears fine, it boots, all drivers load, even the workstation service loads, network connectivity is fine.

    However the [LanmanServer] service never starts from boot, and most services with a dependency on that service fail to provide service or fail to start.


    When I attempt to manually [start] the service it produces a pop up dialog indicating:



    and the following Event Log entry in System:



    I tried removing and reinstalling the "File and Printer Sharing for Microsoft Networks" Service

    I tried removing and reinstalling the "Client for Microsoft Networks" Client

    I tried resetting the "Winsock" and "TCP/IP" stacks from the command prompt

    I tried recording the file and registry components accessed while manually attempting to start it up, with SysInternals Process Monitor, nothing stood out, the service seems to have access to everything it needs and appears to be proceeding to start up and then shuts down.

    Does anyone know the test it performs to determine "The network is not present or not started?"

    And have any idea why the workstation service would start, but not the server service?

    Thanks

    Environment:

    Windows 2008 r2, flat network







    • Edited by jwillis84 Tuesday, October 30, 2012 6:13 AM
    Tuesday, October 30, 2012 5:41 AM

All replies

  • Hello,
     
    Thank you for your question.

    I am currently looking into this issue and will give you an update as soon as possible.
     
    Thank you for your understanding and support.


    TechNet Subscriber Support in forum |If you have any feedback on our support, please contact tnmff@microsoft.com.

    Thursday, November 01, 2012 1:35 AM
    Moderator
  • Please try to restart all the dependency services below and check if all of them can be started sucessfully:
    Computer Browser service, DFS Namespace service, Netlogon service.

    Please also verify below things:
    The server has network connectivity, and the link light is displayed.
    The server's network adapter contains a valid IP address.

    After that, please also try to uninstall the NIC driver and install a new version NIC driver on this problematic DC.

    If anything unclear, please feel free to let us know. Thanks!
    Thursday, November 01, 2012 6:18 AM
  • Computer Browser service was disabled, nevertheless I tried enabling and restarting it.

    DFS Namespace restarted

    Netlogon service would stop, but would not restart; I had to reboot the system to get it to come back online.

    I am using RDP to get to the console, so link light is displayed.

    I am using RDP to get to the console, so it has a valid IP address.

    After each step I tried manually starting the [Server] service and it continued to produce the popup dialog above and the Event log entry as before.

    I cannot remove the NIC driver and reinstall at this time, the server is 1200 miles away. A secondary server is being prepped for shipment, when that arrives, the server with the problem, can be taken offline and the NIC reinstalled by using the iLO NIC to manipulate the server remotely. Then the NIC can be removed and reinstalled remotely.

    The task is becoming a time drain and management is willing to blame inconsistent product behavior. The likelihood the problem will ever be fully understood is rapidly declining. I will close this request once I've been told to stop working on it, probably by this Sunday 11-04-2012.

    Thank you


    -- John Willis, Facebook: John-Willis, Skype: john.willis7416


    • Edited by jwillis84 Friday, November 02, 2012 2:30 PM
    Friday, November 02, 2012 2:29 PM
  • Hi,

    Thank you for your information. This issue usually cause by the NIC card drivers corrupt that cause service which depend on network connection could not started. Anyway, since this DC is in remote office and you cannot reinstall the network card driver, shipping a new DC to replace this problematic one is also a good options to fix this issue effecienely. 


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Tuesday, November 06, 2012 2:28 AM
  • The replacement server is scheduled to arrive today.

    The HP iLO gives us the ability to change the primary OS NIC driver remotely.

    Once services are restored to the branch office, the NIC driver will be removed and reinstalled to see if that solves the problem of not being able to start the [server] service.

    The HP server uses HP NCU and HP Branded Broadcom drivers, which have a history of communications problems with Microsoft software deployments. Google recommendations have been inconsistent but seem to state release cycles are out of sync between HP and Microsoft products and conflicts often arise causing mysterious problems like this.

    An attempt will be made to collect and verify either the removal and reintall method, or the server will be wiped and reinstalled with a new copy of the OS.


    -- John Willis, Facebook: John-Willis, Skype: john.willis7416


    • Edited by jwillis84 Tuesday, November 06, 2012 3:38 PM
    Tuesday, November 06, 2012 3:37 PM
  • Hi,

    Thanks for your information. Are there have any update for this issue? Could you let us know reinstall the NIC driver worked or not?


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Monday, November 12, 2012 5:19 AM
  • There are no updates at this time.

    We had to manually eject the DC from the domain since it was interfering with workstations logging on to the domain.

    Also the site does not currently have the capacity to support power and an additional server connected to the network at the same time. We are working on logistics to add a switch and power, or return the failed DC to central for repair. It is not a priority as the workstations had experienced problems for almost 7 days. Those had become the priority. Management has deemed it unimportant to repair this DC and more important to support the workstations and end users. All workstations are now back to logging on to the domain.

    So while curious, it is no longer of importance to us. We have prepared for future events by manually automating the backup of the registry and synchronizing the backup offsite.  [ ERUNT ]


    -- John Willis, Facebook: John-Willis, Skype: john.willis7416


    • Edited by jwillis84 Monday, November 12, 2012 2:47 PM
    Monday, November 12, 2012 2:46 PM
  • Hi,

    Thanks for your info. From current informaiton, we have understood you had manyally eject this problemtic DC from domain. If anything further need help, please feel free to let us know. Thank you for your time and efforts!


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Wednesday, November 14, 2012 1:26 AM