Project Web Access and Sharepont FQDN

[support]

I am running Project Server 2003 with Sharepoint links
and all work well in the intranet but when accessing from
the extranet the Sharepoint site information cannot be
accessed.
From what I can tell, the Project Web Access is linking
to http://servername/sites/.. where it should be
linking to http://servername.domain.com/sites/.. I can
access the project server with the FQDN
http://servername.domain.com/projectserver so the DNS is
setup and resolving correctly.
I have tried changing the Project / Sharepoint reference
in the admin Sharepoint section from
http://servername:80/sites to
http://servername.domain.com:80/sites but even though the
test link resolves it correctly when I try to save the
change I get an error:

"Project Server cannot connect to the specified Web server
running Windows SharePoint Services. Please check the HTTP
protocols and the port numbers in both URLs".

I tried changing this reference direct on the database as
well as some registry entries to the FQDN but the changes
cause either project server or Sharepoint to not work
altogether.

I can resolve http://servername.domain.com/projectserver
both on the intranet and the extranet so this is not a
DNS issue.

I can see that the project web access links to
http://servername both internally and externally so I'm
trying to change this to reference
http://servername.domain.com how do I do this?

This must be possible somehow otherwise this would be
unuseable over the internet.

 

[rome]

we have found a temporary workaround.
add an entry to each remote client machine's hosts file:

10.10.10.10 servername
(public ip) (netbios name)

anyone have the real solution?
thanks.

 

[Gary L. Chefetz \(MVP\)]

Rome:

In Project Web access, have you entered an extranet address for SharePoint?
Admin > Manage Windows SharePoint Services > Connect to Server

--

Gary L. Chefetz, MVP
"We wrote the book on Project Server
http://www.msprojectexperts.com

-

 

[Guest]

Hello, Thank you for your reply.

Ill try to explain our set up the best way i can.

currently, our company website is on top of sharepoint:
wwww.ourcompanysite.com

from there - we have a link to projectserver.
we also have an operations site - which really is the
sharepoint site with all the shared documents and fancy
stuff =)
everything works 100 percent, exception of projectserver.
for example:
1. i go to "Task"
2. i select an item from the "Task Name"
3. i click on "Link Risks"
4. then click on "New Risk"
5. then select one of the items from
"Relationship Description combobox"
6. and click on the command button "Go".

once i click on the "Go" button, i noticed the webrowser
is attempting to connect to
http://netbiosname/sites/projectserver_102/lists/risks/newf
orm.aspx?

instead of:
http://extranetname/sites/projectserver_102/lists/risks/new
form.aspx?

we have sql server, sharepoint, and project server loaded
on one physical machine.

hope this all make sense.

 

[John Sitka]

Do you have multiple IP's bound to the NIC?

 

[Guest]

Hello,
as far as i know - we only have one public ip for the
machine.

 

[John Sitka]

public or private not an issue. Logical is.
I had an issue with multihomed network cards.


http://groups.google.ca/groups?hl=e...tihomed+sitka&meta=group%3Dmicrosoft.public.*

 

[Gary L. Chefetz \(MVP\)]

Rome:

From your description, everything works fine except linking to SharePoint.
Project Server is behaving as expected and so is SharePoint. I can't say for
sure, but it seems to me that you haven't got the correct architecture in
place to support what you're trying to accomplish. If you want this
functionality to fly on the Extranet and the Intranet, you'll need two front
ends; one facing the extranet and one facing the intranet, both sharing the
same data. This applies to both SharePoint and Project Server.

--

Gary L. Chefetz, MVP
"We wrote the book on Project Server
http://www.msprojectexperts.com

-