2012 R2 DC not reachable

Hi,

my business and I service about 300 customers in the small business range, mostly with pure Microsoft environments.

Our so far only two customers who run no servers other than Windows Server 2012 R2 experience this problem:

Every now and then, every other day or less frequent, logon into RDS is not possible because no domain controller is available.  DNS service does not work even though the service is running.  The AD member servers log frequent events relating to no DC available.  The DC logs no events, feels just fine, cannot resolve any DNS queries and sits there in ignorant bliss.
Restart of the service does not help, I have to reboot the entire machine .

Both customers run VMware, one has Exchange, the other does not.   Both customers have only one single DC. One domain, one tree.  
Eventlog does not record anything of any help.  

Many other customers run Server 2012 R2 for some services and 2008 R2 for others.  They don't report anything like this.

Does anybody have a clue what might be happening there?  Has anyone experienced something like that?

Thanks,
Ralph
LVL 2
Ralph ScharpingDigital TherapistAsked:
Who is Participating?
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.

Miguel Angel Perez MuñozCommented:
Both customers run VMware, one has Exchange, the other does not.

Ensure vmware don´t do oversubscription/overcommit memory, focus especially on Exchange setup. I suggest you set fixed memory value.
0
Ralph ScharpingDigital TherapistAuthor Commented:
Thas is the case.  Memory is not oversubcribed.
0
Miguel Angel Perez MuñozCommented:
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Ralph ScharpingDigital TherapistAuthor Commented:
DNS is already configured as described.
0
Miguel Angel Perez MuñozCommented:
And OS is updated?
0
Ralph ScharpingDigital TherapistAuthor Commented:
Yes, no patches available.
0
Miguel Angel Perez MuñozCommented:
Another thing, your DNS is configured to use any kind of router as forwarder?
0
Ralph ScharpingDigital TherapistAuthor Commented:
No, I am forwarding to google.  But resolving even internally does not work when the issue occurs.
0
Miguel Angel Perez MuñozCommented:
You can try disabling EDNS0, on command prompt run dnscmd /config /EnableEDNSProbes 0
Not requires restarts.
0
Ralph ScharpingDigital TherapistAuthor Commented:
The command went through without an error message.  But I'll have to wait a few days to check if this changed anything.

Somehow I don't think it is an isolated DNS issue...
0
kevinhsiehCommented:
Which type of NIC are the VMs using? They should be using Vmxnet3.
0
Ralph ScharpingDigital TherapistAuthor Commented:
They are not.  Default is E1000 on VMware 5.5 and that's what they are.
0
kevinhsiehCommented:
Yeah, I think that is your problem. Change to VMXNET3 and things should be a bit better. E1000 is not recommended. If you have VMware support you can also call them, but I have been told that E1000 is not recommended if VMXNET3 is available. I had to switch my VMs too as the default was E1000.
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
Ralph ScharpingDigital TherapistAuthor Commented:
Thank you for this hint.  I will change that and retry.  But I will need to wait a week to verify if this is really better.
0
Ralph ScharpingDigital TherapistAuthor Commented:
I'm thinking we might be on the right track here.  Just exchanged the LAN adapters on all VMs.  First thing I notice is MUCH faster logon times...
0
kevinhsiehCommented:
:-)
0
Ralph ScharpingDigital TherapistAuthor Commented:
So far so good.  No crashes yet since I made the change.
0
Ralph ScharpingDigital TherapistAuthor Commented:
Perfect!
I just wonder why the creation of a new VM defaults to E1000.
No trouble since I changed it....
Thanks a million!
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 Server 2012

From novice to tech pro — start learning today.

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.