Trustwave and Cybereason Merge to Form Global MDR Powerhouse for Unparalleled Cybersecurity Value. Learn More

Trustwave and Cybereason Merge to Form Global MDR Powerhouse for Unparalleled Cybersecurity Value. Learn More

Services
Managed Detection & Response

Eliminate active threats with 24/7 threat detection, investigation, and response.

Co-Managed SOC (SIEM)

Maximize your SIEM investment, stop alert fatigue, and enhance your team with hybrid security operations support.

Advisory & Diagnostics

Advance your cybersecurity program and get expert guidance where you need it most.

Penetration Testing

Test your physical locations and IT infrastructure to shore up weaknesses before exploitation.

Database Security

Prevent unauthorized access and exceed compliance requirements.

Email Security

Stop email threats others miss and secure your organization against the #1 ransomware attack vector.

Digital Forensics & Incident Response

Prepare for the inevitable with 24/7 global breach response in-region and available on-site.

Firewall & Technology Management

Mitigate risk of a cyberattack with 24/7 incident and health monitoring and the latest threat intelligence.

Solutions
BY TOPIC
Microsoft Security
Unlock the full power of Microsoft Security
Offensive Security
Solutions to maximize your security ROI
Rapidly Secure New Environments
Security for rapid response situations
Securing the Cloud
Safely navigate and stay protected
Securing the IoT Landscape
Test, monitor and secure network objects
Why Trustwave
About Us
Awards and Accolades
Trustwave SpiderLabs Team
Trustwave Fusion Security Operations Platform
Trustwave Security Colony
Partners
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Trustwave PartnerOne Program
Join forces with Trustwave to protect against the most advance cybersecurity threats
Loading...
Loading...

INFO: Troubleshooting Connector Agent issues

Expand / Collapse


This article applies to:

  • MailMarshal SPE
  • Connector Agent

Question:

  • What are common issues with Connector Agent?
  • Where do I look for logs and other information to debug Connector Agent?
  • What can I do to make debugging easier?

Response:

The following points address some common issues and points to consider when troubleshooting Connector Agent:

Invalid addresses

  • The Primary email address for each user (in the AD or LDAP at the customer site) must match a domain that belongs to the customer in SPE.
    • If any user does not match the domains, then that Connector Agent will have errors until ALL users are corrected.

Logs and other messages

  • The end customer CA GUI often gives an error "invalid checksum," but this is misleading. This is actually a generic error.
  • For best information, look at the SPELdapService log (found on the Customer Console server in the Logging subfolder of the install).
    • If the log shows invalid email addresses, the customer must fix all of these to get good imports.
    • When there are invalid addresses, the Connector Agent issues constant retries which are rejected.
    • An AD entry with a blank SMTP address is a particular case that is common and can be hard to resolve.
    • If the CA at the customer site is set to send updates more often than allowed by the SPE installation, this also causes rejected attempts.
  • Also see the logs at the end customer connector agent installation (...\Marshal\ConnectorAgent\Logging)

Update frequency and "test mode"

  • When testing or debugging, check the box "in test mode" for the customer (in Admin Console, Connector agent tab for each customer). This removes the restriction on "too frequent updates" and allows the customer to make and test changes.
  • For production usage, set the Update Frequency to 4 hours (in Admin Console). Ensure that the customer Connector Agent is not configured to send updates more frequently. If the CA tries to send more frequent updates, they will only be rejected causing errors, frequent retries, and full logs. 

 Address validation

  • The LDAP and AD groups are validated at different times in the process.
    • With the AD connector, the Connector Agent rejects users that do not match the customer's domains as configured in SPE. Non-matching users are not sent.
    • With the LDAP connector, the Connector Agent sends all users. Non-matching users are rejected by SPE.
  • With AD domain validation, you might encounter a problem due to inconsistent capitalization (the check for matching domains is case sensitive, though it should not be).
    • If you encounter this issue and it cannot be corrected at the customer site, contact Trustwave Technical Support for a fix. This fix will also be included in a future release of Connector Agent.

To contact Trustwave 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
.