djhunt01
asked on
RDP Not Working on Virtualized 2008 R2 Server Running on Hyper-V R3
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
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
Haresh Nikumbh
Are you able to ping VM from Win7 machine?
ASKER
Hi! Thank you for your response. Yes, we're able to ping the VM from the Win 7 machine.
Doug
Doug
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.
I assume this was configured before but the NIC and firewall would have been reconfigured by the hyper-V integration tools when migrated.
ASKER
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
The firewall is and has been disabled. Any other suggestions would be welcome!
Thank you and take care!
Doug
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.
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.
ASKER
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
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
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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
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
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
Cheers!
--Rob