Hi Guys,

I am getting confuse in trying to forward port 53 (BIND9) from guest SlackWare 13.1 64-bit to host Windows 7 64-bit.
As per manual, I need to use the vbox command line utility "VBoxManage"
# VboxManage modifyvm "VM name" --natpf1 "guestdns,tcp,,53,,53" --> which I have done as such. When I reboot my VM and check to see if the port 53 was indeed forwarded, i get nothing. To check if the port was forwarded, I use
# VBoxManage.exe getextrada SlackWare131 enumerate
That command line reveals that the port 53 was not forwarded.
I tried to forward the port with "setextradata" as such
# VBoxManage.exe setextradata "name of vm" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/DNS/HostPort" 53
# VBoxManage.exe setextradata "name of vm" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/DNS/GuestPort" 53
# VBoxManage.exe setextradata "name of vm" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/DNS/Protocol"TCP
But again to no avail.
I did allow Vbox to passthrough the Windows 7 firewall.
I cant seem to be able to work this out and any help would be much appreciated

I am having a bit of a doubt as far as the name of the network adatper. I am doing NAT and the adapter as the value of 1. So as per manual the name "natpf1" seems to be right but since all my efforts have come to no good, I am doubting myself now and if you guys could confirn that as well

PS: Could it be that on a unix platfomr you need to be root to forward port below 1024. Hence not allowing to do so on the gues SlackWare131 64-bit ?
If that is the case, how could I run my DNS Server (BIND9) in my VM ?

Kind Regards,

I have got news..
I found out that the issue of me not being able to forward any port is due to me not knowing the type of network adapter VBox is emulating and therefore inputing the wrong emulation type in my command line. My VM is emulating Intel PRO/1000 MT Desktop (82540EM). I cannot find the right name for this emulation. If anyone out there could help me, that would be much appreciated..
I did issue a couple of commands on the host to forward other port than 53. Above 1024. I forwarded the port 3128 which worked when I had a look at the XML file. Due to the wrong emulation name for the NIC, when I restarted my VM I got this error:

Failed to open a session for the virtual machine SlackWare
unknown error creating VM
(VERR_CFGM_INVALID_CHILD_PATH)

Result Code:
E_FAIL (0x80004005)
Component:
Console
Interface:
IConsole {6375231a-c17c-464b-92cb-ae9e128d71c3}

I issued a port forward with emulator: natpf1, e1000, 82540EM but to no avail. The port forwarding worked but every single time when I rebooted my VM I got the error mentionned above. My VM did not accept those names.
I then had the idea of changing the adapter to PCnet-PCI II (Am79C970A). The VM worked and could connect to the internet. I then issued a port-forward command for port 3128 which worked as per XML file. When I rebooted, I got the error mentionned above again.
This is a complete deadlock for me. I hope someone has the solution for me as this VM is suppose to run SQUID and BIND9. Big bump..... The host being windows is not really helping either. I have very little experience with WIndows and that does not help..

Kind Regards,

Have you looked in the ~/.VirtualBox/Machines/<machine name>/<machine name>.xml file? It lists the adapter types in use in the Network section.

Alternatively VBoxManage showvminfo <machine name> | grep '^NIC ' | grep -v disabled

Thanks catkin for your reply.
yes I checked the xml file.
<Adapter slot="1" enabled="false" MACAddress="080027A28F22" cable="true" speed="0" type="82540EM">
<DisabledModes>
<NAT>
I used adapter type mentionned in the XML file above and still got the error message mentionned in my last message.

Kind Regards,

The thread is marked SOLVED; if you solved it, would you like to share the solution?

I did not really solved anything. For some unknown reasons to me, no adapter was being recognized when trying to forward my ports in a NAT mode. I tried on two VMs that I have running; one of slackware and the other one of Ubuntu. Both gave me the same error message everytime (mentionned in my message above). I therefore decided to bridge all my VMs. It does make it easier because I can now more easily communicate with my VMs from externally. NAT was kicking my ass so bad that for the moment I will keep bridging until I find out why the adapter used is not recognized when doing port forwarding. I have a feeling its a simple thing but have no idea what it is..