[FIXED] Can't connect after changing windows 7 RDP port

[Doc11]

Hello, I've searched the faq and the forum for a bit and couldn't find any info or topic about my current issue.
In case you know of or can find a link that already deals with this issue, I'll gladly read it.

Otherwise, here is my problem:
I have a windows 7 guest installed in virtualbox 5.0.10 r104061 with Oracle_VM_VirtualBox_Extension_Pack-5.0.12-104815.
virtualbox guest additions are installed
The network adapter is set as bridged, using Paravirtualized network adapter (virtio-net). I have tried intel adapters as well.
The vm runs well, and I can connect to it via rdp with the default port (3389) without any problem.

However, for security reasons, I usually change the rdp port in windows using the method described by microsoft in kb306759 (sorry, can't post link yet)
I has worked on all physical and virtual machines (using vmware I admit) I installed up to today.

Now that I'm experimenting with virtualbox to replace vmware, it won't connect anymore once I've change the port.
The guest system is nowhere to be found using rdp with a custom port.

Plz halp!

[socratis]

virtualbox 5.0.10 r104061 with Oracle_VM_VirtualBox_Extension_Pack-5.0.12-104815

The ExtPack version has to match the VirtualBox version. I would upgrade my VirtualBox to the latest and greatest, 5.0.12 as of this writing. See if that helps...

[Doc11]

The ExtPack version has to match the VirtualBox version. I would upgrade my VirtualBox to the latest and greatest, 5.0.12 as of this writing. See if that helps...

I could have bet that I downloaded both on the same day... Apparently I would have been wrong.
So, I just installed VirtualBox 5.0.12 b104815, reinstalled the extension pack as well as the guest additions.

The problem didn't disappear.
rdp will connect just fine to the guest with default port, and won't connect with custom port.

Thanks for noticing that detail though.

[Perryg]

If you are using RDP directly to the host and not through the vRDP used by VirtualBox ( host ip + port ) then the issue would be with the guest. How exactly are you connecting?
Where are you changing the port and if you are changing the port in the guest settings and not using vRDP the port really never changes in the guest.

[Doc11]

If you are using RDP directly to the host and not through the vRDP used by VirtualBox ( host ip + port ) then the issue would be with the guest. How exactly are you connecting?
Where are you changing the port and if you are changing the port in the guest settings and not using vRDP the port really never changes in the guest.

As I mentioned, I change the rdp port in the registry as described by microsoft in kb306759
It has worked flawlessly on every windows I've installed for a few years now, be it with a physical or virtual machine.
Considering switching to virtualbox and this is the first time I've encountered that issue.

I use bridged network adapter to avoid that kind of issue, but apparently it doesn't work here.

vrdp is not enabled on that vm, and doesn't need to be since I want to connect directly to the guest.
For the sake of testing, I have tried enabling it with the same custom port as the guest but it doesn't change anything.

[Perryg]

Since you are directly connecting then the issue must be with the guest. VirtualBox simply provides the network connection in this scenario.

[Doc11]

VirtualBox somehow doesn't seem to let the rdp protocol pass through once the port is changed in guest windows.

That port change method works both with physical machines and virtual machines guests installed in vmware.


EDIT: wait a moment, something came up which I may have overseen as it's a fresh uncomplete install.

EDIT 2: okay, I need a new brain. Anyone knows where I can find a cheap spare one? Mine doesn't seem functional anymore.
Anyway, I usually have a third party firewall software installed... and it's not installed yet. So windows firewall... Someone slap me.


Thanks for your support, and sorry for the stupidity.

[Perryg]

All I can say is good luck and I hope you figure it out.

[Doc11]

Problem is now fixed.

Thanks again for your support and sorry for my oversight.