Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have a publicly available web server (although IP restricted, usernames / passwords etc) that we need to be able to present reports through. Our report server is located at a different site, so we need to be able to open ports for this.

Our initial consideration is to move the reportserver virtual directory from port 80 to a different port - any recommendations?

Also, as reporting services uses Windows authentication, what is the best way for the server to securely authenticate for this application only?


share|improve this question

We setup ours using SSL, and Windows Auth on the normal port 443 with port 80 redirecting to 443 before prompting for username and password. Our external user base is pretty small so we just created them domain accounts.

share|improve this answer
Nice thing about this approach is if it's all domain users, or at least a very small number of users, you can use a certificate issued by your own CA, which is what we've done. – Mark Henderson Aug 11 '09 at 1:20

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.