MDaemon Web Conference Access Troubleshooting

Setting up web conferences in MDaemon can indeed cause problems with cross-domain access. The main reasons why users from one domain cannot connect to the web conference server despite the “Include all domains in the user buddy list” feature being enabled may be: incorrect domain access rights settings, user authentication issues, group or user restrictions, and incorrect network configuration parameters. To solve the problem, it is necessary to check domain access rights settings, verify user credentials, and check the network configuration.

Table of Contents

• Main causes of web conference access problems
• Step-by-step web conference setup
• Checking cross-domain access rights
• Solving common problems
• Additional recommendations

Main causes of web conference access problems

Even with the “Include all domains in the user buddy list” feature enabled, users may experience problems accessing web conferences. The main causes are:

1. Domain access restrictions - Each domain in MDaemon has its own access rights settings. Even with the global “Include all domains” setting, individual domains may be restricted from accessing web conferences.

2. Authentication issues - Users may receive “Authentication required” messages when trying to connect, especially if their credentials are not properly configured for cross-domain access.

3. Group and user settings - Individual users or groups may be restricted from accessing web conferences through their account settings.

4. Network configurations - Routing issues or firewall restrictions may block access to the web conference server.

Important: According to MDaemon documentation, users can join conferences with users from other domains only if those domains are also hosted on the same MDaemon server.

Step-by-step web conference setup

To properly configure web conferences with cross-domain access support, follow these steps:

1. Open the MDaemon remote administration interface

   • Go to Main | Web Conference Server

2. Check the “Include all domains in the user buddy list” setting

   • Make sure this option is enabled (as you already mentioned)
   • This function adds all domains to the user’s default buddy list

3. Configure web conference parameters

   • Check port and IP address settings
   • Ensure the server is listening on the correct interfaces
   • For example, the setting *,*:80 will make Webmail listen on all IP addresses on the specified ports

4. Check SSL/TLS settings

   • When using HTTPS, ensure the certificate is properly configured
   • Add all domains to the certificate’s Subject Alternative Names list

Checking cross-domain access rights

To resolve cross-domain access issues, you need to thoroughly check access rights settings:

1. Check administrator roles

   • Global administrators have access to all settings and can control every parameter
   • Domain administrators have limited control only over domains they have been granted access to

2. Check user account settings

   • Ensure user accounts are properly configured for web conference access
   • Verify that users are not restricted in their access through their account settings

3. Check group settings

   • Ensure that groups the users belong to have access to web conferences

4. Check network configuration

   • If there are access issues from the local network, you may need to add entries to the MDaemon routing table
   • Ensure there are no firewall restrictions blocking access to web conference ports

Solving common problems

Problem: “Authentication required” message

If users receive an “Authentication required” message, it may mean:

• User credentials are incorrect
• The user does not have an account on the MDaemon server
• Domain authentication issues

Solution:

1. Ensure the username contains only the part before the @ sign
2. Check that the domain part is correctly specified in the client settings
3. Verify that the user account is not disabled or frozen

Problem: “Access Denied” errors

If users receive “Access Denied” messages, this may be related to:

- Restrictions in Remote Administration settings
- Issues with Account Editor access
- Restrictions set at the group or user level

Solution:

1. Check Remote Administration settings for users
2. Ensure users have the necessary access rights
3. Verify that accounts are not restricted from accessing web services

Problem: Users don’t see each other in the buddy list

Even with the “Include all domains” feature enabled, users may not see each other in the buddy list. This may be due to:

• Individual user settings
• Data synchronization issues
• Group-level restrictions

Solution:

1. Check individual settings for each user
2. Restart web conference services
3. Check MDaemon server error logs

Additional recommendations

1. Update MDaemon to the latest version

   • Latest versions include improvements in web conference functionality
   • Known cross-domain access issues have been fixed

2. Check event logs

   • Analyze MDaemon logs for errors
   • Look for messages related to authentication and access

3. Test connection from different locations

   • Try connecting from different networks
   • Check accessibility from both local and remote machines

4. Consult MDaemon support

   • If the problem persists, contact technical support
   • Provide them with detailed configuration information and error logs

It’s important to remember that proper web conference configuration requires careful attention to each parameter, especially when working with multiple domains on one server.

Sources

1. Web Conference Server - Official MDaemon Documentation
2. New in MDaemon 25.5 - New Features and Improvements
3. MDaemon Server Release Notes - Release Notes
4. Web Services - Web Services Settings
5. Web Server - Web Server Configuration
6. MDaemon Installation Guide - Installation Guide
7. Configuring ActiveSync in MDaemon - ActiveSync Configuration

Conclusion

Key points to consider when solving web conference access problems between domains in MDaemon:

1. Check all levels of access rights - from global settings to individual user parameters
2. Ensure proper authentication settings - especially regarding credential format for cross-domain access
3. Analyze network configuration - check routing and firewall restrictions
4. Use the latest version of MDaemon - to get all fixes and improvements
5. Maintain detailed logs - they will help diagnose hidden issues

If the problem persists after implementing all recommendations, it is advisable to contact MDaemon technical support with complete configuration information and error logs. Remember that cross-domain web conference operation requires careful configuration at all system levels.