Accessing Project Server 2003 from Project Pro 2003 Through a firewall

[young.russell]

I'm sure this question has been asked to death, but none of the
previous answers I have dug up seem to make sense. It doesn't help I'm
new to Project.

Anyway, I set up a Small-Scale Project Deployment in our company's DMZ.
This means everything is on one server except for the SQL 2000 box,
which is on another server. Both servers are in the DMZ.

Project Pro 2003 will not connect to the Project Server 2003 in the DMZ
from either the Internet or our internal network. I've figured out this
is because Project Pro 2003 is using SQL Port 1433, which obviously I'm
not going to asked to be passed-through the firewall.

Is there any way to not have Project Pro 2003 use SQL through the
firewall? Am I missing something?

I read about using a Front-End server, but I'm confused as to whether
or not a front-end server would remove the necessity or sending SQL
through the Firewall.

I've been told that they did it this way before without using sql
through the Firewall. Does anyone have any suggestions?

 

[J Burford Fields]

In general, if you are going through a firewall you do not want to be
using the MS Project Professional Client. PWA should be fine. If you
need to use Project Professional, I think the recommended practice is
to do so by connecting to a terminal server that is configured with
Project Professional and closely coupled to the MS Project Server
front-end.

You probably want to vpn to the DMZ if you're access it remotely from
the Internet.

J