Re: Joining a computer to a domain

Tech-Archive recommends: Fix windows errors by optimizing your registry

> I am having a similar problem. Qestion? What exactly do you do to
> troubleshoot the problem. My XP clients do not ping the 2003 server AD
> domain DC. The server do infact ping the XP clients. So, I can not join
> these XP clients to the Domain.

You need to ensure that the clients are only pointing to the internal DNS
server and that the zone is configured to accept dynamic updates (and the
clients haven't been stopped from registering in DNS). This will sort
itself out then, providing there's no network problems. If you need to
resolve public addresses use a forwarder from DNS or let the proxy server do
it.

--
Paul Williams
Microsoft MVP - Windows Server - Directory Services
http://www.msresource.net | http://forums.msresource.net


.

Relevant Pages

  • Re: Permissions across 2 Forrest
    ... Primary DNS server on 1.x and the 18.x network along with DHCP and WINS. ... For instance ForrestA DNS is now a secondary for Forrest B and vise versa. ... WINS clients must use the same "WINS Database"* ...
    (microsoft.public.windows.server.active_directory)
  • Re: Still strange not fully working DNS server
    ... On none of the computers (both DC and clients) no firewall software is ... For the rest nothing happens in the DNS forward lookup zone. ... Is the new server Global catalog? ... The config you mentioned was not configured so I have configured ...
    (microsoft.public.windows.server.dns)
  • Re: Client installation frustration.
    ... not, apparently, any DNS lookup issues on my network. ... connection's addresses in DNS" and "Use this connection's DNS suffix in DNS ... is a file and print server that we have at one of our secondary sites. ... Is there any way to cancel all current requests to install clients? ...
    (microsoft.public.sms.admin)
  • Re: problem with xp clients and windows 2003
    ... We now have the cross cable running from the room's switch ... >> policy but logs into the server. ... >> aware that this is a DNS issue but I have TRIPLE checked the DNS ... >> If I do NSlookup from the problematic clients, ...
    (microsoft.public.windows.server.networking)
  • Re: Critical! system down - Local interface stopped listening on all ports
    ... He could ping yahoo.com by name. ... both client and server. ... Internet connection ... >>> Server and all clients have internet access through NAT router. ...
    (microsoft.public.windows.server.sbs)