Having been used to VMPlayer for decades, I experimented with VirtualBox yesterday and spent quite a few hours trying to SSH into an instance, when in VMP it was a breeze.

I understand from these answers that VBox needs port forwarding or alternatively use Bridged (which worked for sometime then broke connectivity on the guest after some time) - then I just gave up on VBox.

Why this difference in implementation between the two ? Why does VMP require no port forwarding while VBox does ? Is it for better security ?

Even cloning a VM was not as easy as it is with VMP (just copy the entire dir!)

To elaborate:

my guest IP:; host: (I am assuming (Vmnet1) is the one - so it seems like it IS being bridged (I had earlier not looked at Vmnets, just my WLAN ip 192.168.0.x- my bad) - but it still begs the question - why does it work with the VMPlayer guest in NAT mode while the actual underlying connection looks bridged ? Is VMP doing something under the covers ?) - So when I changed to Bridged, the Guest IP address is now (correctly) - and yes, I did restart after each N/w change

I guess I will accept the answer "the NAT/Bridge setting is largely irrelevant if you're only communicating from the VM Host to one of its guests"

closed as unclear what you're asking by G-Man, Stephen Kitt, Anthon, sam, jayhendren Jan 4 '17 at 0:13

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 1
    VirtualBox does not require port forwarding. I'm using a host-only network with a static IP, which I may SSH into, for example. – Kusalananda Jan 3 '17 at 17:33
up vote 1 down vote accepted

Your premise is faulty. Neither has to apply the networking in any particular way.

VMware bridges by default (that's the "VM Network") because it's a system geared towards people who run multiple VMs on a group of servers and (mostly) know exactly what they're doing with the network.

VirtualBox NATs by default because it is geared towards people who run one (or so) server on a desktop PC and quite often know little or nothing about networking.

I run a couple of VMs on VirtualBox that both NAT and bridge. (The bridge is on the host-only network so I can get to them trivially from my host. The NAT is so the servers have easy access to the Internet.)

  • I am just reporting what I experienced on my W8.1 box. I confirmed again before I wrote my question, it wasn't out of the blue. That's the way my two VMs communicate with the same guest OS version. I created a brand new guest from same ISO and tested on each of these and saw that VB assigned a 10.0 IP and couldn't connect via NAT while VM assigned a 192.168 IP and it could, without any changes. And BTW, this is VMPlayer, - both are the free versions. – killjoy Jan 4 '17 at 18:13
  • @killjoy you're saying that your VB guest couldn't connect to the rest of the network? Or that something on your network couldn't connect to the VB guest? The former would be broken; the latter would be expected with NAT. – roaima Jan 4 '17 at 18:16
  • On VB, when I couldnt ssh to my guest via NAT, obviously as I need port forwarding, I switched to Bridged, and I was able to, then the guest stopped having inet access. Obviously I must be doing something wrong, so I will retest with VB; but my main question is, how does ssh'ing into VM work with NAT without having to do any port forwarding ? – killjoy Jan 5 '17 at 20:01
  • @killjoy you cannot ssh to a guest in through a NAT interface unless it has port forwarding configured. When you switched the guest to Bridged mode it needs either to use DHCP for its network configuration or you must ensure you have created a network configuration that fits the wired LAN your host uses. Note that you probably can't do this with WiFi because WiFi client drivers typically won't allow multiple MAC addresses – roaima Jan 5 '17 at 22:47
  • I appreciate you trying to help me out here; maybe I am not being succinct enough, I CAN SSH into VMPlayer guest VM (whether over wired or WIFI and whether local or remote), even remote cloud VMs, without port forwarding, so again: my main question is, how does SSH'ing into a guest in VMPlayer work with NAT without having to do ANY port forwarding ? - My question is not about how to get it to work in VirtualBox, rather WHY port forwarding is not needed in VMPlayer. Also see Kusalananda's comment where he says PF is not needed. – killjoy Jan 7 '17 at 11:57

Not the answer you're looking for? Browse other questions tagged or ask your own question.