Problem to join

Hi,
Within client machine, I am able to ping the domain's IP like

C:\Users\peter>ping 192.255.10.21

Pinging 192.255.10.21 with 32 bytes of data:
Reply from 192.255.10.21: bytes=32 time=4ms TTL=126
Reply from 192.255.10.21: bytes=32 time=1ms TTL=126
Reply from 192.255.10.21: bytes=32 time<1ms TTL=126
Reply from 192.255.10.21: bytes=32 time=1ms TTL=126

Ping statistics for 192.255.10.21:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 4ms, Average = 1ms

Open in new window

   
and I also have put this
https://dl.dropboxusercontent.com/u/40211031/t995.png

to IPv4 of the client, but when joining to the domain, I get this
https://dl.dropboxusercontent.com/u/40211031/t996.png

why?
LVL 11
HuaMin ChenProblem resolverAsked:
Who is Participating?
 
Will SzymkowskiSenior Solution ArchitectCommented:
The second error message is related to DNS which is why you cannot add the machine to the domain. Can you ping domain.com and get a reply back? Have you changed the DNS suffixes in Network Adapter Settings or on the machine itself?

Will.
0
 
dlb6597Commented:
what results do you get if you ping the domain name?
0
 
HuaMin ChenProblem resolverAuthor Commented:
Here is what I get
C:\Users\peter>ping tst220750a.com
Ping request could not find host tst220750a.com. Please check the name and try again.

C:\Users\peter>ping 192.255.10.21

Pinging 192.255.10.21 with 32 bytes of data:
Reply from 192.255.10.21: bytes=32 time=1ms TTL=126
Reply from 192.255.10.21: bytes=32 time=2ms TTL=126
Reply from 192.255.10.21: bytes=32 time=1ms TTL=126
Reply from 192.255.10.21: bytes=32 time=1ms TTL=126

Ping statistics for 192.255.10.21:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 2ms, Average = 1ms

Open in new window

0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
dlb6597Commented:
your domain name isn't registered correctly in DNS or that is not the correct domain name or DNS is not functioning correctly...

can you ping the hostname of your domain controller?
what does the command "nslookup -type=srv _ldap._tcp.tst220750a.com" return?
what does the command "nslookup yourdchost_name" return
0
 
Craig BeckCommented:
Is 192.255.10.21 a domain controller on the tst220750a.com domain?  If so, is it running the DNS service?
0
 
HuaMin ChenProblem resolverAuthor Commented:
Thanks all.
Here is what I get

C:\Users\peter>nslookup -type=srv _ldap._tcp.tst220750a.com
DNS request timed out.
    timeout was 2 seconds.
Server:  UnKnown
Address:  192.255.10.21

DNS request timed out.
    timeout was 2 seconds.
_ldap._tcp.tst220750a.com       SRV service location:
          priority       = 0
          weight         = 100
          port           = 389
          svr hostname   = cshhkb02.tst220750a.com
cshhkb02.tst220750a.com internet address = 192.255.10.21
cshhkb02.tst220750a.com AAAA IPv6 address = 2002:c0ff:a15::c0ff:a15

Open in new window

How can I know which is DC host name?
0
 
Seth SimmonsSr. Systems AdministratorCommented:
I've requested that this question be deleted for the following reason:

The question has either no comments or not enough useful information to be called an "answer".
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
This users issue is clearly related to DNS. I have stated that in my first post that DNS needs to be corrected before the machine can be added to the domain.

Will.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.