Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Get Fabric certified for FREE! Don't miss your chance! Learn more

Reply
GlynMThomas
Resolver I
Resolver I

Fabric Gateway Setup

Hi,

 

We've setup a fabric gateway so we can ingest data from our on prem resources. The gateway iteself is setup and registered with our fabric tennant and we can see it in fabric and select it for data connections. However when trying to connect through it to our on prem database I'm getting the following error:

Please check your network connectivity to ensure your on-premises data gateway can access ne.frontend.clouddatahub.net and restart the service to retry the connection again once the connectivity issue has been resolved.

Activity ID: 9400b69a-de1b-4e59-bef4-be1902fa31ef

I have checked the connectivity to this url on the gateway server and it seems fine:

 

# 1) DNS + TLS to the Fabric front end
tnc ne.frontend.clouddatahub.net -Port 443 -InformationLevel Detailed
ComputerName : ne.frontend.clouddatahub.net
RemoteAddress : 48.209.130.115
RemotePort : 443
NameResolutionResults : 48.209.130.115
MatchingIPsecRules :
NetworkIsolationContext : Internet
IsAdmin : False
InterfaceAlias : Ethernet 2
SourceAddress : 10.140.18.2
NetRoute (NextHop) : 10.140.18.30
TcpTestSucceeded : True

I've also ran diagnostics on the gateway and it seems to be able to connected to everything required:

 

General Information
Service Bus Namespace : WABI-NORTH-EUROPE-O-PRIMARY-relay2.servicebus.windows.net
Host Name : ns-prod-db3-001.northeurope.cloudapp.azure.com
Host IP Address : 172.205.67.145
 
Proxy configuration : Proxy settings match for all Gateway process configurations.
 
Overall Results : 31/31 tests succeeded.
 
Note: If one or more tests failed, contact your network administrator to open the ports for the required servers.
Firewalls often intermittently allow traffic on blocked sites. Even if a test succeeds, you may still need to allowlist that server on your firewall.
 
Summary:
Server Name:                                       IP Address:          Test Results: 
gv20-prod-db3-001-sb.servicebus.windows.net        20.234.40.147        Success   
gv10-prod-db3-001-sb.servicebus.windows.net        40.67.236.69         Success   
gv1-prod-db3-001-sb.servicebus.windows.net         40.113.56.142        Success   
gv29-prod-db3-001-sb.servicebus.windows.net        68.219.120.117       Success   
gv11-prod-db3-001-sb.servicebus.windows.net        74.178.124.248       Success   
gv7-prod-db3-001-sb.servicebus.windows.net         74.178.124.250       Success   
gv21-prod-db3-001-sb.servicebus.windows.net        74.234.50.71         Success   
gv12-prod-db3-001-sb.servicebus.windows.net        40.113.56.98         Success   
gv6-prod-db3-001-sb.servicebus.windows.net         40.67.236.60         Success   
gv25-prod-db3-001-sb.servicebus.windows.net        40.113.33.94         Success   
gv13-prod-db3-001-sb.servicebus.windows.net        40.67.236.70         Success   
gv0-prod-db3-001-sb.servicebus.windows.net         74.178.124.61        Success   
gv22-prod-db3-001-sb.servicebus.windows.net        40.67.224.118        Success   
gv14-prod-db3-001-sb.servicebus.windows.net        74.234.45.105        Success   
gv8-prod-db3-001-sb.servicebus.windows.net         40.113.56.111        Success   
gv23-prod-db3-001-sb.servicebus.windows.net        20.82.160.93         Success   
gv15-prod-db3-001-sb.servicebus.windows.net        128.251.48.196       Success   
gv4-prod-db3-001-sb.servicebus.windows.net         74.178.124.72        Success   
gv28-prod-db3-001-sb.servicebus.windows.net        20.123.80.155        Success   
gv16-prod-db3-001-sb.servicebus.windows.net        20.13.154.86         Success   
gv3-prod-db3-001-sb.servicebus.windows.net         40.67.236.55         Success   
gv24-prod-db3-001-sb.servicebus.windows.net        20.67.233.185        Success   
gv17-prod-db3-001-sb.servicebus.windows.net        74.234.20.174        Success   
gv5-prod-db3-001-sb.servicebus.windows.net         40.113.56.106        Success   
gv27-prod-db3-001-sb.servicebus.windows.net        72.145.3.30          Success   
gv18-prod-db3-001-sb.servicebus.windows.net        128.251.48.156       Success   
gv2-prod-db3-001-sb.servicebus.windows.net         40.113.56.179        Success   
gv26-prod-db3-001-sb.servicebus.windows.net        20.82.184.205        Success   
gv19-prod-db3-001-sb.servicebus.windows.net        20.13.157.1          Success   
gv9-prod-db3-001-sb.servicebus.windows.net         40.67.236.50         Success   
ne.frontend.clouddatahub.net                       N/A                  Success   
 
Detailed Results
Server Name: gv20-prod-db3-001-sb.servicebus.windows.net        IP Address: 20.234.40.147
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: gv10-prod-db3-001-sb.servicebus.windows.net        IP Address: 40.67.236.69
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: gv1-prod-db3-001-sb.servicebus.windows.net         IP Address: 40.113.56.142
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: gv29-prod-db3-001-sb.servicebus.windows.net        IP Address: 68.219.120.117
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: gv11-prod-db3-001-sb.servicebus.windows.net        IP Address: 74.178.124.248
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: gv7-prod-db3-001-sb.servicebus.windows.net         IP Address: 74.178.124.250
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: gv21-prod-db3-001-sb.servicebus.windows.net        IP Address: 74.234.50.71
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: gv12-prod-db3-001-sb.servicebus.windows.net        IP Address: 40.113.56.98
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: gv6-prod-db3-001-sb.servicebus.windows.net         IP Address: 40.67.236.60
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: gv25-prod-db3-001-sb.servicebus.windows.net        IP Address: 40.113.33.94
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: gv13-prod-db3-001-sb.servicebus.windows.net        IP Address: 40.67.236.70
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: gv0-prod-db3-001-sb.servicebus.windows.net         IP Address: 74.178.124.61
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: gv22-prod-db3-001-sb.servicebus.windows.net        IP Address: 40.67.224.118
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: gv14-prod-db3-001-sb.servicebus.windows.net        IP Address: 74.234.45.105
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: gv8-prod-db3-001-sb.servicebus.windows.net         IP Address: 40.113.56.111
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: gv23-prod-db3-001-sb.servicebus.windows.net        IP Address: 20.82.160.93
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: gv15-prod-db3-001-sb.servicebus.windows.net        IP Address: 128.251.48.196
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: gv4-prod-db3-001-sb.servicebus.windows.net         IP Address: 74.178.124.72
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: gv28-prod-db3-001-sb.servicebus.windows.net        IP Address: 20.123.80.155
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: gv16-prod-db3-001-sb.servicebus.windows.net        IP Address: 20.13.154.86
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: gv3-prod-db3-001-sb.servicebus.windows.net         IP Address: 40.67.236.55
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: gv24-prod-db3-001-sb.servicebus.windows.net        IP Address: 20.67.233.185
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: gv17-prod-db3-001-sb.servicebus.windows.net        IP Address: 74.234.20.174
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: gv5-prod-db3-001-sb.servicebus.windows.net         IP Address: 40.113.56.106
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: gv27-prod-db3-001-sb.servicebus.windows.net        IP Address: 72.145.3.30
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: gv18-prod-db3-001-sb.servicebus.windows.net        IP Address: 128.251.48.156
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: gv2-prod-db3-001-sb.servicebus.windows.net         IP Address: 40.113.56.179
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: gv26-prod-db3-001-sb.servicebus.windows.net        IP Address: 20.82.184.205
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: gv19-prod-db3-001-sb.servicebus.windows.net        IP Address: 20.13.157.1
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: gv9-prod-db3-001-sb.servicebus.windows.net         IP Address: 40.67.236.50
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
Server Name: ne.frontend.clouddatahub.net                       IP Address: N/A
 
Port:      Status:    Proxy Uri:                    
443        Open       N/A                           
 
GlynMThomas_0-1769080947475.png

This is happening when trying to create a new SQL server dataset connection in fabric. I'm a bit stumped as to what could be the issue. Any ideas would be appreciated.

 

Kind Regards

 

Glyn

1 ACCEPTED SOLUTION

Hi @GlynMThomas 

 

Try the following-

 

Restart Gateway services:

  1. Open Services.msc
  2. Look for "On-premises data gateway service"
  3. Ensure its status is Running
  4. If not, right‑click > Start
  5. If it is running, right‑click > Restart

Run Gateway Diag:

  1. Open the On-premises data gateway app on the server
  2. Go to Diagnostics
  3. Run "Start new test"
  4. Check Last completed test results for blocked URLs/ports

Check Firewall whitelisting for outbound 443:

*.frontend.clouddatahub.net

 

I trust this will be helpful. If you found this guidance useful, you are welcome to acknowledge with a Kudos or by marking it as a Solution.

View solution in original post

8 REPLIES 8
v-sgandrathi
Community Support
Community Support

Hi @GlynMThomas,

 

Just wanted to check regarding your question. We haven’t heard back and want to ensure you're not stuck. If you need anything else or have updates to share, we’re here to help!

 

Thank you.

v-sgandrathi
Community Support
Community Support

Hi @GlynMThomas,

Thank you @KevinChant and @deborshi_nag for your response to the query.

Since we haven't heard back from you yet, I'd like to confirm if you've successfully resolved this issue or if you need further help?

If you still have any questions or need more support, please feel free to let us know. 

We are more than happy to continue to help you.

deborshi_nag
Resident Rockstar
Resident Rockstar

Hi @GlynMThomas  Is ne.frontend.clouddatahub.net  your on-premise SQL Server? Have you checked 1433 port from the gateway? 

 

Test-NetConnection -ComputerName <server> -Port 1433

I trust this will be helpful. If you found this guidance useful, you are welcome to acknowledge with a Kudos or by marking it as a Solution.

Hi,

Yes I've tested the URL and port from the gateway server. It's in the original body of this post. I used powershell to test the connection and it succeeded. 

Hi @GlynMThomas 

 

Try the following-

 

Restart Gateway services:

  1. Open Services.msc
  2. Look for "On-premises data gateway service"
  3. Ensure its status is Running
  4. If not, right‑click > Start
  5. If it is running, right‑click > Restart

Run Gateway Diag:

  1. Open the On-premises data gateway app on the server
  2. Go to Diagnostics
  3. Run "Start new test"
  4. Check Last completed test results for blocked URLs/ports

Check Firewall whitelisting for outbound 443:

*.frontend.clouddatahub.net

 

I trust this will be helpful. If you found this guidance useful, you are welcome to acknowledge with a Kudos or by marking it as a Solution.
KevinChant
Super User
Super User

Can your gateway definitely connect to your on-prem source in your own network?

As far as I can tell yes, I did a tcp connection test to both the dns name and ip with the port for the SQL db and it came back successful.

Okay, did you also test with a UDL file to confirm for certainty the SQL connection is there?
https://learn.microsoft.com/en-us/troubleshoot/sql/database-engine/connect/test-oledb-connectivity-u... 

Helpful resources

Announcements
Join our Fabric User Panel

Join our Fabric User Panel

Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.

February Fabric Update Carousel

Fabric Monthly Update - February 2026

Check out the February 2026 Fabric update to learn about new features.

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.