VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (424 - 426 of 16363)

Ticket Resolution Summary Owner Reporter
#21000 duplicate la instalacion viene rota xd64
Description

lo intalo despues de mucho tiempo sin instalarlo (pq antes el año pasado lo tenia instalado) viene con error critico y no abria asi q abri el setup para repararlo y me encuentro q no se puede reparar

#756 invalid Das COM-Objekt für VirtualBox konnte nicht erzeugt werden xcom
Description

Could not loadthe setting file

'C:\Dokumente und Einstellungen\meinusername\VirtualBox\VirtualBox.xml (VERR _OPEN _FAILED ).

FATAL ERROR :Invaliddocument structure

Location:

'C:\Dokumente und Einstellungen\thorsten\VirtualBox\VirtualBox.xml, lin1 column 1.

Fehlercode : E_ FAIL (0 x80004005 )

Komponente : VirtualBox

Interface: IVirtualBo

{76b25 3 c15 d4-4785 a9 d3-adc6a 462beec }

Callee RC : E_ NOINTERFACE (0x 80004002 )"

A new installation doesn´t help. OS. Windows XP Pro SP2 german

#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