Unable to Contact Active Directory Domain Controller

I have a thin client server that will not reconnect to a domain. I have reset tcpip and winsock. There is no entry in my internal DNS server. I can ping the server by ip because the ip is static but I cannot join a domain.

I keep getting the message, "An Active Directory Domain Controller (AD DC) for domain "My Domain" could not be contacted ."

I am running Windows Server 8 R2. I can go to the internet and ping DNS server, DHCP server, and gateway.

From other computers I can ping the troubled server by ip but not by host name. I added a manual A record in DNS and it still doesn't work. Any suggestions experts? Thanks in advance.
waynerayAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Santosh GuptaCommented:
1.  "nslookup serverIP"
2. check if the server is pointing to correct DNS server.
3. on cmd do "ARP -A serverip" and see if MAC address and IP is mapped correctly.
4. are you able to ping any other server by name or not
 and share the results.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
waynerayAuthor Commented:
When I do the nslookup with the troubled computer ip, the host name is given I can tell it is based on the A record I put in DNS. When I run the ARP command, I get the message, "No ARP entries found".

I can ping other servers by hostname. I did get the server to see the domain by using the fully qualified domain name. When I tried to connect, it appeared successful but I got an error. I apologize I did not write the entire error down but it did join the domain. I will do some more testing tomorrow. I think it is fixed. Thanks for your help.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.