Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
"The remote session was disconnected because there were network problems during the licensing protocol" after enabling RemoteFX Windows 8 VM

问题 "The remote session was disconnected because there were network problems during the licensing protocol" after enabling RemoteFX Windows 8 VM

  • Saturday, December 08, 2012 6:01 PM
     
     
    Sign In to Vote
    0

    I receive the error anytime I try to connect (from Windows 7 physical client machines running the recent RDP 8 "update") to the Windows 8 VM (w/RemoteFx enabled) running on Windows Server 2012 Hyper-V Server. The GPU on the server is DirectX 11 capable. At one point this was working, however, just recently this stopped working (not sure if any Windows Server 2012 updates did this or the RDP 8 "update" for Windows 7/2008 R2).

    If I connect to the Windows 8 VM (with RemoteFx enabled) from the Hyper-V manager, the connection works (no licensing protocol errors)

    However, if I remove the RemoteFx from the Windows 8 VM, all RDP 8 clients connect fine.

    I've checked all the event logs (noticed no errors) and the Remote Desktop Virtualization Host Agent is running. I've checked the RD Licensing Diagnoser and no errors reported.


     

All Replies

  • Monday, December 10, 2012 10:21 AM
     
     
    Sign In to Vote
    0

    Please check if both of "Remote Desktop Virtualization Host Agent" and "RemoteFX Session Lincesing" service has been starded.

    “Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.”

     
  • Thursday, December 13, 2012 9:08 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi,

    I would like to confirm what is the current situation? Have you resolved the problem or do you have any further progress?

    If there is anything that we can do for you, please do not hesitate to let us know, and we will be happy to help.

    Lawrence

    TechNet Community Support

     
  • Thursday, December 13, 2012 4:56 PM
     
     
    Sign In to Vote
    0

    I didn't realize the thread moved....

    No, unfortunately the problem is not resolved. The "Remote Desktop Virtualization Host Agent" is running. I do not see anything listed for "RemoteFx Session Licensing" in the Services MMC, however, I do have "Remote Desktop Licensing" started. How does one go about getting this service ("RemoteFx Session Licensing") "installed" and to show up?

     
  • Thursday, December 13, 2012 6:42 PM
     
     
    Sign In to Vote
    0
    Did you change the connection setting to "LAN" from "Automatically detect"?

    Don Geddes - SR Support Escalation Engineer - Remote Desktop Services - Printing and Imaging

     
  • Thursday, December 13, 2012 6:53 PM
     
     
    Sign In to Vote
    0
    Yes, I just tried that and I still get the same error...this is both with an RDP client on Windows 7 as well as the RDP client on the actual Hyper-V machine (Windows 2012).
     
  • Thursday, December 13, 2012 7:06 PM
     
     
    Sign In to Vote
    0

    What GPU are you using?

    Don Geddes - SR Support Escalation Engineer - Remote Desktop Services - Printing and Imaging

     
  • Thursday, December 13, 2012 7:20 PM
     
     
    Sign In to Vote
    0
    It's an AMD Radeon HD 6310 video chipset running on an AMD E-350D APU.
     
  • Monday, December 17, 2012 9:39 PM
     
     
    Sign In to Vote
    0
    How long has this deployment been up and running?  You stated originally that it was working and now all of sudden is not. 

    Don Geddes - SR Support Escalation Engineer - Remote Desktop Services - Printing and Imaging

     
  • Tuesday, December 18, 2012 5:34 PM
     
     
    Sign In to Vote
    0

    ~end of October timeframe was when I first had it all running and then one day (late November timeframe) I went to reconnect to the Windows 8 VM that had the RemoteFx GPU enabled and I received that error message. Unfortunately the exact days I don't remember.

     
  • Tuesday, December 18, 2012 10:08 PM
     
     
    Sign In to Vote
    0
    I have another case with similar symptoms that I am working on right now, but we're still investigating.  Any chance you can open a case with Microsoft support?

    Don Geddes - SR Support Escalation Engineer - Remote Desktop Services - Printing and Imaging

     
  • Wednesday, December 19, 2012 3:11 PM
     
     
    Sign In to Vote
    0

    Would I have to use one of my "incidents" from either an MSDN or TechNet subscription to open this case?

     
  • Wednesday, December 19, 2012 5:35 PM
     
     
    Sign In to Vote
    0
    You would have to use that or PPI (pay per incident) support. 

    Don Geddes - SR Support Escalation Engineer - Remote Desktop Services - Printing and Imaging

     
  • Monday, January 07, 2013 5:22 PM
     
     
    Sign In to Vote
    0
    Has anybody figured this out? I have the exact same issue. Hyper-V on server 2012, running a Virtual macine Windows 7 x64 pro. Enabled RemoteFX 3D and can no longer RDP to this VM. 
    • Edited by JFoley22 Monday, January 07, 2013 5:23 PM
    •  
     
  • Tuesday, January 08, 2013 9:02 PM
     
     
    Sign In to Vote
    0

    What is the client OS that you are connecting from?  Two things you should try:

    1. Do NOT enable RDP 8 on the Windows 7 SP1 VM.  You should install RDP 8 and update the ICs though.

    2. Change the connection setting on the client from "Automatically detect" to "LAN"

    Don Geddes - SR Support Escalation Engineer - Remote Desktop Services - Printing and Imaging

     
  • Wednesday, January 09, 2013 1:06 AM
     
     
    Sign In to Vote
    0

    What is the client OS that you are connecting from?  Two things you should try:

    1. Do NOT enable RDP 8 on the Windows 7 SP1 VM.  You should install RDP 8 and update the ICs though.

    2. Change the connection setting on the client from "Automatically detect" to "LAN"

    Don Geddes - SR Support Escalation Engineer - Remote Desktop Services - Printing and Imaging

    My infrastructure is such... Server 2012 Datacenter, Windows 7 Enterprise 64-bit virtual machine with RemoteFX GPU installed(I said originally it was Win 7 Pro, but it is actually Enterprise if that makes a difference). I am trying an RDP session from a Windows 8 laptop to the Windows 7 Virtual machine and I get the network problems/licensing error. I can RDP just fine with the same setup to a Windows 8 Enterprise VM with RemoteFX installed just fine. 


    I am not exactly sure what you mean by "Do NOT enable RDP 8 on the Windows 7 SP1 VM. Do you mean per the KB article I shouldn't do the Group Policy stuff it suggests?

    I have tried to change the settings to LAN from Auto with no luck, same result. 

     
  • Wednesday, January 09, 2013 7:43 PM
     
     
    Sign In to Vote
    0

    What is the client OS that you are connecting from?  Two things you should try:

    1. Do NOT enable RDP 8 on the Windows 7 SP1 VM.  You should install RDP 8 and update the ICs though.

    2. Change the connection setting on the client from "Automatically detect" to "LAN"

    Don Geddes - SR Support Escalation Engineer - Remote Desktop Services - Printing and Imaging

    My infrastructure is such... Server 2012 Datacenter, Windows 7 Enterprise 64-bit virtual machine with RemoteFX GPU installed(I said originally it was Win 7 Pro, but it is actually Enterprise if that makes a difference). I am trying an RDP session from a Windows 8 laptop to the Windows 7 Virtual machine and I get the network problems/licensing error. I can RDP just fine with the same setup to a Windows 8 Enterprise VM with RemoteFX installed just fine. 


    I am not exactly sure what you mean by "Do NOT enable RDP 8 on the Windows 7 SP1 VM. Do you mean per the KB article I shouldn't do the Group Policy stuff it suggests?

    I have tried to change the settings to LAN from Auto with no luck, same result. 

    Yes, exactly, do NOT enable RDP 8 via group policy on the VM that has the vGPU.  This is from the article:

    Virtual desktops that have RemoteFX vGPU installed cannot use RDP 8.0.
    Issue
    After you install and enable RDP 8.0 by using Group Policy on a computer that has RemoteFX vGPU installed, RDP 8.0 is not available.
    Resolution
    This update does not enable RDP 8.0 for connections to computers that have RemoteFX vGPU installed. If you must have RDP 8.0 enabled, remove RemoteFX vGPU from the virtual desktop to enable RDP 8.0.

    Don Geddes - SR Support Escalation Engineer - Remote Desktop Services - Printing and Imaging

     
  • Thursday, January 10, 2013 1:45 AM
     
     
    Sign In to Vote
    0
    I tried that also, didn't work. I just ended up upgrading the VM to Windows 8 and everything is fine. 
     
  • Thursday, January 10, 2013 11:51 PM
     
     
    Sign In to Vote
    0

    I've tried to repro this issue but I'm not able to.  Every Windows 7 SP1 VM I've tried works fine as long as RDP 8 is installed but not enabled.  There is a known issue where you must change the connection setting to "LAN", but I cannot reproduce this "problems during the licensing protocol" error. 

    Don Geddes - SR Support Escalation Engineer - Remote Desktop Services - Printing and Imaging

     
  • Tuesday, January 15, 2013 8:22 AM
     
     
    Sign In to Vote
    0
    Hi Ivan Lopez, Do you have any updates on this issue?

    “Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.”

     
  • Friday, April 19, 2013 12:29 PM
     
     
    Sign In to Vote
    0

    Sorry, for some reason I wasn't receiving notifications when this thread was updated...

    No, unfortunately I'm still having the same issue. I've staged a second Hyper-V 2012 server instance, exact same hardware, went through all the same steps. I moved the Windows 8 test VM from one instance to the other added the RemoteFx virtual GPU but RemoteFx from any RDP client does not work (whether it's a Windows 7 client PC w/remote desktop client or whether it's a Windows 8 or Windows 2012 client machine w/remote desktop client. I keep getting the licensing related error message.

     
  • Friday, April 19, 2013 9:09 PM
     
     
    Sign In to Vote
    0
    Have you added the VM with the RemoteFX vGPU to a collection?  You must do this in order for RemoteFX to function correctly and for the client that is connecting to obtain a license. 

    Don Geddes - SR Support Escalation Engineer - Remote Desktop Services - Printing and Imaging


     
  • Saturday, April 20, 2013 4:18 PM
     
     
    Sign In to Vote
    0
    Yes, the VM is in a collection and the VM is part of AD as is the host server.
     
  • Sunday, April 21, 2013 8:56 PM
     
     
    Sign In to Vote
    0
    As an update, interestingly enough, I decided to add another new Windows 8 VM to the mix and RemoteFx does work with that VM *without* it being added to the collection. However, the previous Windows 8 VM with which I'm having the licensing error message, still has the same problem. I'm puzzled by the fact that this VM did originally work with RemoteFx but then stopped.
     
  • Monday, April 22, 2013 6:47 PM
     
     
    Sign In to Vote
    0

    Another update.....

    With the Windows 8 VM that has been giving me problems I've done the following (all of which have not resolved the problem):

    - Re-installed Windows 8 doing an in-place upgrade

    - removed the VM from AD

    - removed the Collection

    - added the VM back to AD

    - added back the Collection