broken VRDP in 6.0.4 on AMD HW

[nbi]

Linux rdesktop (1.8.4) and also vinagre cannot connect to port 3389 on AMD HW. This problem does not exist on an Intel PC, but is 100% reproducible on AMD HW. When rdesktop/vinagre fail they exit with error code 76 (protocol error). I have verified that ms-wbt-server is listening on port 3389 upon failure. The log file does not show any errors. This is for a Win 7 Pro 64bit guest.

[nbi]

log for win7_basic vm

[Socratis]

00:00:00.068849 Installed Extension Packs:
00:00:00.068865   VNC (Version: 6.0.4 r128164; VRDE Module: VBoxVNC)
00:00:00.068868   Oracle VM VirtualBox Extension Pack (Version: 6.0.4 r128413; VRDE Module: VBoxVRDP)

You have both the RDP *and* the VNC ExtPacks installed. Where did you get the VNC ExtPack from? It sort of needs to be compiled, it's not distributed in binary format.

And from the log, you're not using the RDP module, you're using the VNC one, which is unsupported (see ch. 9.22 Other Extension Packs):

00:00:00.443885 Audio: Initializing VRDE driver
00:00:00.445144 VNC: port = 3389
00:00:00.445308 VNC: Configuring password
...
00:00:00.568198 VNCServerImpl::VRDEResize to 720x400x32bpp

Maybe that's why you can't connect with RDP? Because you're using VNC as the protocol of choice?

[nbi]

Great catch - that must be it. I will verify in a couple of hours. I did not go out of my way to install anything extra. In fact I was under the apparently mistaken impression that there is only one extension pack. My procedure for upgrading has always been to check for Debian packages first and only if they're far from being current would I get the upgrade directly from VirtualBox. Since I installed 6.0.4 later on the AMD platform than on the Intel maybe this is a Debian packaging issue. I will verify. Thanks again for the quick catch.

Yes, removing the VNC extension pack solved the problem. I have no idea how that came to be installed, I certainly took no steps to install it. All good now. Many thanks for your help.

[Socratis]

Great!

BTW, it's usually better and faster, if issues get first addressed in the ​VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is not a bug and someone from the developers has to deal with it and close it as either [WorksForMe] (most probably), or [Invalid].