Converted Hyper V machine - unable to RDP

[ashleymilne]

Today I used the standalone vmware converter to convert a Hyper V machine (Windows 2008R2 SP1) that was running on a physical server (Windows 2008R2) to an server running Esxi 4.0 The conversion went fine, after a few reboots I installed vmware tools, uninstalled the converter, a few more reboots to let the hardware sort itself out. This machine that I converted was a terminal server, for some reason now, I am unable to RDP into it. I can ping it on the local network, I can acces the internet from the machine and the local network. RDP is enabled, the windows event logs don't show any errors, all services that should be running are running. I am stumped. My next move will be to shut down the machine, edit the hardware, remove and add the network card.

Thoughts?

[Sree]

Hi,

    "This machine that I converted was a terminal server, for some reason now, I am unable to RDP into it. I can ping it on the local network, I can acces the

internet from the machine and the local network ".

1.Have you tried disabling the firewall in windows machine?

2.From the VM is Default gateway pingable?

3.Did you tried migrating the VM to another host and checked the same?

4.If VM is running in active-active NIC configuration,please do flip the nic's and check the same.

[ashleymilne]

1. Yes have tried disabling firewall and when I try to RDP it refuses the connection faster when the firewall is disabled.

2.Yes the default gateway is pingable from the machine.

3.I do not have another host to migrate to.

4. Not sure what you mean by active active??

[Sree]

Hi,

    Thanks for the confirmation.

4. Not sure what you mean by active active??

The port group were in VM is residing is it running on Active-Active Nic?If so identify the active(I/O) nic via esxtop screen and do flip the nic to check RDP is possible via other NIC.

1.From the Virtual machine are we able to take RDP of another VM'S which are part of same port group?

[ashleymilne]

I will check the active active, but this is a converted hyper v machine.

Yes I am able to rdp into other machines from this one, just not able to rdp into it.

[William22]

Hi

Welcome to the communities.

please check if you were using custom port for rdp instead of default port 389.

And firewall settings to allow rdp port .

"With normal actions you get normal results."

[ashleymilne]

Not using any custom ports, has always been 3389.

Firewall settings have been checked, even with windows firewall disabled it does not work.

[PatrickHoban]

On the Remote tab in System Properties select the 3rd option (if you have the 2nd selected) & click Apply. If you have the 3rd option select then select the 2nd option & click Apply. Then click the 1st option & click Apply. Now select the original option you had it set to & click Apply. Try to RDP into the server again.

Regards,

Patrick

http://patrickhoban.wordpress.com

[ashleymilne]

Thanks Patrick, that did not work though.

[PatrickHoban]

What do you see if you run netstat -nao | find "3389"

Regards,

Patrick

http://patrickhoban.wordpress.com

[ashleymilne]

Nothing, it just returns to the next line in the command prompt.

[ashleymilne]

Ok we have established that we are unable to telnet into port 3389 on the machine in question, not sure why this is or what I can do about this.

I tried changing the RDP port, still could not telnet into the changed port with the windows firewall off.

Have gone back to the Hyper V machine for now, I noticed that I had the tick mark for IPV6 ticked off on the hyper v machine, not sure if that would have made a big difference or not.

Any suggestions for converting it again, as it needs to run under Esxi, would be appreciated.

[PatrickHoban]

If you run netstat -nao you don't see anything listening on 3389? Is the Remote Desktop Services service running?

Regards,

Patrick

http://patrickhoban.wordpress.com

[ashleymilne]

Yes the service was running.

[PatrickHoban]

I knew I had this problem before but was a little off with the last thing I had you try. I found my notes on what worked for me. Try this.

1. On the Remote tab in System Properties set Remote Desktop to Do not allow connections to this computer. Click OK.
   
2. Stop all 3 Remote Desktop Services. (Remote Desktop Configuration, Remote Desktop Services, & Remote Desktop Services UserMode Port Redirector)
   
3. Start all 3.
   
4. Back on the Remote tab select Allow connection (which ever of the two you prefer).
   

Regards,

Patrick

http://patrickhoban.wordpress.com

[ashleymilne]

Patrick, tried this several times, did not work. Thanks for your suggestions.

AM

[sp4rt4n]

I know this is a old discussion, but I ran into the same issue. I've tried to convert a Hyper-V Virtual Machine running Windows Server 2008 R2 (configured as a Terminal Server) with the vCenter Converter Standalone 5.0.1 Build 875114 to a standalone ESXi 5.1 U1 Build 1157734. So far no problems while migrating and after but I wasn't able to establish a RDP connection TO this VM. VM was ping-able and I was able to establish a RDP-connection from this VM.

After some time of trying and searching, I finally foud the reason...

The configured TS-Connection was linked to the former network adapter, which wasn't present anymore. While converting, the Converter adds a new network adapter, which also got another name in the OS.

After reconfiguring the TS-Service and linking it to the new network adapter I was able to successfully establish a RDP connection to the VM.

Another workaround here would be to disable or delete the configured RDP-Connection from the TS, uninstall the network adapter and THEN convert the VM. After converting, you can rename the new network adapter to the origin name of the former network adapter and enable the configured RDP-Connection or setup a new one.

Sure, some steps of the above could be obsolete, I will try it out and edit or add my knowledge about it.

Hope this could help someone who's trying to convert a Windows Terminal Server.