How to connect project server on the Internet

G

Gerard

Hi,

Newbie question (i guess): Got MS project server 2007 up and running. Works
fine on the intranet. But can't reach it from the internet. Popup box is
displayed credentials correctly passed but after that no project (but a
search enigne). Did a "create and extent" of the sharepoint site and made
one for the internet port 8888. But still, typing http://<myIpAdd>:8888/pwa
i can just logon, but nothing else appears.
Thanks for any help!
Gerard
 
P

Paul Conroy

Is your firewall nat'ing the address or are you hitting the site with the
public address ? If the former, I would suggest using a DNS alias and not
IP addr. Changing to a DNS alias will require a new AAM for you externally
facing site.

P
 
G

Gerard

Hi Paul,

Thanks for the anwer! Guess iam not a network specialist. What i did was
just creating a NAT mapping in the router for the outside world to the
server running ProjectServer2007. Something like this functions without a
problem for a Sharepoint server. Are you saying that the firewall might be
the problem? Iam typing the public ip-addr: hhtp://xyz.asd.qwe.erd:8888/pwa
(just like i do reaching sharepoint (using a different port). Sharepoint
pops up with logon and continues after a passing the correct credentials;
Project comes with the same logon but there it stops).
Any idea how to fix this?

Gerard
 
B

Brian Smith \(MSFT\)

Do you have an AAM address for hhtp://xyz.asd.qwe.erd? If not then it may
be redirecting to whatever you have in AAM and may not be available on the
internet. SharePoint may not need to redirect so it works for simple sites.
 
G

Gerard

Thanks Brian,
No don't got any AAM, never heard from it, never needed it too (is it
alternate address mapping?)
How to set it up?
Thanks,
Gerard
 
B

Brian Smith \(MSFT\)

Yes, it is alternate access mapping. Basically if the AAM points to
http://servername but you can hit the same server with
http://xyz.asd.qwe.erd:8888 then if you are using a PWA site it will
redirect to http://servername/pwa from the fully qualified domain name (same
if you tried the IP address) - and usually your client will not know how to
get to http://servername. You can add another public URL in AAM
representing another zone (and set you desired authentication method) and
then set http://xyz.asd.qwe.erd:8888 as the URL and you will be able to
avoid the redirect.
 
G

Gerard

Brian, thanks for the useful information!

Brian Smith (MSFT) said:
Yes, it is alternate access mapping. Basically if the AAM points to
http://servername but you can hit the same server with
http://xyz.asd.qwe.erd:8888 then if you are using a PWA site it will
redirect to http://servername/pwa from the fully qualified domain name
(same if you tried the IP address) - and usually your client will not know
how to get to http://servername. You can add another public URL in AAM
representing another zone (and set you desired authentication method) and
then set http://xyz.asd.qwe.erd:8888 as the URL and you will be able to
avoid the redirect.
Click to expand...
 
Top