Solved

RDP Not Working on Virtualized 2008 R2 Server Running on Hyper-V R3

Posted on 2013-05-30
9
871 Views
Last Modified: 2016-11-23
Greetings!

We have a virtualized Terminal Server running Windows Server 2008 R2, which has been working perfectly well under VMWare 5.0.  We converted it using the free 9 five V to V utility to run under Hyper-V.  The host we are running the converted VM on is a Dell PowerEdge 2950 with Server 2012 Datacenter installed.

The converted VM is running on the Hyper-V host, and has Internet connectivity and access to shared files on other servers on our domain.  The only thing that isn't working properly is the ability to RDP into the server.  The server is setup to listen for RDP on port 3394, and we verified that setting in the registry.  The firewall is off.  When trying to connect from a Windows 7 RDP Client the connection times out.

The 2950 has two Broadcom Netxtreme II NICs.  NIC teaming is not turned on, and one of the NICs is bound to Hyper-V.

From what we've researched this is probably an issue with the virtual NIC configuration, but we would appreciate guidance on next steps to try.

Thank you in advance for your help!

Doug
0
Comment
Question by:djhunt01
  • 4
  • 4
9 Comments
 
LVL 22

Expert Comment

by:Haresh Nikumbh
ID: 39208319
Are you able to ping VM from Win7 machine?
0
 

Author Comment

by:djhunt01
ID: 39208489
Hi!  Thank you for your response.  Yes, we're able to ping the VM from the Win 7 machine.

Doug
0
 
LVL 77

Expert Comment

by:Rob Williams
ID: 39208859
The windows firewall will by default create a firewall exception for remote access when enabled, however this will default to port 3389.  3394 will be blocked unless you create the rule manually.  Perhaps try disabling the firewall all together as a test.

I assume this was configured before but the NIC and firewall would have been reconfigured by the hyper-V integration tools when migrated.
0
 

Author Comment

by:djhunt01
ID: 39208982
Hi Rob!  Thank you for your input.

The firewall is and has been disabled.  Any other suggestions would be welcome!

Thank you and take care!

Doug
0
Better Security Awareness With Threat Intelligence

See how one of the leading financial services organizations uses Recorded Future as part of a holistic threat intelligence program to promote security awareness and proactively and efficiently identify threats.

 
LVL 77

Expert Comment

by:Rob Williams
ID: 39209151
My apologies, in re-reading I see you already stated; "The firewall is off."

Have you verified the server is listening as it should on the correct port using
netstat -an |find "3394"
It should return:
TCP    0.0.0.0:3394           0.0.0.0:0              LISTENING

You could also try telneting from another station to verify it is accessible
telnet <IP> 3394
Which should return a flashing cursor and blank window.  An error or timing out would indicate a connection issue if it is listening above.
0
 

Author Comment

by:djhunt01
ID: 39209246
Hi Rob!  Thank you for continuing on this adventure.

Netstat did not show port 3394.  However, I think we're narrowing down the problem.  If I go into the settings for the local area network connection, it shows the static address we set of 192.168.0.26.  However, if we do an IP config it shows an APIPA address as well as 192.168.0.26.  Is there a mapping somewhere involving a virtual NIC that we should be checking?

Also, we can access the machine by installing VNC on it.

Thank you and take care!

Doug
Network-Connection-Details-Scree.jpg
0
 
LVL 77

Accepted Solution

by:
Rob Williams earned 500 total points
ID: 39209279
Check under the properties of the network adapter, Internet Protocol Ver 4 (TCP/IPv4) properties, that the static IP is configured under the general tab and not the "alternate configuration tab".

It looks as if DHCP (Obtain an address automatically) is configured under general and static under alternate.  That will not work.
0
 

Author Comment

by:djhunt01
ID: 39209351
Hi Rob!

That was almost it...It was actually the other way around, which is interesting.  I think the conversion process from VMWare provided us some "gifts".

I can't thank you enough for your help with this.

Take care!

Doug
0
 
LVL 77

Expert Comment

by:Rob Williams
ID: 39209398
Glad to hear you were able to resolve.  It is often recommended to remove NIC's or convert them temporarily to loopback adapters when converting or cloning.  I suspect this is one reason why.

Cheers!
--Rob
0

Featured Post

How to improve team productivity

Quip adds documents, spreadsheets, and tasklists to your Slack experience
- Elevate ideas to Quip docs
- Share Quip docs in Slack
- Get notified of changes to your docs
- Available on iOS/Android/Desktop/Web
- Online/Offline

Join & Write a Comment

First I will try to share a design of a Veeam Backup Infrastructure without Direct NFS Access backup. Note: Direct NFS Access backup transport mechanism is only available in Veeam v9 In above I try to design the Veeam Backup flow between i…
Resolve DNS query failed errors for Exchange
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

746 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now