Troubleshooting Tip: Resolving Winbind Secondary Domain Join Issue with error 'Failed to connect to bus: Invalid argument'
| Description | This article describes how to resolve the issue where joining a secondary domain in Winbind configuration on FortiNAC is failing.
The issue occurs when the Winbind Domain Configuration contains special characters, such as an underscore, in the Name and Local NetBIOS Name entries, causing an error 'Failed to connect to bus: Invalid argument'. |
| Scope | FortiNAC, FortiNAC-F. |
| Solution |
 Figure 1. Winbind Configuration example where no special characters such as '-' are included in the entries highlighted in red.
The fix for this issue will be available in the v7.6.3 GA release.
Related documents: Technical Tip: MSCHAPv2 authentication, join FortiNAC in domain and checks Technical Tip: FortiNAC Domain join using account with minimum permissions Troubleshooting Tip: FortiNAC cannot join the Winbind domain |
