Does anyone know things about VMWare virtual machines? I want my virtual machine to be able to use the host-only network connection thingy to access a samba server on the host (Ubuntu). How do I set up this?
The virtual network card works, as in bridging mode it can connect to the internet. The host now has a device named vmnet1, which should apparently be where the guest connects in host-only mode. But I can't see anything through pinging. Not even totally sure what address to ping. Windows claims to be connected to something with ip address 192.168.0.16. The vmnet1 device says: vmnet1 Link encap:Ethernet HWaddr 00:50:56:c0:00:01 inet addr:192.168.38.1 Bcast:192.168.38.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:87 errors:0 dropped:0 overruns:0 frame:0 TX packets:154 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
So you've got a windows VM on a Linux host, with the VM's NIC set to host-only mode. vmnet1 on the host is the virtual NIC connecting the host to the host only network, which looks to be set up correctly.
If the VM is reporting its IP as 192.168.0.16 something's going wrong there, as it should have an address in 192.168.38.0/24, and it should be getting this from the DHCP service provided by vmware player on the host. Try manually setting the IP on the VM to 192.168.38.2, mask 255.255.255.0 and DNS 192.168.38.1. You should then be able to ping the host from the VM on the hosts vmnet1 IP, 192.168.38.1
My experience is with windows hosted vmware workstation and ESX (which runs on bare metal) but it ought to be the same.
Comments 3
Reply
The virtual network card works, as in bridging mode it can connect to the internet. The host now has a device named vmnet1, which should apparently be where the guest connects in host-only mode. But I can't see anything through pinging. Not even totally sure what address to ping. Windows claims to be connected to something with ip address 192.168.0.16. The vmnet1 device says:
vmnet1 Link encap:Ethernet HWaddr 00:50:56:c0:00:01
inet addr:192.168.38.1 Bcast:192.168.38.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:87 errors:0 dropped:0 overruns:0 frame:0
TX packets:154 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Reply
If the VM is reporting its IP as 192.168.0.16 something's going wrong there, as it should have an address in 192.168.38.0/24, and it should be getting this from the DHCP service provided by vmware player on the host. Try manually setting the IP on the VM to 192.168.38.2, mask 255.255.255.0 and DNS 192.168.38.1. You should then be able to ping the host from the VM on the hosts vmnet1 IP, 192.168.38.1
My experience is with windows hosted vmware workstation and ESX (which runs on bare metal) but it ought to be the same.
Reply
Leave a comment