Re: Access server using PP and domain account

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

Date: Tue, 17 Aug 2004 14:58:07 -0600

Larry,

The error message your getting is clearly indicating that IIS is having trouble processing your credentials through. If it were SQL server causing the problem you'd probably be getting a different error - which I have intimate experience with (network blocks on port 1433/1434 traffic- this is probably NOT your problem given your error message).

Did you check/add the DNS suffix search settings for name resolution? Regardless of the fact that you're specifying a FQDN in the URL in the project professional connection setting - M$Project somewhere along the way still tries to do WINS resolution. Call it Micro$oft hubris - M$ expecting you to be on a M$ network. I have no M$ network available to me in my building yet I'm successfully connecting to a project server on another network in another building on our campus.

I've also added an entry in the hosts file of my workstation but this is essentially redundant if you do the prior step. If you're interested the file is in C:\WINDOWS\system32\drivers\etc and the entries look like this:

# target IP shortname FQDN
999.000.999.999 server1 server1.my.domain.com

Have you had anyone watch the incoming traffic to your project server while you try making a connection? Your network guys can do this with a sniffer. Tell them the problem you're having and the machine you're trying to connect to and then ask them to set aside 5-10 minutes to watch for you. You may need to have a hole punched in the firewall for your IP address to get through. Even if you're using DHCP your IP address can be made to "stick" to your machines MAC address - in effect giving you a static address.

Also, since you're using SSL have you got your certificates all legitimate? Are you or have you ever been prompted to review/accept the site certificate?

Earl

>>> SizzleMaster<larry@datasculpting.com> 8/17/2004 2:37:30 PM >>>
Well you learn something new everyday. Thanks for replying. I didn't know
you could associate a domain\username account from outisde the domain in XP
using control panel. Unfortunately, this disn't solve the problem. I
associated my domain\user account on XP for the https://FQDN/, made sure
that it's a trusted site with automatically log in using windows account
set. When I go to PWA, I no problem logging in on XP with this account.
I'm not even prompted for UN:PW now. But, still get that authenticate error
trying from PP. I can login using PP when I'm in logged into the domain.
The other post was somewhat different highlighting the fact this is all
going through ISA. And it doesn't work using the netbios name either. Some
of the other postings duplicated in the last couple of days were accidents.
I kept trying to post one as new and it kept posting back to the old thread
and then all of a sudden several duplicates showed up as new threads. Yes I
know thse forums are voluntary and certain ettiquette should be followed.
Sorry for that and thanks again. I'm still trying.
"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
    ... PWA is easy. ... My conceptual issue is the fact that when you configure an account to ... configurable and uses the credentials that you logged onto the workstation ...
    (microsoft.public.project.pro_and_server)
  • Re: Trust relationship between this workstation and Primary Domain
    ... it, with a new computer ID, a new workgroup ID, but again to no avail. ... password policy, renamed admin account, automatic updates are controlled by ... * PLEASE post all messages and replies in the newsgroups ... "Workstation ...
    (microsoft.public.win2000.networking)
  • Re: Re-Post - "the trust relationship between this workstation and
    ... account is NEW to the workstation. ... needs admin group priv at workstation level. ... only problem is adding a new user account on the station. ... This would be on the DNS server 172.20.100.2 ...
    (microsoft.public.windows.server.active_directory)
  • Re: Re-Post - "the trust relationship between this workstation and
    ... "the trust relationship between this workstation and the primary domain ... only problem is adding a new user account on the station. ... The DNS Zone for your AD Domain must be DYNAMIC, ... Client computer must use STRICTLY the INTERNAL DNS server which can ...
    (microsoft.public.windows.server.active_directory)
  • Joining NT4 to a Windows 2000 domain; secure channel prob?
    ... Trying to logon with a domain account pops up the error: ... The trust relationship between this workstation and the primary ... Searching PDC for domain MYDOMAIN ... ...
    (microsoft.public.windows.server.active_directory)