VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (961 - 963 of 16363)

Ticket Resolution Summary Owner Reporter
#848 invalid No sound from windows guest via vbox RDP -> Fixed in 1.5.2. Paul Moss
Description

Centos 5 as host. Sound works fine from there. VBox 1.4. Windows XP SP2 in guest vm.

Connect from ubuntu laptop over vbox RDP to guest. Results in no sound. Only faint static noises. Connect from ubuntu laptop over MS RDP to guest. Results in sound being played.

Would prefer sound to be available with vbox RDP. As then MS RDP doesnt need to be enabled via My Computer.

Thanks

#849 fixed Keyboard Command 0xF5 (Disable Key Scaning) dont work osbios
Description

Normally the keyboard command 0xF5 is telling the keyboard to ignore any key pressing. Until the keyboard Command 0xF4 is send. This behavior is necessary to get no interference during keyboard programing. (e.g. getting the keyboard ID)

On VirtualBox this command seems to be ignored!

#850 fixed UDP NAT port forwarding broken Xavier Pitz
Description

Windows PC IP : 192.168.30.2 (condor client connecting UDP 192.168.30.3:57278)


Linux host IP : 192.168.30.3 (NAT 192.168.30.3:57278 --> 10.0.2.15:57278 (extradata set))

Windows guest IP : 10.0.2.15 (condor server listening on UDP port 57278)


The guest app properly listen on 10.0.2.15:57278 (TCPview confirms it) but the Windows PC client is never able to establish a proper communications with it.

Following extradata were configured for the VM :

Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/CD57278/Protocol, Value: UDP

Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/CD57278/GuestPort, Value: 57278

Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/CD57278/HostPort, Value: 57278

I then also forwarded UDP ports 57279 & 57280 from the host to the guest, and was looking to test with another UDP client/server software. I tried scorched 3D. I was able to see in the scorched 3D server, that the incoming connections from the client appeared as coming from the guest virtual default gateway (10.0.2.2) and not from the windows client IP (192.168.30.2). This is why I think UDP NAT is broken in VirtualBox 1.5.2. NAT Translation based on virtual default gateway IP instead of the real origin IP maybe. I think that no NATed UDP applications are yet able to communicate with external machines (except the host itself maybe).

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy