Page 1 of 1

Froward Port on 2 different GOSes

Posted: 15. Jul 2009, 17:22
by defo
Hi!
I am install 3.0.2 on my ubuntu, and make 2 different guest Os (ubuntu server).
I have forwarding port in first gOS by method:
(in first gOs xml file)
<ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/openssh/Protocol" value="TCP"/>
<ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/openssh/GuestPort" value="22"/>
<ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/openssh/HostPort" value="2222"/>
<ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/openhttp/Protocol" value="TCP"/>
<ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/openhttp/GuestPort" value="80"/>
<ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/openhttp/HostPort" value="8888"/>
its work great. but i want have 2 gOs (in one time) and forwarding another port to second virtual machine.
like :
(in second gOs xml file)
<ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/openssh2/Protocol" value="TCP"/>
<ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/openssh2/GuestPort" value="22"/>
<ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/openssh2/HostPort" value="2000"/>
<ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/openhttp2/Protocol" value="TCP"/>
<ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/openhttp2/GuestPort" value="80"/>
<ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/openhttp2/HostPort" value="8000"/>
localhost:8888 - work (and ssh too)
but
localhost:8000 - dont work

if i running second OS without first gOS - dont work too

where is my problem?
first and second gOSes - its clone of one VDI
thanx, and sorry i have bad English.

Re: Froward Port on 2 different GOSes

Posted: 30. Jul 2009, 20:07
by defo
i try to change digits in "pcnet/0/LUN#0" patern. nothing.
i have no ideas!
help me

Re: Froward Port on 2 different GOSes

Posted: 30. Jul 2009, 21:33
by Sasquatch
The other VM does have a working network? When you clone an installed VM (especially if it's Linux based), the NIC inside the VM can get a different name, thus rendering existing configuration useless.