Cannot find Domain Controller

  • Thread starter Thread starter ats@jbex
  • Start date Start date
A

ats@jbex

I have a small test domain consisting of a router that acts as DHCP server,
a Windows 2003 server and an XP machine. Both machines are fully up to
date with all patches and Service Packs. The XP machine gets it's IP
address from teh router and the server has a static IP address. Thes erver
runs email & internet servers both of which are accessible from the XP
machine. However, whenever I log in to the XP machine I cannot access
anything on the server. The Event Log shows error ID 1054 saying that
Windows cannot obtain the domain controller name for your network. Also
error ID 15: Automatic certificate enrollment for local system failed to
contact the active directory (0x8007054b). The specified domain either
does not exist or could not be contacted. Enrollment will not be performed.
Any help with this would be greatly appreciated.

TIA

--
ats@jbex

When an old lady got hit by a truck
I saw the wicked gleam in your eyes

Adam and The Ants - Whip In My Valise
 
AD client rely on DNS being properly set up in order to "find" the domain.

You did not mention DNS in your post so how is DNS setup?
What DNS server does the XP client have listed as the preferred DNS server
in the properties of TCP/IP?

hth
DDS

"ats@jbex" <allen@allenjones.NOSPAM.co.PLEASE.uk> wrote in message
news:2omazk0fsrbs.1hv3cq86rk64o$.dlg@40tude.net...
>I have a small test domain consisting of a router that acts as DHCP server,
> a Windows 2003 server and an XP machine. Both machines are fully up to
> date with all patches and Service Packs. The XP machine gets it's IP
> address from teh router and the server has a static IP address. Thes erver
> runs email & internet servers both of which are accessible from the XP
> machine. However, whenever I log in to the XP machine I cannot access
> anything on the server. The Event Log shows error ID 1054 saying that
> Windows cannot obtain the domain controller name for your network. Also
> error ID 15: Automatic certificate enrollment for local system failed to
> contact the active directory (0x8007054b). The specified domain either
> does not exist or could not be contacted. Enrollment will not be
> performed.
> Any help with this would be greatly appreciated.
>
> TIA
>
> --
> ats@jbex
>
> When an old lady got hit by a truck
> I saw the wicked gleam in your eyes
>
> Adam and The Ants - Whip In My Valise
 
On Mon, 27 Aug 2007 08:43:42 -0600, Danny Sanders wrote:

> AD client rely on DNS being properly set up in order to "find" the domain.
>
> You did not mention DNS in your post so how is DNS setup?
> What DNS server does the XP client have listed as the preferred DNS server
> in the properties of TCP/IP?
>
> hth
> DDS

The DNS is assigned by the DHCP router which is set to use two external
ones. However, I have set one of them topoint to my Domian Controller which
also runs DNS, with no change in the situation.
--
ats@jbex

Every year is the same
And I feel it again,
I'm a loser - no chance to win

The Who - I'm One
 
Basic AD DNS setup is install DNS on the DC. Point the DC to itself for DNS
in the properties of TCP/IP. Use the actual IP address NOT 127.0.0.1.

Point all AD clients to the DNS server setup for the AD domain ONLY.

For Internet access either setup forwarders and list your ISP's DNS servers
as the forwarder (this is the only place on an AD domain where your ISP's
DNS server should be listed) or use root hints.

See:

Setting Up the Domain Name System for Active Directory

http://support.microsoft.com/default.aspx?scid=kb;en-us;237675





Best Practices for DNS Client settings in Windows 2000 server and in Windows
Server 2003

http://support.microsoft.com/default.aspx?scid=kb;en-us;825036



How to configure DNS for Internet access in Windows Server 2003

http://support.microsoft.com/default.aspx?scid=kb;en-us;323380



hth

DDS


"ats@jbex" <allen@allenjones.NOSPAM.co.PLEASE.uk> wrote in message
news:1kb4dzp5sqw9z.1p0jfjbwyma73.dlg@40tude.net...
> On Mon, 27 Aug 2007 08:43:42 -0600, Danny Sanders wrote:
>
>> AD client rely on DNS being properly set up in order to "find" the
>> domain.
>>
>> You did not mention DNS in your post so how is DNS setup?
>> What DNS server does the XP client have listed as the preferred DNS
>> server
>> in the properties of TCP/IP?
>>
>> hth
>> DDS
>
> The DNS is assigned by the DHCP router which is set to use two external
> ones. However, I have set one of them topoint to my Domian Controller
> which
> also runs DNS, with no change in the situation.
> --
> ats@jbex
>
> Every year is the same
> And I feel it again,
> I'm a loser - no chance to win
>
> The Who - I'm One
 
Back
Top