Troubleshooting Tip: Resolving Winbind Secondary Domain Join Issue with error 'Failed to connect to bus: Invalid argument'

[Hatibi]

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	Go to Network -> RADIUS -> Winbind -> Domain Configuration. Figure 1. Winbind Configuration example where no special characters such as '-' are included in the entries highlighted in red. Delete the existing Winbind entries for the secondary domain where special characters such as '_' were included in 'Name' and 'Local NetBIOS Name'. Create a new Winbind entry for the secondary domain without using special characters, such as an underscore, in the Name and Local NetBIOS Name entries. Save the changes and try joining the secondary domain again. The fix for this issue will be available in the v7.6.3 GA release. Related documents: Winbind Configuration 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