Report builder connectivity issue from different machine

Asked Jun 01 '17 at 17:51

Active Jun 01 '17 at 18:50

Viewed 187 times

I am trying to connect Report builder from Machine A and my SSRS is deployed in Machine B

Machine A (Client machine with Report Builder 3) --> Machine B (SSRS 2016 - Configured in Native mode)

I am using Windows Authentication and both the machines are not present in domain. I am able to author a report in report builder in Machine B whereas while trying to author a report from Machine A I am getting below error:

Unable to read data from the transport connection: An existing connection was >forcibly closed by the remote host.

Any idea on how to solve this will be really helpful.

edited Jun 01 '17 at 18:50

asked Jun 01 '17 at 17:51

Kannan Kandasamy

13,405
3
25
38

Confused. How can you use Windows Authentication if both machines are not present in the domain? – SS_DBA Jun 01 '17 at 20:06
that is what my problem statement is... During connection it has to use servers windows credential correct? – Kannan Kandasamy Jun 01 '17 at 20:08
Connection to the SQL Database or just to the SSRS portal to deploy the report? – SS_DBA Jun 01 '17 at 20:12
SSRS portal to deploy the report – Kannan Kandasamy Jun 01 '17 at 20:13
I'm assuming you can't get to the SSRS Report portal from the client either. – SS_DBA Jun 01 '17 at 20:18
Can you add MachineA\Username to the security on MachineB as an Admin? – SS_DBA Jun 01 '17 at 20:19
But that will be out of the security Jurisdiction so it is not authenticating – Kannan Kandasamy Jun 01 '17 at 20:25
Trying to use pass through authentication. – SS_DBA Jun 01 '17 at 20:26
Got a breakthru where I am trying to open the Report Builder as a separate application not from IE, and author the reports and while publishing use servers userid and credential – Kannan Kandasamy Jun 01 '17 at 20:27
Ah. I never open RB from IE. – SS_DBA Jun 01 '17 at 20:28

Report builder connectivity issue from different machine

Unable to read data from the transport connection: An existing connection was >forcibly closed by the remote host.

0 Answers0