Project Server 2003 and Sharepoint problem connection

[Arnold Sam]

I am testing 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.

 

[Marco Schmucker (Alegri)]

Hi,

we do have the same problem. Both separate servers do have their own FQDN
entries (http://wss.company.com and http://project.company.com), and are both
accessible via those entries. Both can ping and resolve those FQDNS. All
clients do so, too. But when I enter the FQDN info in Project Server for the
connection, it does not find a WSS. Only hostnames do work.

Is there any place where I can supply the FQDN for the WSS in the WSS admin
or even the database (e.g. table "Sites" where I find the hostname for the
site)?

Thanks,

Marco

 

[flashflash]

I found a solution to this.
My system is a test system so I'm not so concerned with security a
this point - and everything is installed on one box at this point. I
you are putting your system on the extranet please be aware of th
security issues.
Enter the registry keys:

Add the following registry key unde
HKLM\Software\Microsoft\Office\11.0\MS
Project\Webclient Server\ProjectServer\Datasets\STS:
• IsExtranet REG_SZ 1
Add the following registry keys unde
HKLM\Software\Microsoft\Office\11.0\MS
Project\Webclient Server\ProjectServer\Datasets\Application:
• ExtranetServerName REG_SZ (server name, e.g., “example.com”)
• ExtranetServerProtocol REG_SZ (http or https)
• ExtranetServerPort REG_SZ (extranet port number)

There is still one problem though that I have not found a solution for
When you click on a task with a linked document and try to go to tha
document - the resolution is still by hostname not FQDN - but if you g
to the DOCUMENTS link you can access that document fine as it use
FQDN.
Anyone have a fix for this one


-
flashflas

 

[7mgte_Supra]

Hello.
Anyone else have come across this issue?
We are having the same problem


-
7mgte_Supr

 

[Gary L. Chefetz \(MVP\)]

If you want to get an answer here, you need to start a post describing your
problem and symptoms. Don't assume you have the same problem. Also, if
you're going to "me-too" post, you need to quote back the prior thread or at
least the important parts. People reading the news groups directly from
Microsoft have a thread retention of only 30days. So, here is your post
without any frame of reference attached. Maybe someone reading on Google
will reply.


--

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

-