Trying to connect Project Pro to Project Server

[stryngz]

I am new to the whole Project Server 2003 and have a question regarding
connectivity. I have set up the odbc driver and everything works fine
when I start up the Microsoft Project, however the default server it is
trying to connect to is set on the private name of the server. I need
it to be set on the public name. I have already set it in the odbc
driver. When I start up Microsoft Project (without vpn access) and it
asks for the password to the project server I type it in and it comes
back with an error. Then the login information pops up and the default
server setting is set on the private name. I then click the drop down
box and select the public name and then am able to get in. How can I
set the server name to automatically choose the public name to connect
too? I'm trying to explain my problem the best that I can since like I
mentioned I am new to this.

 

[Gary L. Chefetz [MVP]]

Stryngz:

A step-by-step description from you would be helpful. You're talking about
setting up ODBC connections, something you shouldn't have to do manually.
This is confusing.

 

[stryngz]

ok, after I had setup the whole project server 2003 configurations,
another group in my company wants to be able to access the project
server by using the client project pro without having to have a private
connection (VPN). We set up a public address for the server that has
the whole project server installed. In project pro under enterprise
options I believe, we set up an account to access the public address
with the appropriate database user. We then setup an account in the
odbc driver of my local machine. We made sure that we used sql
authentication and used the login for the database in the driver.
After we set that up, we exit the project pro client and then started
it back up. This time the login prompt to access the project server
website pops up. We type in the user and password and it just sits
there for a few seconds. An error pops up stating that the connection
failed and after I click ok, a login prompt pops up that has the
server, login name and password. The server option has the private
server name there by default, when I click the drop box then there is
the public name to the server. I then select the public address and
click ok and then it connects. How can I by default have the public
address name to the database and not the private name?
Sorry if I am really confusing you but like I mentioned I am very new
to this whole concept. Thanks for the help

 

[Gary L. Chefetz [MVP]]

stryngz:

Are you only looking to expose Project Web Access? If not, you should be
aware that the Project Client is not going to perform well, if at all, and
that this arrangement would be a huge security risk. With that said, the
proper way to expose PWA to the Internet is to setup a second front end in
your DMZ pointing to the same database, using SSL and basic Authentication.

 

[Mindaugas Bliudzius]

i had some problem, there is some .exe (don't remember know ) witch allow to
chance credentirials used to connect to projectserver (it must be used on
server). Also i remember i needed to set remember my password in explorer
options.

 

[stryngz]

Is there a way I can post screen shots so that I can show what problem
I am having? It's hard to explain it since I am a beginner. As far as
the .exe where else could I find more info about this? Thanks all for
the help.

 

[stryngz]

ok, I found this article in microsoft that seems to be what is stopping
me from connecting to the project server from project pro without
having to use the vpn:

http://support.microsoft.com/?kbid=837653

It states about using the ConnInfo.exe in the server to set the login
information. However when I try to change the "server\instance" to the
public address we have created for the project server, I then get an
error message stating that the database cannot be accessed at this
time. Can anyone lend me a hand on how to set it to access the public
address by default instead of the "server\instance"? Thanks

 

[stryngz]

After many, many trials I finally decided to re-install the whole thing
and now it seems to work. Guess I must have did something wrong on the
initial setup. Thanks everyone for your help.