Re: XP workstations will not apply GPO software install but 2000 W
From: bbuchen (bbuchen_at_discussions.microsoft.com)
Date: 01/14/05
- Next message: Rob: "Re: GPO for Windows 2000 and XP workstations"
- Previous message: Danny Sanders: "Re: Trust Relationship between NT domain and a windows 2000 native mod"
- In reply to: Herb Martin: "Re: XP workstations will not apply GPO software install but 2000 WS do"
- Next in thread: Herb Martin: "Re: XP workstations will not apply GPO software install but 2000 W"
- Reply: Herb Martin: "Re: XP workstations will not apply GPO software install but 2000 W"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 14 Jan 2005 11:19:07 -0800
Hi,
I don't think it is permissions because all my win2k ws work fine. I have
about 60 of these, I am only having a problem with my XP ws (about 10
machines).
The exact error I get is the following:
Windows cannot obtain the domain controller name for your computer network.
(The specified domain either does not exist or could not be contacted. ).
Group Policy processing aborted.
I have run netdiag with no problems. nslookup, ping any thing I could think
of.
I don't think it is specific to the workstation because all my XP machines
give me
this.
"Herb Martin" wrote:
> "bbuchen" <bbuchen@discussions.microsoft.com> wrote in message
> news:24BE27F6-DD98-4C2D-B1CB-9F81CB88424A@microsoft.com...
> > Hello,
> >
> > I have setup an OU with a GPO that will install Outlook 2003 by Computer.
> > This works great for win 2000 workstations but for any XP ws
> (Professional)
>
> > I get the error upon boot up that it could not contact the DC therefore
> the
> > GPO install will abort. Any ideas? I suspected a problem with DNS
> > but I have check it and seems fine. I am able to log into the WS with a
> AD
> > user and
>
> Such (failure to authenticate and thus load GPOs etc.) is almost
> always a DNS issue but it can be a more direct authentication or
> permission problem.
>
> > I am able to ping, nslookup all systems on the network including the DC
> > without any problems.
>
> This does argue for eliminating DNS as the culprit,
> but let's first say that INTERNAL clients must use
> ONLY the internal DNS servers in their NIC->IP->
> DNS server properties.
>
> How about permissions? Are the install files (the MSI etc.)
> located on a server with Share or NTFS permissions that
> do not allow the XP machines (accounts) to download the
> files?
>
> If you used something like "Authenticated Users-READ" this
> should not be the problem.
>
> Does it really say it "cannot contact the DC" or does it use
> the Server name (for the DC) in the context of trying to
> download the FILES?
>
> There is a difference (the DC doesn't actually have to hold
> the files distributed through the GPO instructions, but the
> key here is to isolate WHAT is failing.)
>
> It sounds like permissions but that seems unlikely to be
> messed up.
>
> --
> Herb Martin
>
>
> >
>
>
>
- Next message: Rob: "Re: GPO for Windows 2000 and XP workstations"
- Previous message: Danny Sanders: "Re: Trust Relationship between NT domain and a windows 2000 native mod"
- In reply to: Herb Martin: "Re: XP workstations will not apply GPO software install but 2000 WS do"
- Next in thread: Herb Martin: "Re: XP workstations will not apply GPO software install but 2000 W"
- Reply: Herb Martin: "Re: XP workstations will not apply GPO software install but 2000 W"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
