Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Good.
Someone made an installation from scratch of the local report server where one uploads the different dashboards, I have a problem there, when I upload my dashboard to the local server and it is within the network it lifts me up and you can quickly view the uploaded report, but when I try to enter from another network it enters but it takes a long time to be able to view the report.
I have correctly configured my public domain so that they can enter from the public network to the reports they enter but it takes time to raise the reports someone knows what else I need to configure.
Clarification When you enter the report from the same server to the reports, it quickly raises all the reports.
We have not yet heard back from you about whether the response addressed your query. If it did not, please share more details so we can assist you more effectively.
Thank You.
Hi @Syndicate_Admin
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If the above response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.
Hey @Syndicate_Admin ,
Sure! Here's a fully rewritten, original, and plagiarism-free version of the explanation to address your issue about slow SSRS report loading outside the local network:
You mentioned that your SSRS reports load instantly when accessed from within your local network. However, when attempting to access the same reports using a public network or from outside, they are accessible but take a long time to load. This delay could be caused by several configuration or performance-related factors.
Your internal network benefits from fast LAN speeds. When accessing externally, the response depends heavily on your server’s upload speed, which may be limited on your internet plan.
Fix:
Test your internet speed using tools like Speedtest.net.
Upgrade your connection if the upload speed is low.
Use a business-grade internet package optimized for hosting.
You’ve set up a public domain to reach your report server. If there's any delay in how that domain resolves or routes traffic, it can slow down access.
Fix:
Check DNS resolution speed using tools like nslookup or tracert.
If using a reverse proxy (like NGINX or IIS ARR), ensure it's configured for efficient request handling and proper timeout settings.
Delays can occur if your firewall or router is throttling traffic, or if the server ports (usually 80 and 443) aren't fully optimized for external access.
Fix:
Make sure ports 80 (HTTP) and 443 (HTTPS) are open and properly forwarded.
Enable HTTPS to ensure secure and stable external connections.
Verify that your firewall or NAT isn’t slowing traffic down.
If the reports include large datasets, images, or complex calculations, they may take time to render—especially over a slower external connection.
Fix:
Optimize the report queries to reduce the data size.
Enable caching for frequently accessed reports.
Paginate reports or filter data before rendering.
Use stored procedures instead of heavy inline queries.
SSRS commonly uses Windows Authentication. From external networks, Kerberos or NTLM authentication may cause lags or delays.
Fix:
Consider switching to Forms Authentication or Basic Authentication (with SSL for security).
Review SSRS settings to avoid unnecessary authentication negotiation.
Area Recommended Action
| Internet Connection | Ensure high-speed upload bandwidth |
| Report Server Settings | Enable caching, optimize queries, reduce report size |
| Domain/DNS Setup | Use a reliable DNS and check routing paths |
| Security Configuration | Allow HTTPS and test firewall for any blocks |
| Authentication Mode | Use external-friendly authentication (Forms or Basic) |
Run performance tests using tools like:
Fiddler (for HTTP performance)
Traceroute (to analyze connection hops)
SSRS built-in log files (for report execution time)
Compare local vs. public load times to isolate the delay.
Test reports with smaller data loads to see if the issue is tied to dataset size.
If you found this solution helpful, please consider accepting it and giving it a kudos (Like) it’s greatly appreciated and helps others find the solution more easily.
Best Regards,
Nasif Azam
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
| User | Count |
|---|---|
| 41 | |
| 39 | |
| 37 | |
| 29 | |
| 24 |
| User | Count |
|---|---|
| 122 | |
| 110 | |
| 83 | |
| 69 | |
| 68 |