Custom Query (16363 matches)
Results (937 - 939 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #6403 | obsolete | BindIP does not work for inbound NAT port-forwarded connections | ||
| Description |
Linux HostOS with multiple secondary IPs bound. 1.1.1.x are public/outside addresses in this example.
eth0 - primary hostos IP 1.1.1.1 Hostos has tcp/22 bound specifically to 1.1.1.1 with sshd using the "ListenAddress 1.1.1.1" directive in sshd_config. Now setting the guestos to bind to 1.1.1.2: VBoxManage setextradata "guest os" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/BindIP" "1.1.1.2" VBoxManage setextradata "guest os" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/Protocol" TCP VBoxManage setextradata "guest os" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/GuestPort" 22 VBoxManage setextradata "guest os" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/HostPort" 22 Then when trying to connect to ssh -p 22 1.1.1.2 connection is refused, and wireshark dump on the hostos shows it is being reset. Testing this by binding to tcp/23 for the guestos on the outside of the NAT: VBoxManage setextradata "guest os" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/Protocol" TCP VBoxManage setextradata "guest os" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/GuestPort" 22 VBoxManage setextradata "guest os" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/HostPort" 23 Now, ssh -p 23 1.1.1.2 works. However, ssh -23 1.1.1.1 is also being forwarded to the guestos, but is not what is expected due to the BindIP of 1.1.1.2. Hostos netstat reports guestos is binding ALL (0.0.0.0) tcp/23 connections. This should not be. For instance, should I want to bind 1.1.1.2:80 to guestosA and 1.1.1.3:80 to guestosB, you cannot, as the first guestos that starts will bind to all 0.0.0.0:80. The BindIP should limit what IP address the NAT's are bound to. |
|||
| #6411 | obsolete | Windows guest hang on restart (Similar #3679) | ||
| Description |
After installing all the latest Microsoft updates, Windows XP, 2003 Server, 2008 Server, and 2008 R2 Server (only versions tested so far) hang on restart. Guest OS goes through the Windows shutdown process and right before the restart it hangs and has to be manually reset. So far the OS shutdown process has completed but restart hangs. |
|||
| #6417 | obsolete | RPD not scaling well | ||
| Description |
I saw some forums on the web complaining about the rdp session in virtualbox not scaling well. I'm having some weird problems. I understand that when i connect to my virtualmachine via the embedded rdp server of vbox i'm getting some sort of console session instead of a real terminal server session in the guest OS, so i should change the resolution manually in the video configuration of the guest OS in order to get the resolution i want. But if I inadvertently maximize my rdp client window (doesn't matter if i'm using mstsc or rdesktop-vrdp), my screen stop refreshing. The session still works, but i have to keep disconnecting and connecting again to have screen updates in order to change manually the resolution back to what was set before. The host machine doesn't have a GUI, so all the work was done using VBoxManage and VBoxHeadless. The host is a Debian Lenny AMD64 and the host is a Windows Server 2008 Standard 32bit. |
|||

