Workstation Service did/will not start – Day 1

Background

On a MS Windows Machine, unfortunately you might run into a situation where the Workstation Service did not start.

 

TroubleShooting

Services

Review your workstation service, it’s status, startup Type, and “Log On As” account.

workstation_20170511_0556AM

 

Event Viewer

Images

Application

Source: Userenv // Event ID 1053

Userenv_20170511_1139PM (BushedUp)

 

System

Source: NetLogon // Event ID 5719

NetLogon_20170511_1229AM (Brushed Up)

 

Tabulate

 

Branch Source Type Event ID Description
 Application  
 Userenv  Error  1053 Windows cannot determine the user or computer name. ( The workstation driver is not installed.) Group Policy processing aborted.
 System
 NetLogon  Error  5719 This computer was not able o set up a secure session with a domain controller in domain … due to the following: These are currently no logon servers available to service the logon request.
This may lead to authentication problems. Make sure this computer is connection to the network.

 

 

 

Remediation

Regedit

Outline

Launch regedit and review the Service configuration.

Our service is Workstation and the specific registry branch is HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation.

  1. Launch regedit
  2. Transverse to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation branch
  3. Backup Registry
    • Export contents of that branch
  4. Review the following keys
    • Depend on Group (DependOnGroup)
      • Should be empty
    • Depend on Service (DependOnService)
      • Varies depend on Win OS Version
        • Windows 2003
          • bowser
          • mrxsmb20
          • nsi

 

Steps

In our case we temporarily renamed “DependOnService” to “DependOnService.20170511.1218AM

 

Original

regedit_20170511_1217AM

 

Revised

regedit_20170511_1227AM

regedit_20170511_1227AM

Summary

This is only Day 1.

And, it is only a temporary workaround.

In later posts, we will identify each dependency listed and see whether it is a service or a device.

The problem may lie with a malfunction device, disabled or missing device, or other things.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s