Client cannot join the domain

I am trying to join a client to the domain. Both the client and the
server can ping each other with no problem but the client tells me the
domain controller cannot be located.

Any ideas? Thanks.

Whare is the DNS server for the domain? Does the client point to it of it's
DNS? Does the DNS server for the AD domain point to itself for it's DNS?

hth
DDS

"john" <(E-Mail Removed)> wrote in message
news:4c592a72-3e49-43c6-8ce0-(E-Mail Removed)...
>I am trying to join a client to the domain. Both the client and the
> server can ping each other with no problem but the client tells me the
> domain controller cannot be located.
>
> Any ideas? Thanks.

On Feb 12, 11:33*am, "Danny Sanders" <dsandersNOS...@ciber.com> wrote:
> Whare is the DNS server for the domain? Does the client point to it of it's
> DNS? Does the DNS server for the AD domain point to itself for it's DNS?
>
> hth
> DDS
>
> "john" <johnbah...@hotmail.com> wrote in message
>
> news:4c592a72-3e49-43c6-8ce0-(E-Mail Removed)...
>
>
>
> >I am trying to join a client to the domain. Both the client and the
> > server can ping each other with no problem but the client tells me the
> > domain controller cannot be located.
>
> > Any ideas? Thanks.- Hide quoted text -
>
> - Show quoted text -

DNS server is on the DC. It is pointing to the IP if the DC. I have
also tried it with the DNS address given to me by my carrier but
didn't work.

AD must have a DNS server set up for the AD domain. Your AD DCs will
register SRV records in the AD DNS zone. Your AD clients MUST find these SRV
records in order to "find" the domain.

Point your AD DNS server to itself for DNS. Use the actual IP address not
127.0.0.1. Restart the server or restart the netlogon service. Then check
for the SRV records in DNS. See:
How to verify that SRV DNS records have been created for a domain controller
http://support.microsoft.com/default...b;en-us;816587

Setting Up the Domain Name System for Active Directory
http://support.microsoft.com/default...b;en-us;237675

Best Practices for DNS Client settings in Windows 2000 server and in Windows
Server 2003
http://support.microsoft.com/default...b;en-us;825036

How to configure DNS for Internet access in Windows Server 2003
http://support.microsoft.com/default...b;en-us;323380


hth
DDS


"john" <(E-Mail Removed)> wrote in message
news:261e89b4-814b-4dd1-ac74-(E-Mail Removed)...
On Feb 12, 11:33 am, "Danny Sanders" <dsandersNOS...@ciber.com> wrote:
> Whare is the DNS server for the domain? Does the client point to it of
> it's
> DNS? Does the DNS server for the AD domain point to itself for it's DNS?
>
> hth
> DDS
>
> "john" <johnbah...@hotmail.com> wrote in message
>
> news:4c592a72-3e49-43c6-8ce0-(E-Mail Removed)...
>
>
>
> >I am trying to join a client to the domain. Both the client and the
> > server can ping each other with no problem but the client tells me the
> > domain controller cannot be located.
>
> > Any ideas? Thanks.- Hide quoted text -
>
> - Show quoted text -

DNS server is on the DC. It is pointing to the IP if the DC. I have
also tried it with the DNS address given to me by my carrier but
didn't work.

Hello John,

Please post an unedited ipconfig /all from both machines, so we can check
that DNS is configured as needed.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> I am trying to join a client to the domain. Both the client and the
> server can ping each other with no problem but the client tells me the
> domain controller cannot be located.
>
> Any ideas? Thanks.
>

I have
> also tried it with the DNS address given to me by my carrier but
> didn't work.

Of course not. How could the DNS server at your ISP possibly know how
your local network is set up?

Active Directory uses DNS to find AD resources. All DNS clients (and
the server itself) should point to the local DNS, as Danny pointed out.

When you promoted the server to a DC, did you accept the option to set
up DNS for you? Did it give any errors when it did? When you look at your
local DNS server do you see entries for AD resources?

On Feb 12, 7:05*pm, "Bill Grant" <not.available@online> wrote:
> *I have
>
> > also tried it with the DNS address given to me by my carrier but
> > didn't work.
>
> * *Of course not. How could the DNS server at your ISP possibly know how
> your local network is set up?
>
> * * *Active Directory uses DNS to find AD resources. All DNS clients (and
> the server itself) should point to the local DNS, as Danny pointed out.
>
> * * *When you promoted the server to a DC, did you accept the option to set
> up DNS for you? Did it give any errors when it did? When you look at your
> local DNS server do you see entries for AD resources?

No I didn't. I configured it manually since it gave me an error.

On Feb 12, 7:05*pm, "Bill Grant" <not.available@online> wrote:
> *I have
>
> > also tried it with the DNS address given to me by my carrier but
> > didn't work.
>
> * *Of course not. How could the DNS server at your ISP possibly know how
> your local network is set up?
>
> * * *Active Directory uses DNS to find AD resources. All DNS clients (and
> the server itself) should point to the local DNS, as Danny pointed out.
>
> * * *When you promoted the server to a DC, did you accept the option to set
> up DNS for you? Did it give any errors when it did? When you look at your
> local DNS server do you see entries for AD resources?

It did give me an error. I found out what the problem is. I have 5
static IPs and the clients still know the server as having one of the
static IPs. I tried to change the server's IP to the old one but it
didn't connect to the internet for some reason. That old IP only works
on the clients. So I have to somehow let the clients know that the
server has a new IP which seems to be the faster way to solve this
problem.