Paul,
I notice you didn't include the quotation marks in the commands you quoted. That may well make a difference.
The relevant part of the manual is here:
http://www.virtualbox.org/manual/UserManual.html#natforward
If that doesn't fix it, try releasing the .vdi disk image, delete your virtual machine and then create a new virtual machine using your old .vdi disk image.
Peter.
2010/1/7 Paul Grenyer paul.grenyer@gmail.com:
Hi All
On Tue, Jan 5, 2010 at 11:03 PM, samwise samwise@bagshot-row.org wrote:
I'm pretty sure you can just use the VBoxManage command - it's documented in the VirtualBox manual.
A blog description is available here:
http://sk.c-wd.net/wp/2008/01/05/virtualbox-port-forwarding-with-linux-host/
I tried as Peter suggested:
VBoxManage setextradata WinSrv2003 VBoxInternal/Devices/pcnet/0/LUN#0/Config/mssql/HostPort 1433
VBoxManage setextradata WinSrv2003 VBoxInternal/Devices/pcnet/0/LUN#0/Config/mssql/GuestPort 1433
VBoxManage setextradata WinSrv2003 VBoxInternal/Devices/pcnet/0/LUN#0/Config/mssql/Protocol TCP
I restarted VirtualBox as the instructions suggested and now when I try and start my VM I get what you can see in the attached picture.
I'll have some time to see if I can undo the commands later, but if anyone has seen this before and has some suggestions it would be greatly appreciated.
-- Thanks Paul
Paul Grenyer e: paul.grenyer@gmail.com b: paulgrenyer.blogspot.com