πŸ‘» LSA cannot be contacted? Why?

When trying to access a remote desktop session to a server using my domain credentials I got this:


 The first place to go is the event log and under the system event log is the problem, the Workstation service is offline....

The Workstation service depends on the SMB 1.x MiniRedirector service which failed to start because of the following error: 
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

This makes sense as without the workstation service the server cannot talk to the domain, but why has the SMB 1.x redirector not started automatically, so lets look at that, this service is known as the mrxsmb10 service - that is a hidden device service so query it with this:

sc query mrxsmb10

The result is this:

TYPE               : 2  FILE_SYSTEM_DRIVER
STATE              : 1  STOPPED
WIN32_EXIT_CODE    : 1077  (0x435)
SERVICE_EXIT_CODE  : 0  (0x0)
CHECKPOINT         : 0x0
WAIT_HINT          : 0x0

The service has been disabled, and without the workstation service no domain communications can be completed, so lets fix that, start a command prompt as an administrator and run this:

sc config mrxsmb10 start= auto
sc start mrxsmb10


Then check the service again with the command:

sc query mrxsmb10

You should now see this:

TYPE               : 2  FILE_SYSTEM_DRIVER

STATE              : 4  RUNNING
                        (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
WIN32_EXIT_CODE    : 0  (0x0)
SERVICE_EXIT_CODE  : 0  (0x0)
CHECKPOINT         : 0x0
WAIT_HINT          : 0x0

Now you can start the Workstation service:



Then you can login as normal, any services that failed to start should automatically start, however, you may need to start some of the manually, depending on the recovery actions.

If you have services that need to start up in a particular order and are unsure of the order, simply restart the server to restore full service 
Previous Post Next Post

Ω†Ω…ΩˆΨ°Ψ¬ Ψ§Ω„Ψ§ΨͺΨ΅Ψ§Ω„