Error 401 logging in to Project Server from Project Pro 2003

[Jim]

Hi folks.

I recently moved a Project Server 2003 environment from a W2K Server to a
Windows 2003 server. Everything works great with one issue. This
environment is part of a domain. I can access the server through PWA with no
problem. I can log on to the server via MS Project Pro 2003 from computers
that are domain members. The problem arises when logging in to the server
from a laptop that is not a member of the domain.

I plug this laptop in to the network from behind the firewall and access PWA
just fine. When I try to log on via MSP, I get an error stating there was an
unexpected response from the server. It directs me to MS Support website and
tells me to search on http and 401. When I did that, I couldn't find
anything relating to accessing Project Server. It seems there is something
in IIS that needs to be reset, it's a small needle in a big haystack.

Any suggestions on how to resolove this?

Many thanks.

Jim

 

[Gary L. Chefetz \(MVP\)]

Jim:

Read the post, a couple threads prior to yours, by Earl Lewis - RE: "Cross
Domain Single Sign on" for some insight into your issue.

--

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

-

 

[Jim]

Gary,

I read the thread, but I'm not sure they helped other than to point out the
Windows 2003 authenticates domain accounts differently. PWA is not the
problem. I can access that just fine. The problem lies in accessing project
server through MS Project 2003

Could there be something in IIS security that is handled differently between
Win2K and Win 2003?

Thanks.

Jim

 

[Earl Lewis]

Jim,

My post about setting up security on Windoze XP was not really (or only) about connecting to PWA via IE. It also affects how the client running MS Proj Pro connects to the server.

Earl
Gary,

I read the thread, but I'm not sure they helped other than to point out the
Windows 2003 authenticates domain accounts differently. PWA is not the
problem. I can access that just fine. The problem lies in accessing project
server through MS Project 2003

Could there be something in IIS security that is handled differently between
Win2K and Win 2003?

Thanks.

Jim