locked
Remote Desktop hangs on imported virtual machines RRS feed

  • Question

  • Hi

    I am surprised I have not seen this error before, since I can reproduce it very easily.

    I have two win2008R2 servers on a small network I am setting up for Active/directory - SharePoint. It is very strange that if I create a virtual machine with win2008R2 fresh, I am indeed able to connect to it with Remote Desktop. Whilst if I connect to the one that is exported and then imported then it just hangs on welcome message followed by message saying:-

    Please wait for the User Profile Service...

    It never connects.

    I can however, connect with the physical server through Hyper-V and there does not seem to be any issues.

    The port 3389 for remote desktop is open for the server IP address on the router.

    Any ideas will be a great help as the whole idea behind working with virtual servers rather than real servers is the ability to move the virtual servers from one machine to another. Development must be transportable rather than starting all over again.

    Salar

     


    www.salaro.com
    Tuesday, August 24, 2010 12:13 AM

Answers

  • Thank you Brian

    I have not reached the point where I have to set-up now a simple Active Directory on a virtual server in the same network. Both of these hyper-v servers are purely for development and not for real world hosting.

     

    On above I did manage to find a solution. It looks that it is a bug in Hyper-v

    http://itsolutionsdirect.com/slow-rdp-performance-on-a-server-2008-r2-hyper-v-host/253/

    explains it well and it does work. 

     

    However, now I have another issue to solve. whilst the virtual machines are now visible over the web via http/Remote desktop and  the rest, but the physical pcs are only visible on Remote desktop within the firewall.

    So if I want to remote access the physical servers from outside the network, I have to first remote access a virtual server in hyper-v, and then to again Remote Desktop Connect through the virtual machine RDC.

    This is very strange, I have switched firewall on both the server as well as the router. 

    I still cannot RDC the Physical Servers.

    Any ideas is very much appreciated as I dont have a good keyword for Google Searching this subject.

    Salar


    www.salaro.com
    • Marked as answer by salaroo Tuesday, August 24, 2010 7:08 PM
    Tuesday, August 24, 2010 7:07 PM

All replies

  • Have you double checked the virtual network settings of the VM after the Import?

    I frequently see cases where an Export and the resulting Import need to have the virtual network attachment reset.

    This type of behavior would be consistent with what you are seeing as the user profile service attempts to contact Active Directory and if it cannot it will hang for a very long time waiting for the timeout value to be reached before loading a default profile (last resort).

     


    Brian Ehlert (hopefully you have found this useful) http://ITProctology.blogspot.com
    Tuesday, August 24, 2010 2:48 PM
  • Thank you Brian

    I have not reached the point where I have to set-up now a simple Active Directory on a virtual server in the same network. Both of these hyper-v servers are purely for development and not for real world hosting.

     

    On above I did manage to find a solution. It looks that it is a bug in Hyper-v

    http://itsolutionsdirect.com/slow-rdp-performance-on-a-server-2008-r2-hyper-v-host/253/

    explains it well and it does work. 

     

    However, now I have another issue to solve. whilst the virtual machines are now visible over the web via http/Remote desktop and  the rest, but the physical pcs are only visible on Remote desktop within the firewall.

    So if I want to remote access the physical servers from outside the network, I have to first remote access a virtual server in hyper-v, and then to again Remote Desktop Connect through the virtual machine RDC.

    This is very strange, I have switched firewall on both the server as well as the router. 

    I still cannot RDC the Physical Servers.

    Any ideas is very much appreciated as I dont have a good keyword for Google Searching this subject.

    Salar


    www.salaro.com
    • Marked as answer by salaroo Tuesday, August 24, 2010 7:08 PM
    Tuesday, August 24, 2010 7:07 PM
  • The slow RDP performance issue is a really old one that I have responded to in the forums for a really long time now (since the origional Beta of Hyper-V).

    This is technically not a Hyper-V problem but a NIC driver problem that goes back to the NIC manufacturer - and the problem has been around snice the days of NT4 as well as the first 3Com NICs that supported offloading.

     


    Brian Ehlert (hopefully you have found this useful) http://ITProctology.blogspot.com
    Tuesday, August 24, 2010 7:30 PM