A
anovak
We were about to rollout Project Server 2003 using Windows
Authentication when a user began having connection problems from a
particular workstation. We know its a workstation problem rather than
a userid problem because this user can connect OK via my machine and I
can't connect using their machine.
What happens is they logon to Project Pro 2003 using "domain\Project
Server Account" and supply a password. They appear to connect, are
able to bring up a list of projects from the database, and open one of
them. Just as soon as they close the project, another dialog box pops
up requiring a login. Its as if the original authentication never
really "took".
We did a trace on that machine as well as my machine (which works) and
have found the following which is very puzzling:
The "not Working" trace shows the following:
The Client #1 IP is first trying to access the server using NTLM
authentication to authenticate with "domain#1\Project Server Account"
This fails. Then this same client tries to
access the server again utilizing a different NTLM account
"domain#2\Project Server Account" and this works fine.
*** Domain #1 is the native domain of their machine on the network.
However, I have seen with my own eyes their specification of the domain
project server resides on ("domain#2\project server account") when they
logon. It makes no sense that the workstation would be using a
different domain to connect when the user supplied the right domain to
begin with when they logon.
The "Working" trace shows the following:
The Client IP #2 is trying to access the (same) server using NTLM
authentication to authenticate with the domain #2\Project Server
Account. This works fine.
We went through the same "script" on both machines. Please help!!!
Thanks,
Andy Novak
University of North Texas
Authentication when a user began having connection problems from a
particular workstation. We know its a workstation problem rather than
a userid problem because this user can connect OK via my machine and I
can't connect using their machine.
What happens is they logon to Project Pro 2003 using "domain\Project
Server Account" and supply a password. They appear to connect, are
able to bring up a list of projects from the database, and open one of
them. Just as soon as they close the project, another dialog box pops
up requiring a login. Its as if the original authentication never
really "took".
We did a trace on that machine as well as my machine (which works) and
have found the following which is very puzzling:
The "not Working" trace shows the following:
The Client #1 IP is first trying to access the server using NTLM
authentication to authenticate with "domain#1\Project Server Account"
This fails. Then this same client tries to
access the server again utilizing a different NTLM account
"domain#2\Project Server Account" and this works fine.
*** Domain #1 is the native domain of their machine on the network.
However, I have seen with my own eyes their specification of the domain
project server resides on ("domain#2\project server account") when they
logon. It makes no sense that the workstation would be using a
different domain to connect when the user supplied the right domain to
begin with when they logon.
The "Working" trace shows the following:
The Client IP #2 is trying to access the (same) server using NTLM
authentication to authenticate with the domain #2\Project Server
Account. This works fine.
We went through the same "script" on both machines. Please help!!!
Thanks,
Andy Novak
University of North Texas