VISTA host. LINUX guest. wish to reach GUEST from HOST

oclet · Post by **oclet** » 28. Jan 2009, 06:15

I have a VISTA host running newest Virtualbox.

I have a linux debian 32 bit guest.

I want to reach the vista host from the linux guest, via ping and samba .
I wish to reach the linux guest from the vista host, via ssh.

so from the Vista host, i would like to mount samba exported FS inside of linux host.
from vista host, i would like to ssh to the linux guest. I want this to work when
my windows machine vista host is not connected to the net. pretend I am sitting somewhere messing around with my machine, no net connection, but i want to interact with my linux guest.

I have configured two network interfaces in Linux guest. first one works great.
is NAT interface. I have networking inside of linux guest. I can reach the internet through eth0 . this works fine. I'm happy with this.

I have configured a second interface inside of the linux guest, eth1. in the Vista host, in Virtualbox, I have tried:

- making it a HOST nic , connected to wireless nic
- making it a HOST nic, conncted to the LAN nic (not the wireless)
- making it a HOST nic, connected to the tap32 virtualbox driver interface.

I can't get it to work right. Which HOST should I connect the 2nd nic to? What ip should i give the interface inside of the guest? Should I give the nic an IP in the Vista Host?

thanks

choppedliver · Post by **choppedliver** » 28. Jan 2009, 10:42

I have a similar problem.

VISTA HOST, 64 Bit
UBUNTU GUEST v8.10, 32 Bit

Latest VBOX, 2.1.2

NAT works great, but I want to run a server on the GUEST and reach from HOST. Cant do this with NAT unless do PORT FORWARDING.

Tried port forwarding, doesnt work, using vboxmanage. Tried several instructions from forums, instruction manual, etc. No luck.

Tried HOST INTERFACE, instead of NAT, doesnt work either.

This sucks.

Post by **Sasquatch** » 28. Jan 2009, 12:52

HIF is what you need. There must be an active link on the interface you use though. You can always install the MS Loopback adapter. See the VirtualBox FAQ for more info.

choppedliver · Post by **choppedliver** » 28. Jan 2009, 17:01

Like I said, Ive tried nat, which works, but cant run a server because port forwarding with vboxmanage doesnt seem to work.

And Ive tried using the Host Interface method by selecting

Adapter type: Intel Pro/1000 MT Desktop
Attached to: Host Interface

Host Interface: Intel(R) 82562V-2 10/100 Network Connection
( My only choice )

oclet · Post by **oclet** » 28. Jan 2009, 17:11

I have installed a HIF interface

I have successfully installed the MIcrosoft loopback interface

So I still cannot reach my host Vista OS from my guest Linux OS, and the
other way around.

How should I configure the loopback interface? Should I give it an IP?
Which net?

How should i configure eth1 in my guest linux OS ? Should I give it an IP?
What ip and netmask?

thanks

Post by **Sasquatch** » 28. Jan 2009, 22:12

The interfaces need an IP address, else it won't listen to any connections. You can use any IP address in the private space, just make sure that it won't conflict with any existing networks.

oclet · Post by **oclet** » 28. Jan 2009, 22:38

should I:

- set the IP in Windows Vista Host microsoft loopback device?

- set the IP in eth1 of the Debian Guest OS ?

- or both?

Post by **Sasquatch** » 28. Jan 2009, 22:39

Both of course. How would either OS respond to the other one if it doesn't know where to listen on?

oclet · Post by **oclet** » 28. Jan 2009, 22:42

ok so would i give the windows microsoft loopback interface and the guest OS eth1 nics the exact same IP and netmask settings ?

oclet · Post by **oclet** » 28. Jan 2009, 23:59

I tried setting the ip and netmask to the same value in the microsoft loopback interface on the Host and on eth1 on the linux guest... and of course that doesn't work.

This is where I am confused.

I am not sure what values to give the interfaces to they can see each other.

Post by **baf** » 29. Jan 2009, 00:17

One way
Host
192.168.X.1

Guest
192.168.X.2

Both mask 255.255.255.0

X any number from 1-254 that you dont have any network on.

oclet · Post by **oclet** » 29. Jan 2009, 07:15

ok i've done that

I've configure the MS loopback interface to be 192.168.100.1

I've configured the Linux guest eth1 interface to be 192.168.100.2

I can't reach host from guest or guest from host

Any more ideas?

Post by **Sasquatch** » 30. Jan 2009, 20:48

No firewalls that are blocking things? Connecting through IP instead of name?