VMware Communities
MikeD-DK
Contributor
Contributor
Jump to solution

VM Ware Workstation, Windows 2003 (W2K3) std. server, domain controller (DC), network problem

Hello. Running VMWare workstation 5.5.5. and having several problems.

Virtual Network Settings: VMnet8 NAT Subnet 192.168.106.0 DHCP enabled

Gateway IP: 192.168.106.2

Netmask:255.255.255.0

I have a VM, which is std. server W2K3 and the VM hostname is "Alpha". Before I install a Domain Controller (DC) and DNS server on Alpha I make a copy of the VM. The copy hostname is changed to "Beta". (will this give me any problems further on?)

I now install Domain Controller and DNS on Alpha. Domain name "Zebra". I want to make Beta run as an additional Domain controller, and thereby adding it to the already existing domain "Zebra". This is not possible, because I cannot connect to Alpha. And I cannot figure out why? Any ideas?

Alpha:

IP Address. . . . . . . . . . . . : 192.168.106.4

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.106.2

DNS Servers . . . . . . . . . . . : 192.168.106.4

I can ping 127.0.0.1 and 192.168.106.2 and 192.168.106.4, but NOT 192.168.106.5 (Beta)

Beta:

IP Address. . . . . . . . . . . . : 192.168.106.5

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.106.2

DNS Servers . . . . . . . . . . . : 192.168.106.4

I can ping 127.0.0.1 and 192 168 106 5, but NOT 192.168.106.2 and 192.168.106.4. I cannot figure out why? Any ideas?

No firewall is running on any of the VMs (Alpha, Beta)

Hope somebody can help me with my problem.

Thanx in advance.

If I have not described the problems detalied enough, please don't hesitate to ask for further information.

Reply
0 Kudos
1 Solution

Accepted Solutions
rriva
Expert
Expert
Jump to solution

otherwise you can add a second nic, startup the machine, look if you have a different MAC and then remove the first one.

If you can solve you can use SMAC 2.0 MAC Address Changer

http://www.klcconsulting.net/smac/

Bye

R

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanx!

RRiva | http://about.me/riccardoriva | http://www.riccardoriva.com

View solution in original post

Reply
0 Kudos
16 Replies
rriva
Expert
Expert
Jump to solution

Which networking are you using on beta ? NAT again ?

Is a production enviroment or a test ?

Consider to use Host only network on both machine to let it talk each other or Bridged to let them talk with the rest of the network.

Bye

R

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanx!

RRiva | http://about.me/riccardoriva | http://www.riccardoriva.com
Reply
0 Kudos
MikeD-DK
Contributor
Contributor
Jump to solution

Hello. Thank you for a quick reply.

Yes, Beta is also running NAT.

It is a demand that I use NAT.

Thanks.

Reply
0 Kudos
rriva
Expert
Expert
Jump to solution

very strange ...

you could try this :

1) disable nic in beta and then enable it again

2) try to use a static ip address on both machine and look if can talk each other

3) release and renew ip address on both alpha and beta

4) look to both wmx file of alpha and beta and verify that "ethernet0.generatedAddress" is different.

5) Check again "Windows Firewall" on both machine

6) look at your ARP Table on both alpha and Beta and finally on your host machine

let me know ....

Bye

R

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanx!

RRiva | http://about.me/riccardoriva | http://www.riccardoriva.com
MikeD-DK
Contributor
Contributor
Jump to solution

Hello again. And thank you for your reply.

I am not sure what you mean by disableing the nic (network interface card) and enabling it again. Do you mean using the Device manager?

I am already using static IP adresses (sorry, I didn't write that in my original post)

I noticed something interesting:

ethernet0.genratedAddress are not differen! They are the same! - What the consequence of this is I dont really know. Can you help?

No firewall present in any of the machines.

Thanx

Reply
0 Kudos
rriva
Expert
Expert
Jump to solution

You have the same MAC ADDRESS on both machine, so they could not talk !

Shut down beta.

Remove NIC

Add another NIC and look again at your vmx file to have different MAC on alpha and beta and all will wors good.

let me Know

Bye

R

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanx!

RRiva | http://about.me/riccardoriva | http://www.riccardoriva.com
Reply
0 Kudos
MikeD-DK
Contributor
Contributor
Jump to solution

Hello again. Once again thanks for your quick respond.

I have tried to shut down Beta.

I have removed the Ethernet card, and added another one. However, tha ethernet0.generatedAddress remains the same as before.

I other words they still have the same address. ( I can see it both in the vmx file, and in the command prompt -> ipconfig /all)

Any ideas?

Thanx

Reply
0 Kudos
rriva
Expert
Expert
Jump to solution

your wmx file include this :

ethernet0.addressType = "generated"

Bye

R

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanx!

RRiva | http://about.me/riccardoriva | http://www.riccardoriva.com
Reply
0 Kudos
MikeD-DK
Contributor
Contributor
Jump to solution

Hello

Yes the vmx-files for both VM includes that line:

ethernet0.addressType = "generated"

and also:

ethernet0.generatedAddress = "Same MAC address on both machines"

ethernet0.generatedAddressOffset = "0"

Thanx

Reply
0 Kudos
rriva
Expert
Expert
Jump to solution

You can put this in your .vmx file:

uuid.action = "create"

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanx!

RRiva | http://about.me/riccardoriva | http://www.riccardoriva.com
rriva
Expert
Expert
Jump to solution

otherwise you can add a second nic, startup the machine, look if you have a different MAC and then remove the first one.

If you can solve you can use SMAC 2.0 MAC Address Changer

http://www.klcconsulting.net/smac/

Bye

R

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanx!

RRiva | http://about.me/riccardoriva | http://www.riccardoriva.com
Reply
0 Kudos
rriva
Expert
Expert
Jump to solution

If no one of the above works, you can :move the VM folder on another location, power on the VM with another VMWare Workstation and select "I copied IT" when it prompt.

Bye

R

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanx!

RRiva | http://about.me/riccardoriva | http://www.riccardoriva.com
Reply
0 Kudos
MikeD-DK
Contributor
Contributor
Jump to solution

Hello I will try this as soon as possible, but probably not untill next week as I have an important assignment.

Thanx in advance.

Reply
0 Kudos
rriva
Expert
Expert
Jump to solution

Any news ?

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanx!

RRiva | http://about.me/riccardoriva | http://www.riccardoriva.com
Reply
0 Kudos
MikeD-DK
Contributor
Contributor
Jump to solution

Hello, I'm back working with this. Thank you for your patience. I will have an answer for you at the end of the day, I expect.

Reply
0 Kudos
MikeD-DK
Contributor
Contributor
Jump to solution

Your suggestion about creating a new nic and then deleting the "old" one did the trick. I got a new MAC-address. Now everything works fine. Thanks a bunch for your help, advice and guidance.

Reply
0 Kudos
rriva
Expert
Expert
Jump to solution

Smiley Wink very happy for you !

Bye

R

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanx!

RRiva | http://about.me/riccardoriva | http://www.riccardoriva.com
Reply
0 Kudos