>>>If it is then all you need be sure of is that the IIS account used by that page on the report server (as determined above) has sufficient permissions/rights to access the required folders on that server.
>>>If the page is NOT allowing anonymous access then your HttpRequest much include credentials that will be recognized as valid by the report server. This won't change the account used to process the page on the report server.
>>>What happens if you try accessing the url from a browser? Are you prompted for login information?
>>
>>Yes, I get prompted for the Administrator password, but just the first time.
>Once you've logged in once it will persist until the browser is closed.....
>
>I'd suggest temporarily allowing anonymous access the the url you are trying to reach with the HttpRequest. That way the credentials you send (if any) are irrelevant.
>If the process still fails then the problem will be internal to the report server - you'll still need to determine the IIS account being used to process the request and make sure it has sufficient access permissions.
>If it succeeds then remove the anonymous access and try hard coding the administrators credentials as the HttpRequest.Credentials.
>(JIC : You can change the anonymous access setting by opening the page properties / File Security / Authentication /Edit and toggling the check box)

Sorry, I'm not clear where I need to open "the page properties / File Security / Authentication /Edit". Where do I find that?