Can't use VRDP after upgrade to 4.0 on headless VMs
Posted: 17. Jan 2011, 10:52
As I said in object, I'm unable to connect to our headless Virtualbox VMs through VRDP (now called VRDE?!) to both our virtual-machine running on Mac OS X 10.5 Server. One of them is Windows 2003 Server with Terminalservice, and connection to windows works fine, as guest itself... Upgrade was flawless, or seemed so; I'd upgraded additions too, through terminalservice connection, but can't connect through Virtualbox VRDP service. The other vm is an old XP machine i guess it works too, but I haven't enabled windows to be connected, so without VRDP I can't have any confirm.
Taking some more informatin form VMs, both shows Address 0.0.0.0, like this:
Port is OK, but I guess address should be our Server address, because until now I used this address to connect through VRDP... Am I right? How can I change VM VRDP address (if I should)?
Taking some more informatin form VMs, both shows Address 0.0.0.0, like this:
Code: Select all
VRDE: enabled (Address 0.0.0.0, Ports 3397, MultiConn: off, ReuseSingleConn: off, Authentication type: null)
