Hello.

I'm trying to connect remote desktop which however is situated on the local PC.

This is virtual PC machine (VirtualBox) which has VRDP.

When I try to connect it shows me following:

VRDP is set up, port forwarding is also adjusted.

I cannot connect via RDP but via telnet [ip_address] [port] all is connected good.

What's the matter?

Suncatcher_13,

If you havent already, youll need to make sure remote connections are allowed and give yourself permissions on the virtual PC to be able to initiate an RDP session.  Assuming the virtual machine is Windows 8.1, its as easy as going to the System information page and clicking on the Remote settings link on the left. 

Hope this helps!

Mike

Windows Outreach Team IT Pro

Windows for IT Pros on TechNet

The incoming remote connections are allowed. This is undoubtedly.

Take a look at the VRDP manual on the Vbox site. VRDP server is functioning on the host machine regardless of the guest machine installed (Windows, Linux or other). In my particular case it's Linux Mint.

Authentication of connection session is external. 

This means that mstsc uses host system account while connecting. It has NO relation to installed guest system.

Previously all went fine but after Windows reinstallation and router change all have broken.

What is the reason?

Maybe some firewall settings?

Could it be connected with Win8.1 online login?

Where can I view any connection logs?

• Edited by Suncatcher_13 Tuesday, November 11, 2014 8:19 AM

The incoming remote connections are allowed. This is undoubtedly.

Take a look at the VRDP manual on the Vbox site. VRDP server is functioning on the host machine regardless of the guest machine installed (Windows, Linux or other). In my particular case it's Linux Mint.

Authentication of connection session is external. 

This means that mstsc uses host system account while connecting. It has NO relation to installed guest system.

Previously all went fine but after Windows reinstallation and router change all have broken.

What is the reason?

Maybe some firewall settings?

Could it be connected with Win8.1 online login?

Where can I view any connection logs?

• Edited by Suncatcher_13 Tuesday, November 11, 2014 8:19 AM

Hi,

Previously all went fine but after Windows reinstallation and router change all have broken.

What is the reason?

Some settings are mostly have beenchanged, please reset the router to eliminate some filter options, check the permission setttings mentioned by Michael. Control Panel\All Control Panel Items\System\Remote settings

Maybe some firewall settings?

For firewall settings, please make sure that "Remote Desktop" is allowed under control panel\Windows firewall\ Allow an app or feature through Windows Firewall.

Where can I view any connection logs?

Please check the Event Viewer tree on the left side under "Applications and Services Logs -> Windows -> TerminalServices-* important log we should check TerminalService-LocalSessionManager Operational log

Some guides in this link can be helpful (this is an guide for Windows 7, but instructions are similiar to Windows 8.1)

http://windows.microsoft.com/en-IN/windows7/allow-remote-desktop-connections-from-outside-your-home-network

Maybe some firewall settings?

For firewall settings, please make sure that "Remote Desktop" is allowed under control panel\Windows firewall\ Allow an app or feature through Windows Firewall.

Well, I have such allowed apps setings in Firewall:

Is that what is supposed to be?

Where can I view any connection logs?

Please check the Event Viewer tree on the left side under "Applications and Services Logs -> Windows -> TerminalServices-* important log we should check TerminalService-LocalSessionManager Operational log

I've checked the logs and finally found this errors. Many errors with different texts, e.g. 

RDP ClientActiveX est intentando conectarse al servidor (192.168.0.102)

Se desconect la conexin multitransporte.

RDP ClientActiveX se ha desconectado (razn= 1801)

El servidor es compatible con SSL = not supported

Base64(SHA1(NombreDeUsuario)) es = AqV0LPo7xEn3SmpQ0+Xg8Gc+Dl8=-kKn5l5YXjU0uuho38ut+UzYu6tM=

RDP ClientActiveX se ha desconectado (razn= 2308)

and like these.

I've saved all these events in file and uploaded here.

What are these reasons 1801, 2308? Where are they documented? What are the solutions?

• Edited by Suncatcher_13 10 hours 19 minutes ago

Hi

You are stating that you want to connect to a VirtualBox virtual machine and that this machine is running as a guest machine inside of your machine, please correct me if I have misunderstood that part. As for the remote connectivity to the guest operating system, I understand that you would like to establish a remote connection from the host machine in to the VM, is that correctly understood?

The things that come to mind are:

1. When connecting to the Linux VM, has port 4444 on the VirtualBox VRDP Configuration worked before the system reinstall? If so, did you also do any configuration changes to the Microsoft RDP client in order to connect to the port 4444 instead of the standard RDP port TCP 3389?
2. Have you tried changing the port configuration on the VirtualBox configuration?

Assuming that your computer reinstall originated from wanting to get Windows 8.1 on your computer, I would also like to present the possibility of migrating the virtual machine in question to utilizing the built in Client Hyper-V role of Windows 8.1. If your environment is not specifically dependent on utilizing the VirtualBox functionality, the Client Hyper-V is easily enabled by the following steps

1. On your start screen, type "activate" (or equivalent in your language) and choose the "Enable or disable Windows functions"
2. Select the "Hyper-V"-section and make sure to enable both the Hyper-V Management Tools as well as the Hyper-V itself.
3. Reboot the computer and you should now be able to launch "Hyper-V Manager" and build your environment from there.

Is making the transition to Microsoft Hyper-V instead of VirtualBox appeals as a plausible solution, perhaps the cross-systems connectivity could be sorted as well?

Hi

You are stating that you want to connect to a VirtualBox virtual machine and that this machine is running as a guest machine inside of your machine, please correct me if I have misunderstood that part. As for the remote connectivity to the guest operating system, I understand that you would like to establish a remote connection from the host machine in to the VM, is that correctly understood?

Absolutely! You understand the case quite perfectly.

But as I stated previously:

>> Take a look at the VRDP manual on the Vbox site. VRDP server is functioning on the host machine regardless of the guest machine installed (Windows, Linux or other). In my particular case it's Linux Mint.

There is absolutely no matter which guest OS is installed.

>> When connecting to the Linux VM, has port 4444 on the VirtualBox VRDP Configuration worked before the system reinstall?

Yes.

>> If so, did you also do any configuration changes to the Microsoft RDP client in order to connect to the port 4444 instead of the standard RDP port TCP 3389?

No. How do you think could I change standard MS client if I even didn't know how to see its logs till this moment?

I specify port like this

Like usual. Without any hidden configurations.

>> Have you tried changing the port configuration on the VirtualBox configuration?

Yes. Nothing changed. I've got the same error.

>> I would also like to present the possibility of migrating the virtual machine in question to utilizing the built in Client Hyper-V role of Windows 8.1

Could be-could be, but I have no Hyper-V option in Windows functions activation. Maybe it's PRO-feature?

Nevertheless, I'm waiting for analyse results of my logs.

Where can I view any connection logs?

Please check the Event Viewer tree on the left side under "Applications and Services Logs -> Windows -> TerminalServices-* important log we should check TerminalService-LocalSessionManager Operational log

I've checked the logs and finally found this errors. Many errors with different texts, e.g. 

RDP ClientActiveX est intentando conectarse al servidor (192.168.0.102)

Se desconect la conexin multitransporte.

RDP ClientActiveX se ha desconectado (razn= 1801)

El servidor es compatible con SSL = not supported

Base64(SHA1(NombreDeUsuario)) es = AqV0LPo7xEn3SmpQ0+Xg8Gc+Dl8=-kKn5l5YXjU0uuho38ut+UzYu6tM=

RDP ClientActiveX se ha desconectado (razn= 2308)

and like these.

I've saved all these events in file and uploaded here.

What are these reasons 1801, 2308? Where are they documented? What are the solutions?

• Edited by Suncatcher_13 Saturday, January 31, 2015 9:54 PM