Nslookup Fails 2008R2 on ESXi

I have one virtual 2008R2 server.  It was doing just fine.  Today DNS resolution began to fail.  All the other virtual servers, same vSwitch, vLAN, DNS servers, subnet, ESXi host, are fine.  I pull the vNIC, wipe hidden devices, reboot, add a new vNIC, don't connect it yet.  Configure the appropriate static.  Then connect it to the vSwicthc.  NSlookup works fine.  Great?  No.  Give it five minues and NSlookup begins to fail again.  Wash, rinse, repeat.

ESXi 5.0
VMware tools are installed

I appreciate the help!
whoamAsked:
Who is Participating?
 
compdigit44Connect With a Mentor Commented:
Have you install any windows updates recently?
What type of vNic are you using in the VM? Have you tried using VMXNET3 or if already using it tring E1000?
Have you viewed the host and VM's log files for errors/
0
 
whoamAuthor Commented:
Oh, and I can pin IP's all day long.
0
 
whoamAuthor Commented:
IP v6 is disabled
Provider order - Tried both RD session host and MS Network at the top.
0
Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

 
whoamAuthor Commented:
The NIC is recognized as being on a "Domain Network"
0
 
Bruno PACIConnect With a Mentor IT ConsultantCommented:
Hi,

Is it possible for you to copy paste the exact response when the nslookup fails ?
By the way, what are you requesting in your NSLOOKUP ? Which name ?

Have a good day
0
 
whoamAuthor Commented:
All, ended up being port exhaustion on the virtual switch.  System had been upgraded since 3.0 days, only 160 ports.  Bumped to 1060 ports and all is well.

Thanks!
0
 
whoamAuthor Commented:
Solutions were just beginning to be developed when I found the error/solution.
0
All Courses

From novice to tech pro — start learning today.