Tell me more ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.
up vote 0 down vote favorite

I have a SharePoint 2007 setup that is primarily used inside a company, meaning all users access it through the intranet on an url like "moss01.sub.domain.com". Everything is working as intended.

However, the company needs to allow certain users outside the network access to the site. All new users are put in a seperate SharePoint group from the regular users, and everything works fine when testing internally.

However, users who access the site externally through a Citrix Gateway using Citrix Netscaler experiences mangled URLs and missing resources. The citrix netscaler acts as a proxy that translates the external url, "portal.domain.com" to the internal address "moss01.sub.domain.com" behind the scenes. However, Netscaler also inserts a specific token url along the lines of "/cvpn/Ay534FjjMbdl51dpwe/" after the domain, which causes some URL's that are created through javascript or has been inserted as a setting into webparts or similarly "hardcoded" to point to a wrong url.

Correct translation: portal.domain.dk/cvpn/token/Pages/default.aspx -> moss01.sub.domain.dk/Pages/default.aspx

Wrong translation: portal.domain.dk/SomePage/default.aspx -> ????

Some URL's even reference the "moss01"-domain. Basically Netscaler cannot translate all the URLs - is there some way to approach this or some way to alter SharePoint to be aware of this?

share|improve this question

closed as off topic by Alex Angas Jun 6 '11 at 7:15

Questions on SharePoint Stack Exchange are expected to relate to SharePoint within the scope defined in the FAQ. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about closed questions here.

2 Answers

up vote 0 down vote

SharePoint does not support proxies that re-write anything other than the "host" part of the URL, so while the Alternate Access Mapping concept can help you with translating moss01.sub.domain.dk to portal.domain.dk no problem, the token insertion is going to create issues. Microsoft refers to this as "asymmetrical paths", and they explicitly noted as being unsupported. FWIW, I've experienced very similar issues trying to use a Juniper SSL-VPN product which does similar URL re-writes. Some functions work fine, but you probably won't be able to get to 100% functionality.

share|improve this answer
up vote 0 down vote

you could Add an alternate access mapping for sharepoint to use the "external" domain so that it doesnt need to translate anything, or even just extend it on to a new application (with external domain) and allow port 80 traffic to it through your firewall/router?

share|improve this answer
Alternate access mappings only apply if you access the site directly, but through another URL - since Netscaler is translating the content (afaik) it has no effect. I have thought of simply asking them to tunnel traffic through since they already have the new domains setup, but it's a bit of a shift to do that. – cpn Nov 12 '10 at 12:35
I know, but if you think about it, when you set up an alternate access mapping theres no translation being done because the netscaler is passing through the same address then the resources will all be mapped to the correct location (including the generated ones you are having an issue with) which should get rid of your issue.. – Mauro Nov 15 '10 at 8:41

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