Solved: Network problem [garbage out]

johnh1 · ‎04-07-2009

Hello,

I have two virtual machines with windows xp. On the first one, network is working good but form the second one i just can't ping the host. I have tried a lot of settings but none worked.

The strange part is that the second one virtual machine is sending garbage on the network.

Here are some information about my host

vmware -v

VMware Workstation 6.5.0 build-118166

uname -a

Linux localhost 2.6.29 #1 SMP Thu Apr 2 07:51:47 GMT 2009 i686 Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz GenuineIntel GNU/Linux

I haven't done much traffic on the virtual machines but:

ifconfig

eth0 Link encap:Ethernet HWaddr 00:xx:xx:xx:xx:xb

inet addr:xx.xx.xx.xx Bcast:xx.xx.xx.xx Mask:255.255.255.128

inet6 addr: xx:xx:xxxxxxxxx/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:27283 errors:0 dropped:0 overruns:0 frame:0

TX packets:13422 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:16510582 (15.7 MiB) TX bytes:2409688 (2.2 MiB)

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING MTU:16436 Metric:1

RX packets:1072 errors:0 dropped:0 overruns:0 frame:0

TX packets:1072 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:115452 (112.7 KiB) TX bytes:115452 (112.7 KiB)

vmnet0 Link encap:Ethernet HWaddr 00:50:56:c0:00:00

inet addr:192.168.220.1 Bcast:192.168.220.255 Mask:255.255.255.0

inet6 addr: fe80::250:56ff:fec0:0/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:778531439 errors:1937064516 dropped:7536919 overruns:7536903 frame:3318590176

TX packets:1701147247 errors:0 dropped:16 overruns:1802724708 carrier:900896397

collisions:1701738319 txqueuelen:1000

RX bytes:1802724708 (1.6 GiB) TX bytes:779120500 (743.0 MiB)

vmnet1 Link encap:Ethernet HWaddr 00:50:56:c0:00:01

inet addr:192.168.214.1 Bcast:192.168.214.255 Mask:255.255.255.0

inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:822873100 errors:772475659 dropped:1377047572 overruns:654903561 frame:2720409126

TX packets:806030091 errors:755698443 dropped:738855434 overruns:604506120 carrier:2434933282

collisions:705301002 txqueuelen:1000

RX bytes:789252875 (752.6 MiB) TX bytes:772475659 (736.6 MiB)

Second virtual machine (wich is not working) is attached to a custom specific virtual network (vmnet1)

vmnet-sniffer /dev/vmnet1

ARP sender 00:0c:29:c3:41:8e 192.168.214.2 target 00:00:00:00:00:00 192.168.214.2 ARP request

IP src 192.168.214.2 dst 224.0.0.22 unknown protocol 2

IP src 192.168.214.2 dst 192.168.214.255 UDP src port 137 dst port 137

IP src 192.168.214.2 dst 224.0.0.22 unknown protocol 2

IP src 192.168.214.2 dst 192.168.214.255 UDP src port 137 dst port 137

ARP sender 00:0c:29:c3:41:8e 192.168.214.2 target 00:00:00:00:00:00 192.168.214.1 ARP request

IP src 192.168.214.2 dst 192.168.214.255 UDP src port 137 dst port 137

On the host there is no firewall and the virtual machine has the default windows firewall.

Because VMware Workstation 6.5.0 build-118166 is not working with kernel 2.6.29 i had to patch files (patch is attached).

Thank you!

AWo · ‎04-07-2009

To keep it simple: VMware Workstation offers three kinds of networks for connecting guests (I list the defualt setup):

1. VMnet0 or bridged

By using this, you virtual NIC (vNIC) will be attached directly to the physical NIC (pNIC) where the bridge protocol is bound to. That means your guest appears on the physical network as its own instance with its own IP setup, just like any other host. That is maybe something you don't want to use if you want to hide or secure your guests.

2. VMnet1 or host-only

This is a virtual network where the host and all guests (when the vNIC is configured to be "host-only") participates. The host NIC in this network is VMnet1. By using this network, your guests are completely isolated from the outside world, but they are still connected to the host. That is not what you want as you would like to still communicate to the outside.

3. VMnet8 or NAT

That is much the same as VMnet1 but the guests can communicate to the outside as this network is bound to every TCP/IP stack on the host. Thereby you must use this vNIC type if you use something different than an ethernet pNIC. That is maybe what you should use. This hides the guests from the outside as the host sits between the guests and the physical network acting like a proxy and NAT device.

VMnet1 and VMnet8 are served by the VMWare DHCP server.

I would suggest you bring the VMware Network stuff back to the default. Then configure the vNICs of your guests to NAT. Thereby they communicate to each other and the host via VMnet8. They are not visible or accessible from the outside but they can communicate to the world.

Does that address your need?

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

AWo

VCP / vEXPERT 2009

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =

View solution in original post

AWo · ‎04-07-2009

Welcome to the forums!

What do you want to achive by using the custom network type for the vitual NIC's? Any special reason?

What is your goal regarding the network? If we need what you try to achive we can help.

From what I see you mixed up the default a little bit which makes this not easier.

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

AWo

VCP / vEXPERT 2009

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =

johnh1 · ‎04-07-2009

Hello,

Thank you for your answer.

I don't use custom network type for a special reason. I just want to have link between my virtual machine and host. I will use it for improving my computer security and sometimes i will need access to internet (but when i want i will use linux's SNAT and ip_forward). So, if ping host will work i will consider that everything works.

I tried to use the default settings but have not worked.

AWo · ‎04-07-2009

To keep it simple: VMware Workstation offers three kinds of networks for connecting guests (I list the defualt setup):

1. VMnet0 or bridged

By using this, you virtual NIC (vNIC) will be attached directly to the physical NIC (pNIC) where the bridge protocol is bound to. That means your guest appears on the physical network as its own instance with its own IP setup, just like any other host. That is maybe something you don't want to use if you want to hide or secure your guests.

2. VMnet1 or host-only

This is a virtual network where the host and all guests (when the vNIC is configured to be "host-only") participates. The host NIC in this network is VMnet1. By using this network, your guests are completely isolated from the outside world, but they are still connected to the host. That is not what you want as you would like to still communicate to the outside.

3. VMnet8 or NAT

That is much the same as VMnet1 but the guests can communicate to the outside as this network is bound to every TCP/IP stack on the host. Thereby you must use this vNIC type if you use something different than an ethernet pNIC. That is maybe what you should use. This hides the guests from the outside as the host sits between the guests and the physical network acting like a proxy and NAT device.

VMnet1 and VMnet8 are served by the VMWare DHCP server.

I would suggest you bring the VMware Network stuff back to the default. Then configure the vNICs of your guests to NAT. Thereby they communicate to each other and the host via VMnet8. They are not visible or accessible from the outside but they can communicate to the world.

Does that address your need?

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

AWo

VCP / vEXPERT 2009

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =

johnh1 · ‎04-08-2009

I already restored default settings. It seems that NAT is working fine, and thank you for that. But sometimes i just want host only networking, and this part is still not working. Guest OS is getting IP trough DHCP, but when i ping the host, errors are just filling

vmnet1 Link encap:Ethernet HWaddr 00:50:56:c0:00:01

inet addr:192.168.146.1 Bcast:192.168.146.255 Mask:255.255.255.0

inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:44433408 errors:21368585 dropped:1639326 overruns:197536 frame:2764649017

TX packets:20317152 errors:28513206 dropped:1441804 overruns:2694840442 carrier:107487720

collisions:20317151 txqueuelen:1000

RX bytes:2693333114 (2.5 GiB) TX bytes:21368576 (20.3 MiB)

AWo · ‎04-09-2009

But sometimes i just want host only networking, and this part is still not working. Guest OS is getting IP trough DHCP, but when i ping the host, errors are just filling

How do you achive this? Do you change the guest vNIC type to "host-only"?

Please post "ifconfig -a" from host, "ipconfig /all" from guest and the content of the .vmx file when it is not working.

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

AWo

VCP / vEXPERT 2009

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =

johnh1 · ‎04-14-2009

Hello,

Sorry that i wrote you so late. I have to go to some places, and i will be back in two weeks.

Until then i can say that my problem was resolved because now i have internet access for my guest machines. Thank you for that! I gave you a "correct answer"!

All

Network problem [garbage out]