Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

servers VM in the VMworkworkstation are not talking to each other. Cant join to the domain

Posted on 2014-12-13
3
Medium Priority
?
359 Views
Last Modified: 2014-12-13
Hello, I have servers VMs in the VMmware workworkstation v11 that are not talking to each other. They are suppose to be on the same network and should be able to ping each other, join to the domain, etc.

Is it a virtual network adapter? It is currently set to NAT....Should I recreate a new virtual adapter and put all of them on that adapter?

I already tried promoting one member to DC, installing DNS and configuring same DNS for member server and that DC, but it still tells me that it can't find Domain Controller and cant join to the domain. I assigned static IPs to both of them as shown below:

1st server DC, DNS
10.10.10.2
255.255.255.0
10.10.10.1

2nd server member that not able to see DC and join to the domain
10.10.10.3
255.255.255.0
10.10.10.1


Please advise
Thank you
0
Comment
Question by:claudiamcse
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 123

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 2000 total points
ID: 40498104
Have you tried

Bridged Networking or Host Only networking.

I've seen a few issues of late with VMware Workstation 11, and weird network communication.

(I've just been writing a new EE Article using VMware Workstation 11, and I've had network issues, and I've needed to do this!)

Try Power Off, the virtual machines, and Shutdown VMware Workstation.
0
 

Author Comment

by:claudiamcse
ID: 40498214
Will try host. Is it possible that Bridged network connection (Connected directly to physical network) could cause problems? We have lab that is using different forest and domain name, but still....since the laptop is join to the production network, I dont want any new DNS or DHCP servers to be visible to the production environment or causing any issues. Let me know if that would be a risk.
0
 
LVL 123
ID: 40498220
You will want to use BRIDGED Networking for Domain Joins!
0

Featured Post

Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Auditing domain password hashes is a commonly overlooked but critical requirement to ensuring secure passwords practices are followed. Methods exist to extract hashes directly for a live domain however this article describes a process to extract u…
How to deal with a specific error when using the Enable-RemoteMailbox cmdlet to create a mailbox in the cloud-based service, for an existing user in an on-premises Active Directory.
This Micro Tutorial walks you through using a remote console to access a server and install ESXi 5.1. This example is showing remote access and installation using a Dell server. The hypervisor is the very first component of your virtual infrastructu…
This video shows you how easy it is to boot from ISO images for virtual machines with the ISO images stored on a local datastore on the ESXi host.

722 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question