gateway issue - cluster setup

Hi merkol​,
The DMTS_GatewayIsDisabled message is expected because the old gateway was intentionally disabled; the actionable error is the Mashup query execution timeout on the new gateway server. Since Server 2 is in a different data center, run the gateway Network Ports Test and verify the required firewall and proxy connectivity. Also verify the proxy configuration, including Microsoft.Mashup.Container.NetFX45.exe.config, as Microsoft documents this for cloud data-source queries through the gateway. Finally, ensure both cluster members are running the same gateway version, as Microsoft recommends keeping cluster member versions in sync.
Troubleshoot the on-premises data gateway | Microsoft Learn
Adjust communication settings for the on-premises data gateway | Microsoft Learn
Configure proxy settings for the on-premises data gateway | Microsoft Learn
Manage on-premises data gateway high-availability clusters and load balancing | Microsoft Learn

Thank you.

Thank you for your feedback. The network and admin teams checked each link and applied the steps described in them.

• Both servers run the same version, and it is the latest available.
• No antivirus tool is installed.
• The proxy settings were checked and are correct.
• The network test finished successfully.

We could not identify the root cause. The only information we have is that the log shows a timeout after 50 seconds. And this is only happing for SharePoint, for other locations gateway works fine. 

regards,

HI merkol​,

Have you had a chance to review the solution we shared earlier? If the issue persists, feel free to reply so we can help further.

Thank yoyu

Hello,

thank you again for your feedback. Connection from the server to share point is working fine. 

I will create a support ticket. in the mean time we asked users to use direct connection without gateway.

regards

Hi merkol​,

A consistent ~50 second timeout that hits only SharePoint, on only the new server, usually points to something the network test does not exercise: the SharePoint calls are made by the mashup container running under the gateway service account, often to more hosts than the test covers (sign-in, SharePoint tenant, CDN), and over a path that may differ per data center (TLS inspection, WPAD/proxy auto-detect, IPv6). A few targeted checks:

1. Test SharePoint as the gateway service, not as your admin user. Run this on Server 2 in a shell started as the service identity (or SYSTEM via PsExec -s as a close approximation):

$hosts = "login.microsoftonline.com","<tenant>.sharepoint.com","<tenant>-my.sharepoint.com"
foreach ($h in $hosts) {
  $sw = [Diagnostics.Stopwatch]::StartNew()
  try { Invoke-WebRequest "https://$h" -UseBasicParsing -TimeoutSec 60 | Out-Null; "OK  $h  $($sw.Elapsed.TotalSeconds)s" }
  catch { "ERR $h  $($sw.Elapsed.TotalSeconds)s  $($_.Exception.Message)" }
}
Resolve-DnsName <tenant>.sharepoint.com          # compare IPv4/IPv6 answers with Server 1
netsh winhttp show proxy                          # machine-level proxy used by services

If one host takes ~20-50s before succeeding, that is your timeout: typically IPv6 being tried first and blackholed, WPAD auto-detect waiting, or an SSL-inspecting device in the new DC that SharePoint traffic goes through.

2. Compare TLS inspection between data centers. If the new DC breaks and re-signs TLS, add the SharePoint/Microsoft 365 endpoints to the inspection bypass list (Microsoft publishes them as the "Optimize/Allow" Microsoft 365 endpoint categories).

3. Keep production stable meanwhile. In the gateway cluster settings, turn off "Distribute requests across all active gateways in this cluster" (or set Server 2 to disabled for now), so SharePoint refreshes keep going to Server 1 while you test.

So my overall approach would be:

Route traffic to Server 1 (disable distribution / member) for now
-> On Server 2, time each SharePoint-related host as the service identity
-> Compare DNS (IPv6), WinHTTP proxy and TLS inspection with Server 1
-> Bypass inspection / fix proxy for M365 endpoints
-> Re-enable Server 2 and test a SharePoint refresh

AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.