Windows Server

Berry at JSO · Guest

I have a SPS 2003 portal behind ISA 2004, and all of the links on my portal
homepage work except the "Edit page" link under the Actions menu shows the
virtual server internal IP as the root url.

I had this same problem with some WSS sites, but after applying WSS SP2, I
was able to use addalternatedomain and addzoneurl to remedy the problem.

I tried the same technique after applying SPS 2003 SP2, but I still get the
virtual server internal IP as the root url for the "Edit page" link on the
portal home page.

Any ideas?
--
Berry Morgan
JSO

Wei-Dong XU [MSFT] · Guest

Hi Berry,

As I know, this could be resolved by the Link Translation in ISA 2004. This
article introduces the detailed information for you:
Link Translation in ISA Server 2004
http://www.microsoft.com/technet/prodtechnol/isa/2004/plan/linktranslation.m
spx

Furthermore, for the ISA, you could obtain more information from ISA
newsgroup:
Microsoft.public.ISA

Please feel free to let me know if you have any further question on this
matter.

Best Regards,
Wei-Dong XU
Microsoft Product Support Services
This posting is provided "AS IS" with no warranties, and confers no rights.
It is my pleasure to be of assistance.

Berry at JSO · Guest

If SPS 2003 SP2 is supposed to support extranet configurations like WSS SP2,
why do I have to rely on ISA 2004?
Is the syntax to implement addalternatedomain and addzoneurl different for
SPS 2003 SP2? I haven't seen any discussion of these features for SPS 2003
SP2 on microsoft at msdn or technet.

--
Berry Morgan
JSO

"Wei-Dong XU [MSFT]" wrote:

Wei-Dong XU [MSFT] · Guest

Hi Berry,

SPS is developed based on WSS. The option addalternatedomain and addzoneurl
should be the same for WSS and SPS. Since they didn't work at your
scenario, I gave the suggestion on using ISA. For this issue, I'd suggest
you could raise one case to your Microsoft local Product Support Service.
If this is really a bug, your case will be totally free of charge. Your
local Microsoft PSS is:
http://support.microsoft.com/common/international.aspx

Please feel free to let me know if you have any further question on this
matter.

Best Regards,
Wei-Dong XU
Microsoft Product Support Services
This posting is provided "AS IS" with no warranties, and confers no rights.
It is my pleasure to be of assistance.

Wei-Dong XU [MSFT] · Guest

Hi Berry,

How are you? I'd like to know if anything further we can do for you.

If the issue remains, firstly we could ensure the Sharepoint deployment in
ISA scenario following the Step 15 on Page 72 in the Document: Sharepoint
Portal Server 2003 Document: Deploying on an extranet by using ISA Server
2000 and ISA Server 2004, this can be doanlowded here:
http://www.microsoft.com/downloads/details.aspx?FamilyID=4C5BF9DD-3EFB-451D-
B213-98ED039190BF&displaylang=en
*This will help us to make ISA working very smoothly with Sharepoint.

Especially this step:
In the Configure HTTP policy for rule dialog box, on the General tab, in
the URL Protection section, ensure that the Verify normalization check box
and the Block high bit characters check box are cleared, and then click OK.

If that does not work, I also have a few questions for the customer:
1. Does this issue appear on all his Sharepoint Sites?

2. Does this issue appear in ALL his Portal Areas also?

3. Does the issue occur if the customer creates a new Portal Site?

4. Has the customer edited the main page with Frontpage 2003?

5. Despite the seemingly incorrect URL does the link work?

6. Can we get a screenshot of the problem URL?

7. What exactly does the customer mean by he had the same issues in WSS?
WSS sites do not have the 'Edit Page" link.

Expect to your update!

Best Regards,
Wei-Dong XU
Microsoft Product Support Services
This posting is provided "AS IS" with no warranties, and confers no rights.
It is my pleasure to be of assistance.

	Windows Server Forum Index -> Portal Server Development	All times are GMT
Page 1 of 1