Gateway is configured correctly but is unreachable due to local network connectivity problems

[Anonymous]

General Information
Service Bus Namespace : WABI-WEST-EUROPE-relay17.servicebus.windows.net
Host Name : ns-sb2-prod-am3-003.cloudapp.net
Host IP Address : 104.40.150.139
Overall Results : 0/24 tests succeeded.

Note: If one or more tests failed, contact your network administrator to open the ports for the required servers.

Summary:
Server Name: IP Address: Test Results:
g0-prod-am3-003-sb.servicebus.windows.net 52.233.183.100 FAILED
g1-prod-am3-003-sb.servicebus.windows.net 52.166.64.12 FAILED
g2-prod-am3-003-sb.servicebus.windows.net 52.166.69.241 FAILED
g3-prod-am3-003-sb.servicebus.windows.net 52.166.69.211 FAILED
g4-prod-am3-003-sb.servicebus.windows.net 52.166.66.216 FAILED
g5-prod-am3-003-sb.servicebus.windows.net 52.166.69.250 FAILED
g6-prod-am3-003-sb.servicebus.windows.net 52.178.45.230 FAILED
g7-prod-am3-003-sb.servicebus.windows.net 52.174.47.185 FAILED
g8-prod-am3-003-sb.servicebus.windows.net 52.174.44.171 FAILED
g9-prod-am3-003-sb.servicebus.windows.net 13.95.229.200 FAILED
g10-prod-am3-003-sb.servicebus.windows.net 13.95.226.199 FAILED
g11-prod-am3-003-sb.servicebus.windows.net 13.95.228.112 FAILED
g12-prod-am3-003-sb.servicebus.windows.net 13.95.224.18 FAILED
g13-prod-am3-003-sb.servicebus.windows.net 13.95.230.127 FAILED
g14-prod-am3-003-sb.servicebus.windows.net 13.95.229.144 FAILED
g15-prod-am3-003-sb.servicebus.windows.net 13.95.229.46 FAILED
g16-prod-am3-003-sb.servicebus.windows.net 51.137.36.189 FAILED
g17-prod-am3-003-sb.servicebus.windows.net 51.137.36.194 FAILED
g18-prod-am3-003-sb.servicebus.windows.net 51.137.36.195 FAILED
g19-prod-am3-003-sb.servicebus.windows.net 51.137.36.198 FAILED
g20-prod-am3-003-sb.servicebus.windows.net 52.157.212.39 FAILED
g21-prod-am3-003-sb.servicebus.windows.net 52.157.212.44 FAILED
g22-prod-am3-003-sb.servicebus.windows.net 52.157.212.54 FAILED
g23-prod-am3-003-sb.servicebus.windows.net 52.157.212.68 FAILED

[v-zhangti]

Hi, @Anonymous 

Has your problem been solved, if so, please consider Accept a correct reply as the solution or share your own solution to help others find it.

Best Regards

[v-zhangti]

Hi, @Anonymous 

If the test succeeded, your gateway connected to all the required ports. If the test failed, your network environment might have blocked the required ports and servers. You might need to contact your network admin to open the required ports.

Best Regards,

Community Support Team _Charlotte

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[ibarrau]

Hi. It might be difficult for us to find the specific network issue for this. However I can say that the issue is in the machine where you have installed the gateway. You need some specific ports and connections. You can find all the network configuration details in here:
https://docs.microsoft.com/en-us/data-integration/gateway/service-gateway-communication

I hope that helps,

[Anonymous]

Hi ibarrau,

Tnanks for the guidance, but it still doesn't fully work.
I uninstalled the on-prem gateway and installed a new one, but now I cannot put Synapse (Serverless SQL endpoint) as one of my data sources. The source is automatically recognized as SQL Server, but when I try to add it, an error message pops out: "We could not register this data source for any gateway instances within this cluster..."

Were there any changes made to Microsoft's policy on adding cloud sources to on-prem gateway? I was able to add both on-prem and cloud (Synapse) sources couple of weeks ago.
If that's the case, should I create new gateway directy in Azure?

[ibarrau · Accepted solution]

Hello. Ok. Now we know a source. Some cloud sources won't need a gateway at all. Azure sources for example won't need it. However if you have an on premise source and a cloud source you do need a gateway and a configuration because you have "Hybrid sources (on premise and cloud)".

Go to the gateway settings and check this option to make serverless undependant from the gateway:

Gatewayoptions

That option will help you handle both sources. Then you can go to "Schedule Refresh" and edit credentials under "Datasources credentials" for the serverless. That would be all. You don't need to add the cloud source it as a gateway source.

I hope that helps,

[Anonymous]

You are aboslutely right, it works 🙂
Thank you for the timely reply!