Home » Blogs » Kevin Kleinfelter's blog

Networking VirtualBox and VMware

Submitted by Kevin Kleinfelter on Tue, 2008-02-12 22:32.

I'm fiddling around with VMWare Player and VirtualBox VMs.  Naturally, I wanted to see if I could network between the two.  The following seems to work. (VB=VirtualBox; VW=VMWare)

  • Create a TAP adapter (Adapter 1) via VB's VirtualBox.exe running in the host.
    • Attached to Host Interface
    • Interface Name = VirtualBox Host Interface 1 (matching the device name created by TAP)
    • Cable Connected
  • In VW's vmnetcfg.exe, create:
    • VMNet0(Bridged) = Bridget to VirtualBox TAP Adapter
    • VMNet1(Host-only) = Subnet 192.168.11.0; DHCP Start 128 and End 254
    • VMNet8(NAT) = Subnet 192.168.18.0; DHCP Start 128 and End 254; NAT gateway is 192.168.8.2
    • No "automatic bridging"
    • NAT tab says VMnet host = VMnet8
  • In Windows Network Connections:
    • Ethernet-internal = DHCP
    • Cisco VPN (Not used)
    • Wireless Network Connection (Not used)
    • VMware Network Adapter VMnet1
      • Client for Microsoft Networks enabled; File and printer sharing for Microsoft Networks enabled; TCP/IP enabled with static IP 192.168.11.1 and no default gateway
    • VMware Network Adapter VMnet8
      • Client for Microsoft Networks enabled; File and printer sharing for Microsoft Networks enabled; TCP/IP enabled with static IP 192.168.18.1 and no default gateway
    • VirtualBox Host Interface 1
      • Client for Microsoft Networks enabled; VMWare Bridge Protocol enabled; File and printer sharing for Microsoft Networks enabled; TCP/IP enabled with static IP 192.168.0.1 and no default gateway
  • Inside VB Windows 2000 client (Network and Dial-up Connections)
    • Host-only Connection 4 = Client for Microsoft Networks enabled; File and printer sharing for Microsoft Networks enabled; TCP/IP enabled with static IP 192.168.0.101 and default gateway 192.168.0.1
    • Local Area Connection 3 = disabled
  • Inside VW Windows 2000 client
    • Ethernet1-VMNet0-Bridged = Client for Microsoft Networks enabled; File and printer sharing for Microsoft Networks enabled; TCP/IP enabled with static IP 192.168.0.10 and no default gateway
    • Ethernet2-VMNet8-NAT = Client for Microsoft Networks enabled; File and printer sharing for Microsoft Networks enabled; TCP/IP enabled with static IP 192.168.18.10 and default gateway 192.168.18.2 and DNS server 192.168.18.2
    • Ethernet3-VMNet1-HostOnly = Client for Microsoft Networks enabled; File and printer sharing for Microsoft Networks enabled; TCP/IP enabled with static IP 192.168.11.10 and no default gateway
Bookmark/Search this post with:
»

Printing in NAT mode

Submitted by Anonymous (not verified) on Mon, 2008-02-18 14:53.

Hello,

With VirtualBox, are you successful in printing from your guest OS (Windows XP) configured via NAT on a Linux host OS (Ubuntu)?

I can't use NAT and NetBIOS/SaMBa... So, impossible to join the Windows domain, impossible to print, impossible to access share from my VM...

Best regards,

   Fabrice

»

Printing on Host's Printer From Vbox VM Client

Submitted by Kevin Kleinfelter on Sun, 2008-02-24 17:44.

If you're having trouble with NAT and NETBIOS, I recommend setting up a TAP virtual adapter in the host, sharing your printer via the TAP adapter, and using Host-only networking from the client.

»