Paginated Report Fails to Load from Remote Client with Error NET::ERR_CONNECTION_RESET; Works Locall

[zhouli]

We are experiencing an issue where a specific paginated report (.rdl) fails to load in the Edge browser on a remote client machine. The browser's developer tools (F12) show the following error for a critical POST request:

POST http://xxx/ReportServer/Pages/ReportViewer.aspx?%2fnvhtest&rc%3ashowbackbutton=true  net::ERR_CONNECTION_RESET

​​Key Details and Troubleshooting Steps Already Performed:​​

1. ​​Environment:​​

   • •​​Report Server:​​ Power BI Report Server (Version: May 2024)
   • •​​Client Browser:​​ Microsoft Edge . The issue is reproducible with IE mode enabled and the server URL added to the Trusted Sites zone.
   • •​​Data Source:​​ The paginated report uses a SQL Server data source configured with ​​stored username and password​​ (not Windows Integrated Security).

2. ​​Error Symptoms:​​

   • •The report page shows "Loading..." indefinitely.
   • •The NET::ERR_CONNECTION_RESET error occurs on a POST request to ReportViewer.aspx during initial load/rendering.
   • •​​Crucially, the Power BI Report Server logs show no corresponding error events,​​ suggesting the server believes it processed the request successfully or the failure occurred at the network/transport layer.

3. ​​Contrasting Behavior (Core to the Issue):​​

   • •​​The same paginated report opens successfully​​ when accessed from a web browser ​​directly on the report server machine​​ .
   • •​​Power BI reports (.pbix)​​ that use the ​​exact same data source​​ (with stored credentials) open successfully from the ​​remote client's Edge browser​​.
   • •This confirms that general connectivity from the client to the report server and basic data source connectivity are functional. The problem is isolated to this specific paginated report type when accessed remotely.

4. ​​Critical Additional Information:​​

   • •​​Server Firewall and Security Software Disabled:​​ We have completely disabled the Windows Firewall and any third-party antivirus/security software on the report server itself. ​​The NET::ERR_CONNECTION_RESET error persists.​​ This confirms the connection reset is not caused by a security policy on the server actively blocking the request.

​​Request for Support:​​

The evidence suggests the issue is related to how the paginated report processor handles the initial rendering request (the POST) for a remote client versus a local one, potentially involving authentication handoff or data transmission. Since Power BI reports work fine, the problem is specific to the SSRS engine component.

We request assistance in investigating:

• •Why the POST request to ReportViewer.aspx is being terminated/reset specifically for remote clients.
• •The potential difference in authentication or data processing context between a locally and remotely initiated paginated report session.
• •Any required configuration for Kerberos Constrained Delegation (KCD), even when using stored credentials, if the report is configured to "Impersonate the authenticated user" after connecting with those credentials.

[v-saisrao-msft]

Hi @zhouli,

The NET::ERR_CONNECTION_RESET error that appears when loading a paginated report remotely is most likely caused by a Kerberos authentication failure due to missing SPNs for the Report Server service account. To resolve this, you can either register the required SPNs with the setspn command or set the report server to use NTLM only by modifying the RSReportServer.config file. This will help prevent connection resets when Kerberos authentication fails.

Troubleshoot Reporting Services report rendering issues - SQL Server Reporting Services (SSRS) | Mic...

Troubleshoot paginated report execution issues - Power BI | Microsoft Learn

Configure Windows authentication on the report server - SQL Server Reporting Services (SSRS) | Micro...

Thank you.

[v-saisrao-msft]

Hi @zhouli,

Have you had a chance to review the solution we shared by @Jaspreet99 @Shahid12523? If the issue persists, feel free to reply so we can help further.

Thank you.

[Jaspreet99]

@Shahid12523  Just a note here. I see you’re posting replies almost every minute. That kind of pace makes it seem like these are auto-generated rather than genuine contributions. If it’s only generic answers, people might as well go straight to GPT instead of coming here. The real value is when we share fixes we’ve tried or insights from our own work.

I’ll mark this one as inappropriate since it doesn’t feel in the spirit of the community.

[Shahid12523]

- Issue: Paginated report fails remotely with NET::ERR_CONNECTION_RESET during POST to ReportViewer.aspx; works locally.
- Likely Cause: Network device (proxy/firewall) resets connection due to large or complex POST payload. Could also be Kerberos delegation failure if impersonation is enabled.
-

Fixes to Try:
- Bypass network path (VPN or same subnet) to confirm.
- Disable impersonation if using stored credentials.
- Check SPNs and enable Kerberos Constrained Delegation if impersonation is required.
- Simplify report to test payload sensitivity.
- Use Wireshark or Fiddler to trace the reset source.