Skip to main content

LevelBlue Completes Acquisition of Cybereason. Learn more

LevelBlue Completes Acquisition of Cybereason. Learn more

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Infrastructure 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
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
LevelBlue Security Operations Platforms
Security Colony
Partners
Microsoft
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Loading...
Loading...

HOWTO: Setting limits for client connections to WebMarshal

Expand / Collapse


This article applies to:

  • WebMarshal 6.10 and above

Question:

  • What is the limit on concurrent connections from a client computer to WebMarshal?
  • How do I adjust the client connection limit?

Procedure:

WebMarshal 6.10 and above allows a limit on concurrent connections from any one client IP to the WebMarshal Proxy service. This feature helps to avoid inadvertent or intentional flooding of the WebMarshal server.

By default the limit is 6000 concurrent connections from any one IP (for 32 bit operating systems, 4000 concurrent connections from any one IP). This default applies to all installations of WebMarshal 6.10 and above, whether new, or upgraded from a previous version.

You can adjust the setting as follows.

Note: If you have more than one processing server (node), you must make the changes on each server.

  • Add an entry in the WebMarshal Proxy Configuration file (WMProxy.config.xml)
    <WebMarshal> 
        <Proxy>
         <Config>
    <ProxySettings maxClientConnections="{value}" [other attributes...] />      </Config>
       </Proxy>
    </WebMarshal>

Notes:

  • To disable connection limits, set the value to zero or a negative number.
  • To accept the default, remove the entire string maxClientConnections="{value}"
  • For general information about editing XML settings files, see article Q12705.
  • The file WMProxy.config.xml is located on the processing server. If you have more than one processing server, you must make the changes on each server.
  • To apply the change, restart the WebMarshal Proxy service.
  • When entering the value, do not include the braces {}, but do include the quote marks.
  • Back up configuration before making changes.
  • The file WMProxy.config.xml normally contains additional settings. The ProxySettings node can have multiple attributes. This node should only occur once.
  • To adjust this setting, only add (or remove) the specific attribute maxClientConnections.

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
.