Re: Domain Issues (Windows 2003)

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Miha Pihler (mihap-news_at_atlantis.si)
Date: 12/08/04 

Date: Wed, 8 Dec 2004 16:23:02 +0100

Hi Damon,

First thing to check is DNS configuration on the client and domain
controllers (DCs).

Clients use DNS to locate domain controllers and other services in domain.
When you installed active directory (AD) you had to specify DNS name to use
and which DNS server will be used for this. Usually DNS is installed on same
server as AD service. If this is the case then configure you clients to
point to this DNS server for preferred DNS (configured under TCP/IP
properties) or if you use DHCP reconfigure Scope options. Clients should not
point to e.g. your ISP for DNS since your ISP doesn't know anything about
your internal domain.

Also your DC should also point to AD DNS. On Windows 2003 AD server that is
also DNS server you can simply enter 127.0.0.1 as preferred DNS entry (under
TCP/IP properties). If you make this change on server, restart the netlogon
service.

When joining computer to domain you can also use FQDN (fully qualified
domain name) instead of just using NetBIOS name (e.g. use domain.com instead
of domain).

I hope this helps,

Mike

"Damon" <nospam@me.com> wrote in message
news:uBpxarM3EHA.1124@tk2msftngp13.phx.gbl...
>I have setup a local domain. I have already succesfully joined several
> servers to this domain and can logon to them with a domain account.
> However
> today I tried to add a few more servers to this domain.
>
> Some worked fine and I was able to login with domain accounts, however
> some
> could not join the domain saying a valid domain controller could not be
> found (it could ping the DC by name and IP).
> Others were able to join, yet I am unable to login to the domain using a
> domain account (was able to once though)
> Any ideas - all servers are Windows 2003
>
>

Relevant Pages

  • RE: VPN Clients Not Registering in AD DNS
    ... via VPN, the DNS records of the VPN clients are unable to be registered. ... Windows 2003 server? ... please let me know whether the clients get the IP ...
    (microsoft.public.windows.server.sbs)
  • Re: Multi-homed WINS Server does not let me administer it.
    ... Being a VPN Server and even simply running RRAS makes it multi-homed. ... Domain Controllers with the PDF Role are automatically Domain Master Browser. ... Multihomed DCs, DNS, RRAS servers. ... Insure that all the NICS only point to your internal DNS serveronly and none others, ...
    (microsoft.public.windows.server.dns)
  • Re: DNS on Windows Server 2003
    ... You should never multihome domain controllers. ... Then configure the clients toi use the domain internal DNS server only on ther e NIC's and add the ISP's DNS server to the FORWARDERS tab under the DNS server properties in the DNS management console. ... Insure that all the NICS only point to your internal DNS serveronly and none others, such as your ISP's DNS servers' IP addresses. ...
    (microsoft.public.windows.server.dns)
  • Re: Is it safe to use a DHCP to assign the IP addresses to the servers
    ... Being a VPN Server and even simply running RRAS makes it multi-homed. ... Domain Controllers with the PDF Role are automatically Domain Master Browser. ... Multihomed DCs, DNS, RRAS servers. ... there are some registry changes to eliminate the registration of the external NIC. ...
    (microsoft.public.windows.server.networking)
  • Re: Strange Logon Behaviour.
    ... Being a VPN Server and even simply running RRAS makes it multi-homed. ... Domain Controllers with the PDF Role are automatically Domain Master Browser. ... Multihomed DCs, DNS, RRAS servers. ... there are some registry changes to eliminate the registration of the external NIC. ...
    (microsoft.public.windows.server.active_directory)