Alexey Eremenko schrieb: > I have Trouble setting up NAT port-forwarding. > > At first, I did according to VBox documentation: > VBoxManage setextradata "Windows XP" > "VBoxInternal/Devices/pcnet/0/LUN#0/Config/seamlessrdp/UDP" 0 > VBoxManage setextradata "Windows XP" > "VBoxInternal/Devices/pcnet/0/LUN#0/Config/seamlessrdp/GuestPort" 3389 > VBoxManage setextradata "Windows XP" > "VBoxInternal/Devices/pcnet/0/LUN#0/Config/seamlessrdp/HostPort" 3389 > > This is written in the Official VBox documentation: BTW why UDP ??? It > should be TCP !
UDP=0 means TCP (it's a boolean, with value 0 and 1). This is a result of how the option is passed internally, and I agree that it's confusing. However those internal settings were only meant to be temporary solutions until we have some time to integrate this properly into the frontends (command line and GUI). The latest SVN version still understands the old UDP=0 config, but the official way to select UDP/TCP has changed: VBoxManage setextradata "Windows XP" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/seamlessrdp/Protocol" TCP > So next I tried with: > VBoxManage setextradata "Windows XP" > "VBoxInternal/Devices/pcnet/0/LUN#0/Config/seamlessrdp/TCP" 1 > VBoxManage setextradata "Windows XP" > "VBoxInternal/Devices/pcnet/0/LUN#0/Config/seamlessrdp/GuestPort" 3389 > VBoxManage setextradata "Windows XP" > "VBoxInternal/Devices/pcnet/0/LUN#0/Config/seamlessrdp/HostPort" 33 > > So I did the same again with TCP now, but the port-forwarding doesn't > seem to come alive ! > When I did: nmap localhost, I saw that my guest has no extra port. > > Are there any troubleshooting commands? netstat -an is your friend if you want to figure out which ports (TCP/UDP) are listening. Works on both Linux and Windows host. Also keep in mind that on Linux as a normal user you can only provide services on ports > 1024. Also check the release log, there's a full dump of the configuration settings. However the previous code didn't check the config for unrecognized settings, thus you could feed it unrecognized stuff without noticing it (like you did with the TCP setting, which is totally meaningless). This is no longer possible, and you might get an error starting a VM with incorrect config. Remove the conflicting TCP config if this happens to you (specify the key without a value to remove it). BTW: The previous default was to create a UDP forwarding, which you should have got in your second attempt. This is also changed, because few people use UDP server services. -- Klaus Espenlaub InnoTek Systemberatung GmbH, http://www.innotek.de _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
