Is this normal behavior? Internal Address tries to get out

[Mike_Fcpa]

We installed VMWare Workstation on a few of our Windows XP desktop.

Two extra nics were created with internal IP address.. No problems with that.

The problems that this give us, is that those two Virtual nics, with those internal IP address send out legit packets to my infrastructure( Mainly our active directory servers). My AD severs gets confuses and tries to answer to those query through our firewall(normal behavior). My Firewall blocks them of courses. This is non stop, and would like to fix that. I tried unbinding those interface to the Microsoft windows Client.. but this goes on.

In windows XP, you can define orders of NIC.. My primary is #1.

We're running a fully patch Windows XP. And VM Ware 6 build 45731.

Here's IPCONFIG..

onfiguration IP de Windows

Nom de l'hôte . . . . . . . . . . : DevBox

Suffixe DNS principal . . . . . . : acme.com

Type de nœud . . . . . . . . . . : Hybride

Routage IP activé . . . . . . . . : Non

Proxy WINS activé . . . . . . . . : Non

Liste de recherche du suffixe DNS : acme.com

acme.com

Carte Ethernet VMware Network Adapter VMnet8:

Suffixe DNS propre à la connexion :

Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8

Adresse physique . . . . . . . . .: 00-50-56-C0-00-08

DHCP activé. . . . . . . . . . . : Non

Adresse IP. . . . . . . . . . . . : 192.168.199.1

Masque de sous-réseau . . . . . . : 255.255.255.0

Passerelle par défaut . . . . . . :

Carte Ethernet VMware Network Adapter VMnet1:

Suffixe DNS propre à la connexion :

Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1

Adresse physique . . . . . . . . .: 00-50-56-C0-00-01

DHCP activé. . . . . . . . . . . : Non

Adresse IP. . . . . . . . . . . . : 192.168.199.2

Masque de sous-réseau . . . . . . : 255.255.255.0

Passerelle par défaut . . . . . . :

Carte Ethernet Connexion au réseau local:

Suffixe DNS propre à la connexion : acme.com

Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection

Adresse physique . . . . . . . . .: 00-0D-60-48-9C-BA

DHCP activé. . . . . . . . . . . : Oui

Configuration automatique activée . . . . : Oui

Adresse IP. . . . . . . . . . . . : 10.0.18.239

Masque de sous-réseau . . . . . . : 255.0.0.0

Passerelle par défaut . . . . . . : 10.0.0.6

Serveur DHCP. . . . . . . . . . . : 10.0.2.30

Serveurs DNS . . . . . . . . . . : 10.0.2.70

10.0.2.75

Bail obtenu . . . . . . . . . . . : 5 mai 2008 10:58:52

Bail expirant . . . . . . . . . . : 5 mai 2008 22:58:52

[Peter_vm]

If you are not planning to use NAT or Host-Only communiction with your host, you can safely delete those two host virtual NICs, using VMware Virtual Network Settings...

[mike_laspina]

Hi,

That is the default for the VMware NAT service. You can unbind them from the local bridged adapter or stop the services or delete them. Most of the time I set them (DHCP and NAT) to manual start.

[Mike_Fcpa]

Thanks to all who replies.. Let me clarify something.. My Vms need to communicate with the network. They're running DHCP, and get assigned 10.0.0.0 addresses. I beleive that the VmCards with the 192.168 address is used from VM to the host. It's weird behavior that those cards are used outside of this scope.

If I delete those two cards, will network still work on my Vms?

Thanks again! :smileygrin:

[Peter_vm]

Attach/post "vmware.log" files of your VMs. I have no idea which virtual networks they use.

[mike_laspina]

If your VM's are issued an internal DHCP address then you are using the bridged adaptor and do not require NAT or hostonly. Simply stop the NAT and DHCP services and set them to manual as well you do not need to delete anything.

[Peter_vm]

Unless he uses VMnet1 (which has DHCP by default) and bridged it to physical NIC. That is what I'm trying to determine.

[mike_laspina]

Adresse physique . . . . . . . . .: 00-0D-60-48-9C-BA

DHCP activé. . . . . . . . . . . : Oui

Configuration automatique activée . . . . : Oui

Adresse IP. . . . . . . . . . . . : 10.0.18.239

It's not, the bridge is on 10.x.x.x and VMware always defaults to 192.168.x.x on the vmnet's

He indicated his VM's are using DHCP based 10.x.x.x addresses.

[Peter_vm]

I could be wrong, but you know what happens when you have two DHCP servers on the same Ethernet segment... You sometimes get IP from one, sometimes from the other.

[mike_laspina]

Good point, I have been there before.

[Mike_Fcpa]

DHCP assigns a 10.0.0.0 address.. Those two vmnet cards were assigned 192 automaticly, I did nothing for that to happens... I'm more used to ESX and that doenst make sence to me.

Why VM Workstation needs two VMnet at 192 addresses? In my head, that would make better sence on my host PC, to have one Physycal NIC, one VM NIc(With Vm MAC and a 10.0.0.0 address). And Physical PC would forward coresponding packets to VM.

Thanks! :smileygrin:

[Peter_vm · Accepted solution]

It doesn't make sense to me either.

VMware does NOT assign the same subnet to VMnet1 and VMnet8. Something is really wrong here:

Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8

Adresse physique . . . . . . . . .: 00-50-56-C0-00-08

DHCP activé. . . . . . . . . . . : Non

Adresse IP. . . . . . . . . . . . : 192.168.199.1

Masque de sous-réseau . . . . . . : 255.255.255.0

Passerelle par défaut . . . . . . :

Carte Ethernet VMware Network Adapter VMnet1:

Suffixe DNS propre à la connexion :

Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1

Adresse physique . . . . . . . . .: 00-50-56-C0-00-01

DHCP activé. . . . . . . . . . . : Non

Adresse IP. . . . . . . . . . . . : 192.168.199.2

Masque de sous-réseau . . . . . . : 255.255.255.0

Passerelle par défaut . . . . . . :

If you are planning to continue using VM using bridged connection (VMnet0), you can delete misconfigured VMnet1 and VMnet8 virtual networks AND corresponding host virtual NICs.

Use VMware Virtual Network Settings... GUI to to that.

[Mike_Fcpa]

Yes, I'll give that a try..

Thanks for your help!!

PS.. Btw, the two VMnet interface, ARE on the same subnet.. 192.168.199.1 and 192.168.199.2 255.255.255.0 is the same subnet.

[Peter_vm]

PS.. Btw, the two VMnet interface, ARE on the same subnet.. 192.168.199.1 and 192.168.199.2 255.255.255.0 is the same subnet.

And they should NOT be on the same subnet. Did you configure them that way?

[Mike_Fcpa]

Yes yes, I used vmnet0 for brige, and deleted those two..

Everything works fine now..

Thanks!