Project Pro continues to Prompt for credentials after setup?

J

John Benak

Gave a demo of a Project 2002 Pro/Server Proof of concept
setup yesterday, and everything went pretty much OK,
except that after I created & published the demo project
to the server, and some of my audience (with Project
2K2Pro on their desktops) tried to do some similar tasks,
they kept getting prompted for their NT Credentials
before they would be allowed to start Project Pro &
connect to the server. This would happen via PWA as
well.

I showed them all how to set up the server prefs
(collaboration options -> servername), as well as how to
set up Project Server Accounts (Tools->Enteprise Options-
Project Server Accounts), and all of the users had
already been set up as Enterprise Resources. After they
did that, they were still prompted. What gives?

This shouldn't happen, as I myself have NEVER had this
occur (including today), and have been working with the
server for months. The only difference between me and
these users is that I am an administrator on the server.
However, it seems that pass through authentication is
being held up somewhere, or there is a hiccup happening.
Anyone have any ideas? I checked the NTFS perms on the
virtual drive, and they were set to 'everyone' 'full-
control'

All suggestions are appreciated.
Thanks,
John
HP Services
 
J

Jonathan

By default Project Server Web Access is setup to use NTLM. So if your
user is not on the same domain as the server that host Project Server,
you will get this prompt.
 
G

Gary Chefetz [MVP]

John:

If you weren't running under a domain umbrella, you would experience
behavior like this.

--
Gary Chefetz [MVP]
http://www.msprojectexperts.com
"We wrote the book on Project Server"

*** Remember to look for line breaks in links posted to the news group, use
cut and paste for these.
 
G

Gary Chefetz [MVP]

John:

Project Pro makes direct connections to the database while Project Web
Access does not. So, if this is a network issue, then it may be security
around access to data across domains. Make sure that at a custom level, the
trusted sites zone on the work stations is set to allow access to data
across domains and that other domain security policies don't prohibit it.
Make certain at the network level that port 1433 isn't blocked for security.

--
Gary Chefetz [MVP]
http://www.msprojectexperts.com
"We wrote the book on Project Server"

*** Remember to look for line breaks in links posted to the news group, use
cut and paste for these.
 
Top