Has anyone ever gotten this to work?
I installed OS/2 4.52 on Virtualbox 1.5.6 and it can ping itself but not any other machines on the same subnet or the host which is on the same subnet.
I tried using the NAT, Host Interface, and Internal Network in the network settings for the VM w/ no luck.
I can't ping the OS/2 guest from the host or ping the host from the guest...
setting up TCP/IP on OS/2 guest so it's visible to host
With Host Interface networking, you need to configure the bridge on the host, and also in the guest you need to be able to get on the local LAN; ie. get a DHCP address or however your local LAN allows clients on.
I had OS/2 set up with a host interface connection at one time and it worked fine, though I got a couple of BSOD's on the Vista x64 host. The network driver at the time may not have been quite ironed out.
I had OS/2 set up with a host interface connection at one time and it worked fine, though I got a couple of BSOD's on the Vista x64 host. The network driver at the time may not have been quite ironed out.
enable bridging on host?
Dum question time: how do you do this? It sounds like that's the piece I'm missing since it's not set up automatically by VirtualBox
On OS/2, I set up a static IP that is also on the same subnet as the host. OS/2 can ping itself but can't ping any machine on the same subnet. The host can't ping the OS/2 guest.
On OS/2, I set up a static IP that is also on the same subnet as the host. OS/2 can ping itself but can't ping any machine on the same subnet. The host can't ping the OS/2 guest.
You need to set up a network bridge on the host. With different host OS's it's different. With Windows it's just a matter of selecting the two interfaces (the hardware ethernet adapter and the virtual one) and choosing the "bridge these" option. Linux is apparently a little more typing, and may involve sacrificing a goat, I'm not sure. Actually I think the PDF explains how to do it in at least Ubuntu.
Thanks much.
FYI, go into control panel, then ctrl-click to select the Virtualbox and host interface and tell it to bridge them and it creates a bridge. Copy your TCP/IP settings to the Network Bridge properties (WinXP and higher hosts) if you're using a static IP because it'll default to DHCP. If you don't do this, you'll lose network connectivity to the Internet.
This is sort of explained in the online help which I should have read
It's a bit confusing that you have to create this bridge to talk to it because in VMWare and VirtualPC, you can connect to a host interface and it'll automatically create a bridge for you (VMWare has a Bridge Protocol adapter that's added automatically to all network devices).
The Virtualbox way is more flexible because you can create bridges anywhere you need to, e.g., between a few VMs or network adapters.
FYI, go into control panel, then ctrl-click to select the Virtualbox and host interface and tell it to bridge them and it creates a bridge. Copy your TCP/IP settings to the Network Bridge properties (WinXP and higher hosts) if you're using a static IP because it'll default to DHCP. If you don't do this, you'll lose network connectivity to the Internet.
This is sort of explained in the online help which I should have read
It's a bit confusing that you have to create this bridge to talk to it because in VMWare and VirtualPC, you can connect to a host interface and it'll automatically create a bridge for you (VMWare has a Bridge Protocol adapter that's added automatically to all network devices).
The Virtualbox way is more flexible because you can create bridges anywhere you need to, e.g., between a few VMs or network adapters.