Project Web Access keeps returning to dlEULA.asp

[Jeroen Wolfslag]

Hi,

Set up Project Server the way it was meant to be, and everything works like
it should. That is, in the domain itself. However, when I try to reach the
projectserver from outside the domain, the following happens:
1) loginbox (login, works fine)
2) load prereq.asp
3) redirects to dlEULA.asp
4) check the box "I accept the terms in the License Agreement", then click
Next
5) loads download.asp
6) redirects to dlEULA.asp

I have added the site to my "Trusted Sites", where all ActiveX controls are
either enabled, or prompted. There are no files in "C:\WINDOWS\Downloaded
Program Files".

I am calling the site from a box where only http is allowed. Are any other
ports needed? If so, which ones?

TIA

 

[Jeroen Wolfslag]

Found it..

We have rerouted the internal IP address to the external segment. And in the
download.asp page, I found the following code:

//**************************************************************************
**
// Jeroen Wolfslag: This code ensures that the address which calls this
page,
// is also the actual server. Since we have rerouted the internal IP to the
// external segment, this is not going to work. Therefore, skip it..
//**************************************************************************
**
//try
//{
// var referer =
Request.ServerVariables("HTTP_REFERER").Item.toLowerCase();
// var name1 = referer.match(/http*:\/\/([^/:]*)[:]*[^/]*\//)[1] +
referer.match(/(\/[^/]*\/download\/dleula.asp)/)[1];
// var name2 = (g_svr_sServerName + ApplicationVirtualPath() +
"download/dleula.asp").toLowerCase();
//
//
// if (name1 != name2)
// {
// Response.Redirect( "dlEULA.asp" );
// }
//}
//catch( e )
//{
// Response.Redirect( "dlEULA.asp" );
//}

I tried to circumvent it, by commenting out the abovementioned code. But
this is NOT the way to do it: when the page downloaded the controls, I still
ended up with an error message saying that the controls couldn't be
installed properly.

In our ISA server, we checked the box for "Send the origional host header to
the publishing server instead of the actual one (specified above)", and that
fixed my problem.

So in general: make sure the external IP is the same as the IP of the server
itself..