• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 791
  • Last Modified:

vmware ip's get added to our DNS records

Hi All,
I have a strange issue.

We have vmware server 2 installed on a windows server running 2003.
After installation of vmware server 2.0 it created 2 virtual NICs:
VMware Network Adapter (vmnet1) = 192.168.35.1
VMware Network Adapter (vmnet8) = 192.168.94.1

The host has a static IP address of 192.168.1.11

my problem is in our active directory domain, there are 3 dns records for this server, the main ip address and the ip from vmnet1 and vmnet8. My problem is sometimes computers are trying to resolve the dns name of the server and its going to vmnet1 and then timing out..

I have gone into the network connection > vmware network adapter (VMnet1) and removed the check in TCPIP properties for Register this connection's addresses in DNS.However the records still show up. Users are complaining they cant get to the server. Is there a setting im missing in VMWare Server?

Thanks,
Brad
0
g-techforce
Asked:
g-techforce
1 Solution
 
Paul SolovyovskySenior IT AdvisorCommented:
On the VMNics that should not have DNS broadcast you'll need to turn off nebtbios over tcp/ip on the network adapters.  You should also check WINS and delete the entries in there as well.
0
 
DatedmanCommented:
In my experience, Windows will always try to register a NIC no matter what the heck you do.  Workaround: on any NIC (virtual or otherwise, I do this for SAN NICs) you don't want registered, put a bogus DNS server.  To create minimal noise, I put the IP of the NIC itself (and then if the machine's a DNS server make sure it's not listening on that NIC!)
0
 
g-techforceAuthor Commented:
paulsolov,
I have netbios disabled on each NIC, I have register this connection's addresses in DNS disabled, and everytime i delete the dns record on DNS server, they keep coming back.

just fyi i have 2 DNS Servers which are both windows domain controllers. I have deleted the records from both DNS servers.
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.

 
Paul SolovyovskySenior IT AdvisorCommented:
0
 
za_mkhCommented:
If you are not going to use VMNet1 and VMNet8, I recommend deleting these networks/interfaces via the VMWare Server Network Settings App ...
By disabling/deleting VMNet1 and 8, it will remove those adaptors from the Host machine which could also solve your problem.
0
 
ryder0707Commented:
I agree with za_mkh
0

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now