Join domain fails???

  • Thread starter Thread starter serge calderara
  • Start date Start date
S

serge calderara

Dear all,

just as testing purpose for practice in order to plan for
an MCP exam soon.

I have one one PC where I have install W2K server and DNS
installed and I have created a domaine name as
mcse.training.

Then I try from a portable running WinXp to joind that
domain, when I try to do that I get an error that it
cant'connect or invalid dommain name.
I have a perr to peer connexion with the two system and
from XP I can ping the IP adress of W2k server but not
able to join that domain?

any idea why or wht to check?

I was mentionning in XP training kit that if server is
configured with DNS we should configure XP for beeing a
DNS client. Now does DNS configuration can include its own
ipadress: I am stuck here and i am not undestand reaaly
welll why I cannot access.

the only way I can connect to that server is by connection
to a shared folder.

thanks for wour help and explaination
serge
 
In
serge calderara said:
Dear all,

just as testing purpose for practice in order to plan for
an MCP exam soon.

I have one one PC where I have install W2K server and DNS
installed and I have created a domaine name as
mcse.training.

Then I try from a portable running WinXp to joind that
domain, when I try to do that I get an error that it
cant'connect or invalid dommain name.
I have a perr to peer connexion with the two system and
from XP I can ping the IP adress of W2k server but not
able to join that domain?

any idea why or wht to check?

I was mentionning in XP training kit that if server is
configured with DNS we should configure XP for beeing a
DNS client. Now does DNS configuration can include its own
ipadress: I am stuck here and i am not undestand reaaly
welll why I cannot access.

the only way I can connect to that server is by connection
to a shared folder.

thanks for wour help and explaination
serge
Click to expand...

The reason is it can't find the domain is because it's trying to query DNS
for the domain's location. Specifdically the DC's DNS server. The cardinal
rule behind AD is to use ONLY the internal DNS server. If you use an
external server (such as your ISP's), numerous errors will appear, such as
what you've seen. Point the DC's DNS address in IP properties to only it's
DNS server (probably itself in your case). Make sure it's not the loopback
(127.0.0.1) but rather it's actual IP. Then for the XP, and your other
clients, only point it's DNS settings to this DNS server ONLY. Remove the
ISP's or any others. Then it will find the domain.

Read this please:
http://support.microsoft.com/?id=291382

If you want efficient Internet resolution, use a Forwarder. If the
FOrwarding option is grayed out, delete the Root zone, then refresh the
console and try again. Both of these steps are outlined here:
http://support.microsoft.com/?id=300202

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top