Setting up web conferences in MDaemon for multiple domains

MDaemon supports multi-domain web conferences, and the problem of users from one domain connecting to the web conference server is usually related to domain sharing settings or network configurations. In your case, despite having the “Enable all domains in user’s friends list” feature activated, you need to check the domain sharing settings, network rules, and possible IP address conflicts between domains.

Contents

• Basic Web Conference Settings
• Domain Sharing Configuration
• Connection Troubleshooting
• Alternative Setup Methods
• Network Parameters Check

Basic Web Conference Settings

The basic web conference configuration in MDaemon is located in Main | Web Conference Server in the MDaemon remote administration interface. According to the official documentation, there is an option that allows users to join conferences with users from other domains, provided these domains are also hosted on the same MDaemon server.

For multi-domain web conferences to work correctly, you must ensure that:

1. Web conferences are properly enabled for all domains
2. Domain sharing is configured between domains
3. Users use the correct login format (full email address when working with a single IP address)

Important: If multiple domains use the same IP address, you must use the full email address to log in. Otherwise, MDaemon cannot determine which user is trying to log in.

Domain Sharing Configuration

The key element for solving the connection problem for users from different domains is the proper configuration of Domain Sharing. This option is located in Setup > Default Domain & Servers > Domain Sharing tab > Host or IP section.

To configure domain sharing, follow these steps:

1. Open the MDaemon remote administration interface
2. Go to Setup > Default Domain & Servers
3. Select the Domain Sharing tab
4. In the Host or IP section, add the IP addresses or host names with which you need to share domains
5. Check the Enable Domain Sharing box to enable the function

After enabling domain sharing, make sure that Minger is also configured and enabled - the component responsible for handling requests from other hosts when checking local addresses.

Source: Domain Sharing Configuration

Connection Troubleshooting

If users from one of the domains cannot connect to the web conference server despite the activated settings, you need to check several potential issues:

1. IP Address and Domain Binding Issues

As noted in MDaemon community discussions, the most common problem is using a single IP address for multiple domains. In this case, it is recommended:

Solution: Bind each domain to its own IP address and direct connections for each domain to the correct IP address.

This can be done through the server’s network interface settings or through the MDaemon web server settings.

2. Firewall and Network Restriction Issues

According to research, about 10% of WebRTC connections cannot establish a connection without using a TURN server, especially in restrictive or multi-firewall environments.

Solution: If necessary, you can implement a third-party TURN server to ensure connections pass through network restrictions.

3. Checking with MDaemon Health Check

MDaemon version 17 and higher includes a built-in MDaemon Health Check tool that analyzes current security configurations and helps identify issues.

Usage:

1. Run MDaemon Health Check
2. Analyze the security recommendations
3. Make necessary changes to the configuration

Source: Web Conference Server Troubleshooting

Alternative Setup Methods

Method 1: Using Full Email Address

If you cannot bind separate IP addresses to domains, make sure users use their full email address to log in to web conferences:

username@domain1.com
username@domain2.com

Method 2: Configuring Alternative Host Names

In the SSL certificate settings, you can add alternative host names for all domains:

1. Go to Web & SyncML Services
2. In the Alternative Host Names section, specify all secondary domains covered by the SSL certificate, separated by commas
3. Click Create Certificate

Source: SSL Certificate Configuration

Method 3: Separate Domain Administration

Use Domain Manager to administer multiple domains. In Domain Manager, you can manage:

• Domain names
• IP addresses
• Account settings
• Webmail parameters
• Other domain-specific options

Source: Domain Manager Configuration

Network Parameters Check

Additionally, check the following network parameters:

1. DNS Settings - Make sure forward and reverse DNS records are configured for each domain
2. Ports and Protocols - Check that the necessary ports for web conferences are open
3. Firewall - Make sure the firewall is not blocking connections to web conferences
4. Routing Settings - Check the correctness of routing between domains

If you only have one IP address, the server will announce itself as the default domain. It should send and receive mail to the internet without problems, provided that the server’s FQDN has forward and reverse DNS records.

Source: MDaemon and Multiple Domains

Sources

1. Web Conference Server Configuration
2. Domain Sharing Setup Guide
3. Domain Manager Overview
4. Multiple Domains Configuration
5. SSL Certificate for Secondary Domains
6. Hosting Multiple Domains Documentation
7. MDaemon Health Check Feature

Conclusion

Based on the research conducted, the following conclusions can be drawn:

1. The main problem with users from one domain connecting to web conferences of another domain is related to incorrect domain sharing configuration or IP address conflicts.

2. Recommended solutions:

   • Configure proper domain sharing through Domain Sharing
   • Bind each domain to a separate IP address (if possible)
   • Use the full email address for login when sharing an IP
   • Check network settings and firewall

3. Diagnostic tools: Use the built-in MDaemon Health Check tool to analyze the current configuration and identify issues.

4. Preventive measures: Regularly update MDaemon, monitor documentation updates, and consider the specifics of your network infrastructure.

If the problem is not resolved after implementing all recommendations, it is recommended to contact MDaemon technical support or explore deeper security and network configuration settings. Many users have reported successfully solving similar problems after carefully configuring domain sharing and IP addressing.