virtualbox.org

Hello All!

I am brand new to this community, and indeed to using Virtual Box, and have an issue with the software - to put it into context I need to use Virtual Box to given Debian a container for a Windows platform for some software for an Internet radio station, the software is called Centova Cast.

My setup is as follows: Windows 2003 Server behind a MODEM, NOT a router, with encoding software (Edcast & SHOUTcast) streaming to the Internet. I am trying to get a connection between Debian, Virtual Box, and Windows and finding it rather difficult!!!

I have contacted Centova Cast who offer rather limited technical support, largely down to the fact they offer a paid for installation service I suspect, but being a Computer Technician I am keen to resolve this myself.

I currently have the Ethernet and Virtual Box connected bridged together in Windows, which appears to have allocated the Bridge connection a permanent internal I.P. address. When I go into Debian and run ifconfig a it cannot detect the Network Card. I should say my Linux knowledge is very, very, limited.

I have N.A.T. selected within the port forwarding of Virtual Box, to (hopefully) allow data to be passed through to Windows.

That's the issue, can anyone help please?

Thanks.

Nathan.

From the hosts terminal/command window type VBoxManage showvminfo <VM Name> --details and post here. Replace <VM Name> with the actual name of the VM. Use " " if the name has a space in it.

Note if the host is Windows you need to be in the directory that has VBoxManage.exe for the command to work.

Perryg wrote:From the hosts terminal/command window type VBoxManage showvminfo <VM Name> --details and post here. Replace <VM Name> with the actual name of the VM. Use " " if the name has a space in it.

Note if the host is Windows you need to be in the directory that has VBoxManage.exe for the command to work.

Hello Perryg,

Thanks for your response.

I have done as you suggested, and as you are probably expecting, there is rather a lot of information to post through following the command you asked me to enter into the Command Prompt, so here goes:

Code: Select all

C:\Program Files\Oracle\VirtualBox>VBoxManage showvminfo "Centova II"
Name:            Centova II
Groups:          /
Guest OS:        Debian (32 bit)
UUID:            45181c1d-31ef-49bf-957b-3ed032470479
Config file:     C:\Documents and Settings\Administrator.01MAY-8VYDTKLAY\Virtual
Box VMs\Centova II\Centova II.vbox
Snapshot folder: C:\Documents and Settings\Administrator.01MAY-8VYDTKLAY\Virtual
Box VMs\Centova II\Snapshots
Log folder:      C:\Documents and Settings\Administrator.01MAY-8VYDTKLAY\Virtual
Box VMs\Centova II\Logs
Hardware UUID:   45181c1d-31ef-49bf-957b-3ed032470479
Memory size:     512MB
Page Fusion:     off
VRAM size:       12MB
CPU exec cap:    100%
HPET:            off
Chipset:         piix3
Firmware:        BIOS
Number of CPUs:  1
PAE:             off
Long Mode:       off
Synthetic CPU:   off
CPUID overrides: None
Boot menu mode:  message and menu
Boot Device (1): Floppy
Boot Device (2): DVD
Boot Device (3): HardDisk
Boot Device (4): Not Assigned
ACPI:            on
IOAPIC:          off
Time offset:     0ms
RTC:             UTC
Hardw. virt.ext: on
Nested Paging:   on
Large Pages:     off
VT-x VPID:       on
VT-x unr. exec.: on
State:           aborted (since 2014-03-29T21:01:07.093000000)
Monitor count:   1
3D Acceleration: off
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration:
Autostart Enabled: off
Autostart Delay: 0
Default Frontend:
Storage Controller Name (0):            IDE
Storage Controller Type (0):            PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  2
Storage Controller Port Count (0):      2
Storage Controller Bootable (0):        on
Storage Controller Name (1):            SATA
Storage Controller Type (1):            IntelAhci
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1):  30
Storage Controller Port Count (1):      1
Storage Controller Bootable (1):        on
IDE (1, 0): Empty
SATA (0, 0): C:\Documents and Settings\Administrator.01MAY-8VYDTKLAY\VirtualBox
VMs\Centova II\Centova II.vdi (UUID: c2077aa7-8eef-4fd0-919a-79eac536c662)
NIC 1:           MAC: 080027B93AD4, Attachment: Bridged Interface 'MAC Bridge Mi
niport', Cable connected: on, Trace: off (file: none), Type: Am79C973, Reported
speed: 0 Mbps, Boot priority: 0, Promisc Policy: allow-all, Bandwidth group: non
e
NIC 2:           MAC: 08002778396A, Attachment: NAT, Cable connected: on, Trace:
 off (file: none), Type: Am79C973, Reported speed: 0 Mbps, Boot priority: 0, Pro
misc Policy: allow-vms, Bandwidth group: none
NIC 2 Settings:  MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, re
ceive: 64)
NIC 2 Rule(0):   name = Centova Web, protocol = tcp, host ip = 212.159.60.105, h
ost port = 80, guest ip = 169.254.117.19, guest port = 80
NIC 2 Rule(1):   name = Centova Web inteface, protocol = tcp, host ip = 212.159.
60.105, host port = 2199, guest ip = 169.254.117.19, guest port = 2199
NIC 2 Rule(2):   name = Centova server clusters, protocol = tcp, host ip = 212.1
59.60.105, host port = 2198, guest ip = 169.254.117.19, guest port = 2198
NIC 2 Rule(3):   name = Icecast, protocol = tcp, host ip = 212.159.60.105, host
port = 8000, guest ip = 192.168.56.102, guest port = 8000
NIC 2 Rule(4):   name = Icecast 2, protocol = tcp, host ip = 169.254.56.88, host
 port = 8000, guest ip = 192.168.56.102, guest port = 8000
NIC 3:           disabled
NIC 4:           disabled
NIC 5:           disabled
NIC 6:           disabled
NIC 7:           disabled
NIC 8:           disabled
Pointing Device: USB Tablet
Keyboard Device: PS/2 Keyboard
UART 1:          disabled
UART 2:          disabled
LPT 1:           disabled
LPT 2:           disabled
Audio:           enabled (Driver: DSOUND, Controller: AC97)
Clipboard Mode:  disabled
Drag'n'drop Mode: disabled
VRDE:            disabled
USB:             enabled
EHCI:            disabled

USB Device Filters:

<none>

Available remote USB devices:

<none>

Currently Attached USB Devices:

<none>

Bandwidth groups:  <none>

Shared folders:  <none>

VRDE Connection:    not active
Clients so far:     0

Video capturing:    not active
Capture screens:    0
Capture file:       C:\Documents and Settings\Administrator.01MAY-8VYDTKLAY\Virt
ualBox VMs\Centova II\Centova II.webm
Capture dimensions: 1024x768
Capture rate:       512 kbps
Capture FPS:        25

Guest:

Configured memory balloon size:      0 MB


C:\Program Files\Oracle\VirtualBox>

I hope that is useful to you?

Nathan.

Code: Select all

NIC 1: MAC: 080027B93AD4, Attachment: Bridged Interface 'MAC Bridge Miniport', Cable connected: on, Trace: off (file: none), Type: Am79C973, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: allow-all, Bandwidth group: none

NIC 2: MAC: 08002778396A, Attachment: NAT, Cable connected: on, Trace:off (file: none), Type: Am79C973, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: allow-vms, Bandwidth group: none

NIC 2 Settings: MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, receive: 64)
NIC 2 Rule(0): name = Centova Web, protocol = tcp, host ip = 212.159.60.105, host port = 80, guest ip = 169.254.117.19, guest port = 80
NIC 2 Rule(1): name = Centova Web inteface, protocol = tcp, host ip = 212.159.60.105, host port = 2199, guest ip = 169.254.117.19, guest port = 2199
NIC 2 Rule(2): name = Centova server clusters, protocol = tcp, host ip = 212.159.60.105, host port = 2198, guest ip = 169.254.117.19, guest port = 2198
NIC 2 Rule(3): name = Icecast, protocol = tcp, host ip = 212.159.60.105, hostport = 8000, guest ip = 192.168.56.102, guest port = 8000
NIC 2 Rule(4): name = Icecast 2, protocol = tcp, host ip = 169.254.56.88, hostport = 8000, guest ip = 192.168.56.102, guest port = 8000

Why the miniport?
Where did you get these rules?

Perryg wrote:

Code: Select all

NIC 1: MAC: 080027B93AD4, Attachment: Bridged Interface 'MAC Bridge Miniport', Cable connected: on, Trace: off (file: none), Type: Am79C973, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: allow-all, Bandwidth group: none

NIC 2: MAC: 08002778396A, Attachment: NAT, Cable connected: on, Trace:off (file: none), Type: Am79C973, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: allow-vms, Bandwidth group: none

NIC 2 Settings: MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, receive: 64)
NIC 2 Rule(0): name = Centova Web, protocol = tcp, host ip = 212.159.60.105, host port = 80, guest ip = 169.254.117.19, guest port = 80
NIC 2 Rule(1): name = Centova Web inteface, protocol = tcp, host ip = 212.159.60.105, host port = 2199, guest ip = 169.254.117.19, guest port = 2199
NIC 2 Rule(2): name = Centova server clusters, protocol = tcp, host ip = 212.159.60.105, host port = 2198, guest ip = 169.254.117.19, guest port = 2198
NIC 2 Rule(3): name = Icecast, protocol = tcp, host ip = 212.159.60.105, hostport = 8000, guest ip = 192.168.56.102, guest port = 8000
NIC 2 Rule(4): name = Icecast 2, protocol = tcp, host ip = 169.254.56.88, hostport = 8000, guest ip = 192.168.56.102, guest port = 8000

Why the miniport?
Where did you get these rules?

The Miniport (Bridge) is there as I was advised that Centova Cast requires a bridge to enable it to communicate with the Internet from within Virtual Box. There is a bridge within the Devices option in Virtual Box but that cuts to guest off from the Internet completely, so the only other place I could create a bridge was within Windows.

As for "these rules", I don't know what you're talking about, sorry Perryg.

Well someone put the rules in because they are not normal or by default.

The 169.254.117.19 are apippa addresses meaning that they can't go anywhere actually. Microsoft uses them if there is no Internet or network available.

So let's look at this in a different light.
1) Since you do not have a router you must use VBox NAT, which will get you to the Internet.
2) You need access to the host from the guest so you use the Host-only adapter to achieve this.
3) I assume the port forwarding is because the guest needs to use a port so that is the port forwarding, When you do that you access the guest with the hosts ip and port that you assign to the guest using the port forwarding assistant in the network portion of the guest setting under network advanced.

I suggest you study chapter 6 in the VBox users manual

Perryg wrote:Well someone put the rules in because they are not normal or by default.

The 169.254.117.19 are apippa addresses meaning that they can't go anywhere actually. Microsoft uses them if there is no Internet or network available.

So let's look at this in a different light.
1) Since you do not have a router you must use VBox NAT, which will get you to the Internet.
2) You need access to the host from the guest so you use the Host-only adapter to achieve this.
3) I assume the port forwarding is because the guest needs to use a port so that is the port forwarding, When you do that you access the guest with the hosts ip and port that you assign to the guest using the port forwarding assistant in the network portion of the guest setting under network advanced.

I suggest you study chapter 6 in the VBox users manual

So apippa addresses are useless in this context then?

1) Understood I think - I have setup the port forwarding already to allow Centova Cast to send/receive packets from ports 80, 2198, 2199, and 8000.

2. I presume the Host Adapter is that which I can select within Virtual Box?

3) Yes, the guest needs to be able to receive the streams from the playout software installed and operating on the host, pass them onto the guest - Debian/Centova Cast and send them out online.

If Chapter 6 is about N.A.T., I think I already have!

Does this make sense?

To add to my previous reply, I have read Chapter 6 as you suggested perryg, and hope that I understand most of it.

One aspect concerns me where it states that when one chooses Bridged Network in the V.M. that a list of network devices appears and implies that the Host (in my case Windows) adapter - and therefore driver - should appear, but it doesn't, is this correct?

However, I have also read that Virtual Box has the most used 'out of the box' drivers built in, so that if one chooses an interface from the list available, I presume Windows detects this and installs a 'virtual driver' for the V.M. in its system.

Is this correct?

Bridged will only work for you if you have a router in your LAN, but yes there is a driver installed.
For Windows newer than XP you should use the Intel PRO/1000 MT Desktop (82540EM) drivers in the pull down.

As for your port forwarding rules you need to delete them all and then use the GUI in the network setting to forward only the port. Leave out the other information like IP address as the wizard will know what to do with it. This way there will be less of a chance for errors.

Perryg wrote:Bridged will only work for you if you have a router in your LAN, but yes there is a driver installed.
For Windows newer than XP you should use the Intel PRO/1000 MT Desktop (82540EM) drivers in the pull down.

As for your port forwarding rules you need to delete them all and then use the GUI in the network setting to forward only the port. Leave out the other information like IP address as the wizard will know what to do with it. This way there will be less of a chance for errors.

Thanks Perryg, I do find that a bit confusing, as I thought a Windows bridged network allowed Windows to treat the V.M. and guest like another machine, which a router would normally do, so I thought with no router, I would need a bridge in either Windows or the V.M.? Obviously not...? I presume I still select the network interface you mention within V.M. drop-down menu only within N.A.T., not Bridged Network?

Regarding the port forward rules, and deleting all the existing information, I assume you mean the rules within Virtual Box not Windows?

It was true that before VirtualBox had its own Bridge network, you would bridge with the Host, and that might be true today, but the mini port adapter is not what it would have used IIRC. You have to setup the Bridge with the network settings in the Windows host. Its been so long I don't remember the steps now. But that being said, It really depends on the software you are using, and I don't have that. In any regards the VBox NAT uses the hosts adapter to get to the Internet. The host-only allows the host and guest to communicate. You can ( although you would need someone else to tell you how ) setup IPtables in such a way that the guest gets its information and sends information on the host-only adapter.

But all of this is advanced networking and outside the scope of this forum.

Perryg wrote:It was true that before VirtualBox had its own Bridge network, you would bridge with the Host, and that might be true today, but the mini port adapter is not what it would have used IIRC. You have to setup the Bridge with the network settings in the Windows host. Its been so long I don't remember the steps now. But that being said, It really depends on the software you are using, and I don't have that. In any regards the VBox NAT uses the hosts adapter to get to the Internet. The host-only allows the host and guest to communicate. You can ( although you would need someone else to tell you how ) setup IPtables in such a way that the guest gets its information and sends information on the host-only adapter.

But all of this is advanced networking and outside the scope of this forum.

That is pretty much what I currently have setup: I have both the Virtual Box Host-Only Network bridged with the LAN to make a Network Bridge. If I run an ipconfig /a at the Command Prompt it gives the Ethernet Adapter Network Bridge an address of: 169.254.119.19 which you suggested in a previous post was an 'dead' address?

If you have actually/successfully setup the host-only network you would have an address of 192.168.56.* on the host and guest.
You need to check under the preferences -> networking in the main VirtualBox GUI to see if it is in fact setup properly and that DHCP has been enabled.

All in all you might be a lot better off buying a cheap home router. They usually run around $40.00 or so.

Perryg wrote:If you have actually/successfully setup the host-only network you would have an address of 192.168.56.* on the host and guest.
You need to check under the preferences -> networking in the main VirtualBox GUI to see if it is in fact setup properly and that DHCP has been enabled.

All in all you might be a lot better off buying a cheap home router. They usually run around $40.00 or so.

I am sending this message via Debian in Virtual Box!

From if config /a I get:
root@debian:/home/nathan# ifconfig -a
eth0 Link encap:Ethernet HWaddr 08:00:27:06:55:f8
inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0
inet6 addr: fe80::a00

fe06:55f8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:13 errors:0 dropped:0 overruns:0 frame:0
TX packets:76 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1882 (1.8 KiB) TX bytes:10178 (9.9 KiB)

eth1 Link encap:Ethernet HWaddr 08:00:27:15:1a:2b
inet6 addr: fe80::a00

fe15:1a2b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:21 errors:0 dropped:1 overruns:0 frame:0
TX packets:98 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2434 (2.3 KiB) TX bytes:21616 (21.1 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:54 errors:0 dropped:0 overruns:0 frame:0
TX packets:54 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:22597 (22.0 KiB) TX bytes:22597 (22.0 KiB)

root@debian:/home/nathan#

I have checked under File->Preferences->Network, and D.H.C.P. was not enabled, when I enable it it tells me I have an invalid server address and network mask. I guess I have to re-make the bridge and start again!

Here are the defaults

: host-only-1.png (25.24 KiB) Viewed 2610 times

: host-only-2.png (28.41 KiB) Viewed 2610 times

virtualbox.org

WIndows 2003 Server on Debian with Centova.

WIndows 2003 Server on Debian with Centova.

Re: WIndows 2003 Server on Debian with Centova.

Re: WIndows 2003 Server on Debian with Centova.

Re: WIndows 2003 Server on Debian with Centova.

Re: WIndows 2003 Server on Debian with Centova.

Re: WIndows 2003 Server on Debian with Centova.

Re: WIndows 2003 Server on Debian with Centova.

Re: WIndows 2003 Server on Debian with Centova.

Re: WIndows 2003 Server on Debian with Centova.

Re: WIndows 2003 Server on Debian with Centova.

Re: WIndows 2003 Server on Debian with Centova.

Re: WIndows 2003 Server on Debian with Centova.

Re: WIndows 2003 Server on Debian with Centova.

Re: WIndows 2003 Server on Debian with Centova.

Re: WIndows 2003 Server on Debian with Centova.