Forum Discussion

D_Lav's avatar
D_Lav
Helper I
11 months ago
Solved

Gateway installation error - Network request returned unexpected errors

Hi!   i have installed standard on-premise gateway on a server and after installation it wants me to sign-in. Here i cant get past the error "Network request returned unexpected error"     ...
Need Help
  • collinq's avatar
    collinq
    11 months ago

    Hi D_Lav ,

    I am wondering if the issue is in DNS policies - perhaps the you do not have a public DNS resolver?  Are you allowing all the possible domains - they should be *.powerbi.com, *.analysis.windows.net or *. servicebus.windows.net.

    OR, do you have some sort of antivirus software that is blocking it?  Either by domain or endpoints?

    Is there a log being built that maybe gives a hint?  That should be at: C:\Users\<GatewayServiceAccount>\AppData\Local\Microsoft\On-premises data gateway\GatewayConfiguratorLogs

    OR, you could just run a network trace with something like Fiddler to see where the block might be occuring.

  • D_Lav's avatar
    D_Lav
    10 months ago

    i think its solved! FOR some reason, DNS was able to resolve all endpoints except api.powerbi.com. So Powerbi.com could be resolved which was weird. It seemed to be on server side so what we (Security person and i) eventually did was to update C:\Windows\System32\drivers\etc - Hosts file with the following, 

     api.powerbi.com
     api.privatelink.analysis.windows.net

     

    After this it worked. 

     

tayloramy's avatar
tayloramy
Super User
11 months ago

Hi D_Lav, 

 

Based on the PowerShell output, it appears that not all the ports are open properly, as the test to *.analysis.windows.net failed. 

Can you work with your firewall team to have all of the below ports opened:

Public Cloud Domain names Outbound ports Description

*.download.microsoft.com443Used to download the installer. The gateway app also uses this domain to check the version and gateway region.
*.powerbi.com443Used to identify the relevant Power BI cluster.
*.analysis.windows.net443Used to identify the relevant Power BI cluster.
*.login.windows.net, login.live.com, aadcdn.msauth.net, login.microsoftonline.com, *.microsoftonline-p.com443Used to authenticate the gateway app for Microsoft Entra ID and OAuth2. Note that additional URLs could be required as part of the Microsoft Entra ID sign in process that can be unique to a tenant.
*.servicebus.windows.net5671-5672Used for Advanced Message Queuing Protocol (AMQP).
*.servicebus.windows.net443 and 9350-9354Listens on Azure Relay over TCP. Port 443 is required to get Azure Access Control tokens.
*.msftncsi.com80Used to test internet connectivity if the Power BI service can't reach the gateway.
*.dc.services.visualstudio.com443Used by AppInsights to collect telemetry.
ecs.office.com443Used for ECS configuration to enable Mashup features.

Public cloud domain names Outbound ports Description

*.core.windows.net443Used by Dataflow Gen1 to write data to Azure Data Lake.
*.dfs.fabric.microsoft.com443Endpoint used by Dataflow Gen1 and Gen2 to connect to OneLake. Learn more
*.datawarehouse.pbidedicated.windows.net1433Old endpoint used by Dataflow Gen2 to connect to the Fabric staging lakehouse. Learn more
*.datawarehouse.fabric.microsoft.com1433New endpoint used by Dataflow Gen2 to connect to the Fabric staging lakehouse. Learn more
*.frontend.clouddatahub.net443Required for Fabric Pipeline execution


Adjust communication settings for the on-premises data gateway | Microsoft Learn

 
If this helps, please consider giving Kudos. If I answered your question, mark this post as the solution