Internal Address??

J

Joey

When we create sites for our projects to share documents we have a problem.
The address it uses to create the link is the address that we have configured
in the form "Manage Windows SharePoint Services". The problem with this is
it creates a link as if we were on the internal side of the network. For
instatance it makes a site for the project "GogoDolls" with the address of:

http://server1/sites/projectserver_101

I understand it is doing this because the form for connect to a sharepoint
server is set to http://server1/sites

The problem though is when I want to view the pages outside of the company
network the address is still the internal address and not something like:

http://project.company.com/sites/projectserver_101

I have tried to setup the address on the Connect to Sharepoint Server so it
is an external address but it doesn't let you do this.

Will I ever be able to see the documents through the external web site? I
think this could be a big problem. We have access to all the info on the
project web site except for documents?

Thanks!
 
G

Gary L. Chefetz \(MVP\)

Joey:

You need to firstly, have a way of connecting to Project Server using
Windows Authentication for this to work. Generally we use two front ends for
this purpose: One facing internally and one facing external users in the
DMZ. After that, you need to set an extranet address for your SharePoint
server under Manage Windows SharePoint Services in Project Web Access. The
setup is explained in the Installation Guide.

--

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

-
 
J

Joey

Gary,

Thanks for the response. I already have the extranet address set to
https://project.myserver.com and it resolves fine and and I can access the
project web site from outside the newtork using windows authentification.
The problem is still when it creates a site for a new project for document
sharing it is setting the site address to the item in the box "Create a site
under this SharePoint URL:" which has to be the server address just like it
has in the example box on that page " (for example,
https://servername:443/sites)" which will never resolve from outside and
therefore never allow someone from outside the network to hit the new sites
created for document sharing.

I am sorry if I misunderstood your answer but I think I do understand and I
still don't understand how an internal address for the sites will ever
resolve outside the newtork.

Thanks again for your help!!
 
G

Gary L. Chefetz \(MVP\)

Besides only making partial sense in the last reply,... I'm not sure I fully
addressed your question. In addition to pointing out how PWA serves up WSS
content, if you use a second front end, you *are* giving the extranet user
an external address to the content. Each user class gets its own front end,
one on SSL facing out, one standard protocol facing in.

--

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

-
 
C

Chris Moran

Okay looking through this thread, I am having the same issue. Here is the
scenario:

1 - I log into PWA from my hotel room ex: http://www.xyx.org/projectserver
using Project Server authentication
2 - I go to the document library and try to access the library..... (windows
authen, but I never get that far.
3- I click on the folder and I can see at the bottom that it is trying to
grab the library from the internal address. ex: http://serverx/sites....etc
4 - the library never loads and I get an error on the page but the PWA
toolbar is still at the top.

I have the external address specified in the server configuration....

The work around that I have is to make an lmhost file with the internal
server name pointing to the external ip address, then this process works
fine.....

Why is this necessary? What am I doing wrong? How do I fix it?

thanks!
 
Top