.NET APP: Issues rendering SQL RS report externally

[donovant]

HI There,

We have an in-house vb.net/C# application which basically serves as a database front end.

The application was initially desgned primarily for in-house use only, however recently the apllication is being by a few users working from home, and they have come accross a few issues which did not occur when they used the application in the office. The main issue is that the batch report generator function of the application generates the following error on the ReportExecutionService.loadreport call when used externally.

Client found response content type of '', but expected 'text/xml'
at System.Web.Services.Protocols.SoapHttpClientProtoc ol.ReadResponse (.. ommitted)

However the error is not generated when the application is run on the local network, rather the reports are loaded and rendered successfully. The batch reporting module uses the ReportExecutionService.render to generate the reports, but the above error message is first generated on the loadreport function.
I have checked the ReportExecutionService.url property and it is pointing to the externally available SS RS webservice (http://SERVER-IP/ReportServer/ReportExecution2005.asmx). I have also check that credentials are correct as well as the report path. And as i said, it workes perfectly when connected to the local area network.

Can anybody suggest a likely reason for this issue?

[kenobewan]

Referencing is likely to be the main problem. When I log into the office from home I notice some differences. They are negated by the fact that I can still remote into my work desktop.

I take it that this application is not set up as asp.net? If this is correct, then there may well be a referencing issue. Suggest reminding staff of scope creep and costing the upgrade ;).