Forum Discussion
Gateway connection error
Hii a-vdarute
If the error still persists after assigning permissions and restarting the gateway, the most likely cause is a Kerberos / impersonation mismatch between the gateway and the data source. As a next step, try switching the data source to use explicit credentials (for example, SQL authentication instead of Windows), or configure Kerberos delegation (double-hop) correctly if Windows authentication is required. Also verify that the same gateway is mapped to the dataset, the service account password hasn’t changed, and re-add the data source in the gateway cluster before updating credentials again.
Hi a-vdarute,
Thank you for the response and clarification. Since your machine is Azure AD joined only, windows authentication is not supported in this configuration. Because windows authentication requires a proper Active Directory domain join to enable user impersonation.
- Switch the data source to use sql authentication instead of windows authentication. This does not require domain join and will work correctly with your current setup.
Thanks and regards,
Anjan Kumar Chippa
Hi a-vdarute,
Thank you for reaching out to Microsoft Fabric Community.
Thank you rohit1991 for the prompt response.
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided by the user for the issue worked? or let us know if you need any further assistance.
Thanks and regards,
Anjan Kumar Chippa