"The remote session was disconnected because there were network problems during the licensing protocol" After Installing RemoteFX
Whenever I attempt to connect to my virtual machine after installing RemoteFX, I get the following error: "The remote session was disconnected because there were network problems during the licensing protocol."
I am running Server 2012 on the following hardware, with Windows 7 Ultimate as the VM.
Server Specs
-
i7-2600k
-
NVIDIA 560TI
-
8GB RAM
-
400GB HDD
Any help would be greatly appreciated.
November 25th, 2012 12:56am
Hi,
Thanks for your post.
The above error, although it mentions "licensing", has nothing to do with licensing or the lack of a license server. The error message normally means that there was a network problem somewhere in the network path between the client and the target system,
or the client and the target system are not using the same version of RDP. What OS is the client that is being used in this scenario?
Best Regards,
Aiden
If you have any feedback on our support, please click
here
November 27th, 2012 5:16am
The client is Windows 7 SP1 Home Premium.
November 29th, 2012 1:24am
Hi,
Please try to install RDC 8.0 first, to see if the issue still persists.
Description of the Remote Desktop Protocol 8.0 update for Windows 7 SP1 and Windows Server 2008 R2 SP1
http://support.microsoft.com/kb/2592687
Best Regards,
Aiden
November 29th, 2012 7:11am
Did the update, and tried to connect with Windows 8, but still no dice.
November 30th, 2012 2:52am
Hi,
Thank you for your question.
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.
Best Regards,
Aiden
If you have any feedback on our support, please click
here
November 30th, 2012 5:21am
Hi, please help check several things.
1. Make sure "Remote Desktop Virtualization Host Agent", RemoteFX Session Manager and "RemoteFX Session Licensing" services are started and running.
2. Ensure you have the RemoteFX firewall exception on the VM.
3. Check your event log if there is any related error.
Fandy
November 30th, 2012 9:42am
Hi
I have two win8 VMs on Windows server 2012. VMs can ping each other. When RDP into a VM from the other one, get the same error message.
1. In windows server 2012, "Remote Desktop Virtualization Host Agent" is running. RemoteFX Session Manager and "RemoteFX Session Licensing" can not be found in services list at all.
2. shut down all firewall.
3. Did not found any related errors in event logs.
December 1st, 2012 1:24am
More info,
If remove RemoteFX adaptor, the error goes away.
If connect a VM with RemoteFX adaptor in Hyper-V manager, GPU works.
December 1st, 2012 1:27am
I don't see either of the RemoteFX services. Can this be the issue?
December 2nd, 2012 11:27pm
Any updates?
I'm having the same type of errors trying to configure this for TFS lab Management.
One thing I noticed that may cause an issue is that our VMs do not and will never belong to a domain since they are constantly setup and torn down for TFS code tesing environments. I have read in several other places that the VMs using RemoteFX must
belong to the domain in order to get a license, is this correct?
-
Edited by
erkisnotgod
Thursday, December 06, 2012 12:31 PM
December 6th, 2012 12:30pm
Any updates? It would be nice to get it up before the holidays.
December 9th, 2012 12:48am
Nothing new yet, but our contacts from Avnet have opened a support case with MSFT. I will let you know on any progress.
December 9th, 2012 12:57am
I have the same problem. And when i try to connect my Windows 8 Enterprise, it works fine !!
My impression is Windows Server 2012 and RemoteFX doesn't work with Windows 7 (enterprise or ultimate) like Windows Server 2008 R2.
I hope it's going to change because my users are not ready to work with Windows 8 ....
December 11th, 2012 7:42am
To get RemoteFX working on Server 2012 with a Win 7 client, you need to install these two KB articles KB2574819 then KB2592687.
You will also most likely need to configure the remote desktop licensing.
This will fix the licensing protocol error, but if you need DirectX10 support in your connection, it is very much broken.
Our case with MSFT is still being worked on at the moment
December 11th, 2012 1:39pm
Hi erkisnotgod,
As you have opened a case with Microsoft, it will be more efficient to troubleshoot the issue. If you have any feedback, it would be appreciate if you can post it here for reference,
thank you.
Regards,
Fandy
December 13th, 2012 7:32am
Any updates? I really need a resolution here.
December 17th, 2012 5:26pm
Here is what I have so far.
1st step:Install KB KB2574819 and KB2592687 on the Win 7 VM and perform any Group policy mods needed.
Obtain, install and configure remote desktop licencing per MSFT usage requirements on the Server.
Make sure that the RDC still works with the standard Hyper-V GPU.
Shut down the VM.
Add the RemoteFX 3D vide Adaptor and power on the VM.
Let the VM install the drivers and reboot as required.
After the VM reboots the VM screen should say "Video remoting was disconnected" and inform you the RemoteFX 3D is in use.
Now per response of our MSFT case, nothing above DX9 will work on Win 7, and technically the RemoteFX is NOT supported on non-enterprise versions of Win 7.
MSFT response: "Ive gotten some additional information back from the product team, and unfortunately what you are attempting to do is not supported on Windows 7. Here
is what they had to say:
When RemoteFX 3D adapter is enabled on a Windows 7 SP1 Enterprise Guest VM on a Windows Server 2012 with Hyper-V, we (MSFT) only support DirectX 9.
To get DirectX 11 support the customer must run Windows 8. From a SKU perspective we do not support the scenario of a WES 7 image with vGPU enabled as this is only supported with Windows
7 SP1 Enterprise edition, for the list of features supported see the article below:
http://blogs.msdn.com/b/rds/archive/2012/11/26/remotefx-features-for-windows-8-and-windows-server-2012.aspx
"
-
Marked as answer by
Cattmy
Tuesday, December 18, 2012 11:57 PM
-
Unmarked as answer by
Cattmy
Tuesday, December 18, 2012 11:57 PM
-
Marked as answer by
Cattmy
Tuesday, December 18, 2012 11:58 PM
December 17th, 2012 5:42pm
So I take it I need Windows 8 Enterprise, which I do not have access to. Thanks for everyone's help.
-
Proposed as answer by
andydis
Monday, February 04, 2013 2:06 PM
-
Unproposed as answer by
andydis
Monday, February 04, 2013 2:06 PM
December 18th, 2012 11:58pm
For what it's worth, I had just came across this issue using a very similar setup as the original poster and it was resolved by running the Integration Services disk on the Windows 7 guest. After that was installed and rebooted I was able to remote
into the guest while the Remote FX adapter was installed.
-
Proposed as answer by
Wayne Berry 1
Friday, September 26, 2014 10:04 PM
September 17th, 2013 8:13pm
I had the exact same issue and tried several things to make it work.
- Disable firewall (for testing purposes) no luck
- Install both KB (KB2574819 then KB2592687) no luck
- Update the Integration services as per Brian635 and voila!
I left both KB and re-enabled the firewall allowing "remote desktop" and "remote desktop - RemoteFX" Still works. My conclusion, step 2 and 3 together should work.
August 11th, 2014 1:36pm
Hey,
I'm guessing this is all sorted - however if anyone else has this issue it is related to the Windows Firewall Service.
DO NOT disable the Windows Firewall Service - if you do you will receive this error - it's okay to turn it off via the control panel but leave the service alone!
August 12th, 2014 9:34pm
You are so amazing! I spent 1 days on this issue,
and it is solved with your method!!
I can't not imagine what the difference with stopping the windows firewall service and starting
the windows firewall service but turn it off in the total remotefx confuguration?
Should this be the bug of Windows ? lol
-
Edited by
singlewing
23 minutes ago
August 18th, 2015 3:22am