MS Project Ports

[KC]

We have setup MS Project to all users outside of the firewall to view the
project plan. For whatever reason, the client machine is requiring access
to the database that hosts the ProjectServer database. We know this because
the database connection value was using a NetBios server name and when
exposing the plan publically the users were off of the VPN client and teh
NetBios name did not work anymore. Thus, the users were prompted for a
database name - actually it popped up a ODBC connection window. This
obviosuly seems very odd. Having a client be aware of any type database is
problematic.
Have we encountered something common?
Does this mean we need to open up port 433 on our firewall? If so, could
someone point me to the direction of installion recommendations.

Kevin

 

[Gary L. Chefetz [MVP]]

Boy is that a bold and dangerous move! The Project client authenticates
through Project Server to make a connection directly to the database. Do
not, under any circumstances, open your SQL ports to the Internet. Instead,
use Terminal Services or Citrix for this scenario or at least VPN.

 

[Gary L. Chefetz [MVP]]

The client needs access to SQL server, if that wasn't clear in the previous
post.

 

[KC]

Thanks Gary. So in other words, you cannot expose an editable project plan
to users outside you firewall without poking a hole through the firewall for
sql server. If so, that is phooey. Let me see, web services have been
around how long now

Is there any doco explaining this and how to expose your plan to remote
users if VPN is not an option?

KC

 

[Gary L. Chefetz [MVP]]

KC:

In my first reply, I told you the best way.

 

[Brian K - Project MVP]

Thanks Gary. So in other words, you cannot expose an editable project
plan to users outside you firewall without poking a hole through the
firewall for sql server. If so, that is phooey. Let me see, web services
have been around how long now

Baby steps. You cant fix everything. Remember this is only version 2 of
Project Server.

 

[KC]

Hehe, I guess that is a MS-ish way to look at it

 

[Brian K - Project MVP]

Hehe, I guess that is a MS-ish way to look at it

Not at all. It is a realistic view of software development way to look at
it. you have a list of fixes you want to make and a list of features you
want to add. You examine each of them and look at how much work each one
will take to implement. you then have a schedule that, given your
resources, is something like 5 or 6 times more than the time you have till
you have to ship. So you prioritize them and do the ones that are the most
critical. I happen to know that work that would have gone into allowing
the win32 client to work via a web service would have been a HUGE
undertaking. You cant fix everything. That is not MS. That is EVERYONE. Im
curious as to why you feel that this universal truism is an MS way of
looking at it.

 

[Raymond Chiu (gatorback]

KC,

XP remote desktop is a limited poor-man's terminal server, however, it is
very easy and quick to setup. I have an XP virtual machine, which can be
instantly provided for users on port 3389. There is also a hack to use other
ports for multiple XP machines.

I hope this helps.

Ray