Forum Discussion
On-premise data gateway cannot connect to database
Hii Lorenz33
Basic (SQL) authentication requires TCP/IP connectivity, and the error “Named Pipes Provider, error: 40” means the new gateway servers cannot reach SQL Server over the required port. You need to ensure TCP/IP is enabled in SQL Server Configuration Manager, the correct SQL port (usually 1433 or a custom port) is open in the firewall, SQL Server allows remote connections, and if using a named instance, either start SQL Browser or specify the port explicitly (ServerName,Port). Once network connectivity is confirmed from the new gateway servers, Basic authentication will work.
Thanks Rohit. The new Windows 2025 Server on-premise data gateway cluster is being tested with plans to replace the Windows 2016 Server on-premise data gateway cluster. With the Windows 2016, data gateway I am able to successfully create a connection to the same SQL Server database using basic authentication. As it works on the Windows 2016 data gateway and not the Windows 2025 data gateway, this should mean that the required port (1433) should already be open and that there are no firewall issues. Could the Windows 2025 data gateway be attempting access through a different port?