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

WSS 3.0 IIS6/WinSever2003 CAG

We have several WSS sites on a SharePoint WSS box that talk to the outside, all of which are SSL enabled. So you get a CAG(Citrix Access Gateway) to translate the 443 port to the local ssl port on the server.

Everything is set up and works fine until you get into the Site Settings and start rooting around, it seems like a very unstable link library. Links will try to use the local ssl port number instead of the 443 standard; it will try to skip the step. Is that the site? Any ideas on how to fix it?

share|improve this question
up vote 0 down vote accepted

It was the CAG trying to translate the port number intelligently. If I run all the IIS sites on port 443 with CAG's "content switching" feature, the site runs fine. IIS will reject it initially but the vbscript called here basically tells IIS UI to stop whining. Also if you restart IIS without running those scripts, and have two or more sites with the same SSL port, it will halt. Must input the hostheaders on each site in IIS to match that of the context switching rule in the CAG

share|improve this answer

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.