Skip to main content

LevelBlue + SentinelOne: Global Partnership to Deliver AI-Powered Managed Security Operations and Incident Response. Learn More

LevelBlue + SentinelOne: Global Partnership to Deliver AI-Powered Managed Security Operations and Incident Response. Learn More

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
Solutions
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft Security
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
Awards and Accolades
LevelBlue SpiderLabs
PGA of America Partnership
Secure What's Next
LevelBlue Security Operations Platforms
Security Colony
Partners
SentinelOne
Advancing integrated, intelligence‑driven security operations
Microsoft
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Partner Portal
Loading...
Loading...

INFO: Why am I unable to access the WebMarshal console remotely?

Expand / Collapse


This article applies to:

  • WebMarshal 6.X
  • Windows workstation not joined to a domain

Question:

  • Why am I unable to access the WebMarshal console remotely?

Information:

When you attempt to connect a remote WebMarshal console to a WebMarshal server installed on Windows workstations as a workgroup member you could receive an authentication error and be prevented from connecting to the WebMarshal server. 

When a Windows workstations is not a member of a domain, remote connections may be forced to use the "Guest" account and per-account authentication is not available.

Resolution:

To resolve this issue follow the steps below:

Warning: Using the Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Marshal cannot guarantee that problems resulting from the incorrect use of the Registry Editor can be solved. Make sure that you back up your Registry prior to making any changes.

  1. On the machine that is running the WebMarshal Array Manager, start Regedit (Click Start > Run, and enter Regedit).
  2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
  3. Change the Value Data of the forceguest entry to 0.
  4. Restart the WebMarshal Array Manager service.

To contact LevelBlue about this article or to request support:


Rate this Article:
     

Add Your Comments


Comment submission is disabled for anonymous users.
Please send feedback to Trustwave Technical Support or the Webmaster
.