Just Published! Threat Report: Exposing Malware in Linux-Based Multi-Cloud Environments | Download Now

Fatal Error: Could not connect to host - Service Account Local Policies

Fatal Error: Could not connect to host - Service Account Local Policies

Version
Carbon Black Enterprise Protection - All


Issue

Cannot access console, typically after a new install or upgrade.

Symptoms
"Fatal Error. Network error while trying to communicate with Bit9 Server. Error: Could not connect to host"

Console is inaccessible.


Cause
Some environments have Group Policies in place that prevent the Service Account from gaining these security policies.

Service account credentials may have changed, and these policies were not updated to reflect the change.

Solution

Confirm that DNS is working by doing a ping and nslookup for the Cb Protection server from the machine where you're accessing the console from. Attempt to access the console from the Cb Protection server directly.

On the Cb Protection server, add the Service Account to the following Local Policies:

"Log on as a Service"

"Log on as a Batch Job"

Microsoft TechNet article on how to add user to Log on as a Service policy. Same steps can be applie...

Additionally, If the above does not work then navigate to C:\Users\<Bit9 User Account>\AppData\Local\Temp and delete the files within the Temp folder.


Important Note(s)

A Group Policy may need to be added to grant the Service Account these Local Policies.

Also, ensure the Service Account has all the other proper permissions in place, according to Bit9 service account permissions

Labels (1)
Was this article helpful? Yes No
100% helpful (1/1)
Article Information
Author:
Creation Date:
‎06-30-2016
Views:
2405
Contributors