Re: Access server using PP and domain account

From: Earl Lewis (Earldotlewisatutahdotedu)
Date: 08/25/04 

Date: Wed, 25 Aug 2004 15:25:08 -0600

Enomagic,

I suffered from the same (false) assumption about the workstation credentials. With Windows XP using the windows authentication isn't strictly the credentials you use to login to the workstation. Read on...

Let's try a checklist approach. And remember, this is what's working for me - your mileage may vary.

This configuration assumes Windows XP Professional on workstation - which is my case

>>These are server configuration steps<<
- user account is setup on domain (in Active Directory) in which project server resides
- user account is created and setup on project server
- user account on project server is set to use windows authentication
- user ID in project server is entered in [domain]\username format

>>These are workstation configuration steps<<
- project server URL is added to list of trusted sites in IE
- project server FQDN is added to list of network account passwords to store
  (this is found in control panel>>user accounts>>[select desired account]>>manage network passwords
- make sure account information entered for this entry is the same as the AD credentials
- you may need to add a DNS search suffix to your IP configuration to resolve the hostname to the FQDN

Have you had a network guy on the far side watch for your incoming traffic to see if it's making it into the target domain? They can do this with a sniffer program. Try to coordinate it with your tech support people if there is such a thing.

Hope that helps some.

Earl

>>> Enomagic<enomagic@hotmail.com> 8/24/2004 5:48:25 PM >>>
Earl,
I read that reply and having problems seeing the magic that gets this
scenario to work.
PWA is easy. No probs there.

My conceptual issue is the fact that when you configure an account to
connect to ProjServer with, you only have the choice of proj auth (not the
question here) and select "Use Windows user account" which is not
configurable and uses the credentials that you logged onto the workstation
with - how do you get by this? What part of your setup gets around this?

Thanks
Enomagic

"Earl Lewis" <Earldotlewisatutahdotedu> wrote in message
news:ODwWqEfiEHA.592@TK2MSFTNGP11.phx.gbl...
> Enomagic (interesting moniker),
>
> To clarify, I am using windows authentication for project professional
against a project server that resides in a domain that my workstation does
not belong to and I do not login to for any other purpose. In other words I
use a local workstation login on startup and am able to successfully connect
to and run project pro and project web access from my workstation.
>
> See my post dated 8/17/2004 11:19:29 AM in reply to "SizzleMaster's
WWW-Authenticate header error" post.
>
> Earl
>
> >>> Enomagic<enomagic@hotmail.com> 8/22/2004 10:56:26 PM >>>
> Earl,
> the originater of this posting responded to me on .project.server group
> saying I was wrong and that you said you were able to do what he
originally
> asked i.e. connect to Project Professional (PP) with a domain account when
> the client is not in the same domain as the server.
>
> I would be really interested in knowing how you have got around the hard
> coding of the Project Professional client that gives you 2 options to log
> onto the Project Server - 1) using the "Use Windows user account" option
> which only lets you use the account which you logged into the client
machine
> with, or 2) use a project server account (which isn't a domain account).
>
> His comment was that I was wrong and the Earl said you could do it. Is
this
> true, if so, this is of great benefit to us so could you please advise on
> how you managed to achieve this.
>
> Thanks in advance.
> Enomagic
>
> "Earl Lewis" <Earldotlewisatutahdotedu> wrote in message
> news:O4twfFJhEHA.3928@TK2MSFTNGP11.phx.gbl...
> > I connect to a project server in a domain that my workstation is not a
> part of using all of the settings I mentioned in my reply to your earlier
> post. Please check that and see if it helps.
> >
> > Also, posting the same problem 4 or 5 times in the same day doesn't get
> any more attention than 1 well-written post. In fact some NG readers tend
to
> ignore posts like that. I know this is frustrating and you want an answer
> but sometimes it just takes time. Remember, this is voluntary for everyone
> here.
> >
> > Earl
> >
> > >>> SizzleMaster<larry@datasculpting.com> 8/17/2004 11:43:08 AM >>>
> > Can this be done? Or do you need to use a project server account? If
the
> > latter, how do you reconcile these accounts so that one set of data is
> > associated with both. I can't merge them in PS. I seem to need the
> domain
> > accounts in order to log into PWA and the SharePoint sites. If I turn
off
> > Windows Auth and just use basic with SSL, I can't log into PWA.
> >
> > This is driving me nuts. Any help would be GREATLY appreicated.
> >
> >
> >
> >
>
>
>
>

Relevant Pages

  • Re: Access server using PP and domain account
    ... the credentials you use to login to the workstation. ... > - user account on project server is set to use windows authentication ...
    (microsoft.public.project.pro_and_server)
  • Re: Event ID 5719 not on DC but on Offline Client !!
    ... These error messages indicate the Windows workstation or server computer ... Reset the machine account by using the Active Directory. ... Are the machines only using their local DNS server? ...
    (microsoft.public.windows.server.active_directory)
  • Re: How to Login to XP with an UNIX account??
    ... > existed in the workstation first. ... When a user logs onto a Windows XP machine an Access Token is built locally ... an Access Token you cannot perform your initial logon to a Windows XP PC ... using only a UNIX system with no local account information on the PC. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Local policy does not permit you to logon interactively
    ... I had a Windows 2000 Workstation ... > couldn't get in with ANY user account. ... I REALLY don't want to reload this system and I need to ...
    (microsoft.public.win2000.networking)
  • RE: Problem Installing SBS 2000 Client FAX
    ... What are the exact problem symptoms on the problematic workstation ... The installation in Win2K run without any problems, ... > the same user account to install the Shared Fax on another new Windows 2000 ... > windows 2000 Pro workstations or the specific Windows 2000 Pro workstation. ...
    (microsoft.public.windows.server.sbs)