Skip to main content
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Wolfiz

Issue with the Folder connector

Submitted by on ‎01-30-2023 02:47 AM

Hello,

We are in the process of cloudifying our various services but we are having a problem with the NAS connections.

 

Currently we have on-premise gateways on our infrastructure that connect to different sources (that we will call legacy). This solution is fully functional.

 

In the context of the migration we are going to Synapse and Databricks with new gateways (which are in the Azure IAAS). Those gateway must be able to access the NAS (through the folder connector).

Therefore we have opened port 445.

 

The version of the powerbi gateway is the latest (December 2022) and port 445 is open (netuse ok and Test-NetConnection ok, which validates the connection and credentials)

 

However, when we try to create a new connection on the app.powerbi.com we still get this message ...

 

Unable to create data source.
Invalid connection credentials.

Details:

AXA_BE_PBI_DataPlatform_STG: The credentials provided for the Folder source are invalid. (Source at \\s01fs100.axa-be.intraxa\d01v1\626_operations_support.)

Please have this information handy if you choose to create a support ticket.

ActivityId: ca2b952b-2390-4081-a4e1-a043c93e149e
RequestId: efe4ddee-d383-4f00-9566-236cb78b0a0a
Cluster URI: https://api.powerbi.com
Status code: 400
Time: Mon Jan 30 2023 11:30:30 GMT+0100 (Central European Standard Time)

 

So I think there is a problem between the powerbi and the gateway ?

 

Advice ? We must fix that quickly as migration is plan for beginning Feb.

Status: Investigating

Hi @Wolfiz ,

 

The gateway communicates on the following outbound ports: TCP 443, 5671, 5672, and from 9350 through 9354. The gateway doesn't require inbound ports.

 

After the gateway is installed and registered, the only required ports and IP addresses are those needed by Azure Relay, as described for servicebus.windows.net in the preceding table. You can get the list of required ports by performing the Network ports test periodically in the gateway app. You can also force the gateway to communicate using HTTPS.

 

 

Best regards.
Community Support Team_ Caitlyn

See more ideas labeled with:
2 Comments (2 New)
Comments
v-xiaoyan-msft
Community Support
Community Support
‎01-31-2023 10:03 PM
Status changed to: Investigating

Hi @Wolfiz ,

 

The gateway communicates on the following outbound ports: TCP 443, 5671, 5672, and from 9350 through 9354. The gateway doesn't require inbound ports.

 

After the gateway is installed and registered, the only required ports and IP addresses are those needed by Azure Relay, as described for servicebus.windows.net in the preceding table. You can get the list of required ports by performing the Network ports test periodically in the gateway app. You can also force the gateway to communicate using HTTPS.

 

 

Best regards.
Community Support Team_ Caitlyn

Wolfiz
Frequent Visitor
‎02-01-2023 05:58 AM

the gateway itself run smoothly as we are able to do a Net Use from the gateway itself

btw, the gateway has already its synapse/databricks/teradata connection running perfectly

The issue is really located when we want to create a connection using the folder connector - for an unknown reason the credentials are "not ok". 

Idea Statuses