Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4046
  • Last Modified:

Cannot RDP to Windows 2008 R2 Server after previously being able to do so

I have several Windows 2008 R2 servers that I can no longer connect via RDP to. I have been able to do so for several months and then suddenly midday yesterday I was no longer able to. When I attempt to connect from any workstation, the RDP client will sit at "Initiating remote connection. . ." for about 30 seconds or so and then timeout with the message

"Remote Desktop can't find the computer "computername". This might mean that "computername" does not belong to the specified network. Verify the computer name and domain that you are trying to connect to."

I have also tried connecting to the IP address of the machine but I have the same problem.

All the machines in question are Vmware VM's, however I can still RDP to some of the servers on this VMware host without issue.

I have tried turning off the firewall service in Windows on both the workstation and the server, but I am unable to connect.

I am able to both ping these servers as well as browse their file shares without issue. I did not intentionally make any changes to the RDP services on these machines.

I have tried restarting these machines but that did not resolve the issue.

I am NOT able to telnet to these servers on port 3389 either. (That was suggested as a test method in other threads I have seen on RDP issues.)

From the console of the servers with this issue, I can successfully connect a RDP session to that same server without issue.

I am not sure where to go with troubleshooting this at this point, so any assistance I could get with this would be greatly appreciated.
0
Rob Sanders
Asked:
Rob Sanders
  • 10
  • 5
  • 2
2 Solutions
 
simonseztechCommented:
Start TSConfig.msc in running command

Right Click RDP-Tcp then properties.

Look for the Network Card page then select your Network Interfaces.
0
 
Rob SandersAuthor Commented:
ok, once I am at that page what do you want me to do? The drop down menu already said:

"All network adapters configured with this protocol". I tried changing it directly to say vmxnet3 Ethernet Adapter" but it did not make a difference as I am still unable to connect via an RDP session.
0
 
simonseztechCommented:
Make sure the firewall on the allow the "Remote Desktop" on Domain /Enterprise network.

You may have to reboot. Is it a brand new VM or a Physical to Virtual Machine ?
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
John JenningsOwnerCommented:
Can you reboot the VMWare host? It sounds like something in your virtual networking changed. I would recommend taking the host down and then back up to see if that resolves the issue.

If not, you'll need to investigate the virtual networks you have in place. It sounds like some of your routing was changed.
0
 
Rob SandersAuthor Commented:
I have verified that the firewall permits the Remote Desktop application in the domain, home/work and public profiles.

I tried rebooting after making changes under RDP-TCP properties as previously suggested but it did not make a difference.

I cannot reboot the VMWare host right now but I could potentially do so this evening.

One funny thing about this is that one of the servers that is a VM that is actually in the same virtual switch, is not having this issue.
0
 
John JenningsOwnerCommented:
Perhaps you could try removing the troubled VMs from the network switch (make a new one that routes nowhere, maybe?) - shut them down, re-associate them with your existing network switch, and turn them back on?

It's rare, but I've seen issues like this with both VMWare and Hyper-V.
0
 
Rob SandersAuthor Commented:
I tried moving one of the problem servers to a different switch on the vmhost but it did not make a difference.
0
 
John JenningsOwnerCommented:
It sounds like it's time to do some tracerouting, and perhaps even some wireshark. We need to find out where those RDP packets go.

Can you ping the troubled servers and get a response?
0
 
Rob SandersAuthor Commented:
Yes, I am able to ping the servers without issue as well as browse their file shares.
0
 
Rob SandersAuthor Commented:
I am not especially familiar with using Wireshark, but I did set it up on one of my servers to test. As best as I can tell, wireshark does not see any of the RDP packets hitting the server. However, I do not have a lot of experience using Wireshark, so I could be doing something wrong with it.
0
 
Rob SandersAuthor Commented:
I have done a Wireshark capture on the server's nic and while it is capturing I attempt to connect to it from a workstation. The connection is unsuccessful. I then try to RDP to the server from the RDP client loaded on the server and the RDP session is successful. However, when I look at the wireshark capture and apply the 'rdp' filter, it does not show any activity.
0
 
John JenningsOwnerCommented:
So ping works, and SMB works... but RDP does not?

I'm inclined to go back to firewall issues at this point. If ping is working and SMB is working, then your networking is fine. There's something above it that's blocking it.

Can you console into the VMs directly from the host and check their firewalls?
0
 
Rob SandersAuthor Commented:
Firstly, let me correct my earlier post. I looked at the wireshark capture and I actually can see the workstation sending the RDP packets to the server.

Yes, I can console into the server and check the firewall settings. The firewall indicates that it is allowing remote desktop services through. I can even turn off the firewall service altogether and I still have the same problem.
0
 
Rob SandersAuthor Commented:
ok, instead of turning off the windows firewall service, I went into control panel and manually turned off the firewall. After doing so, I was able to connect. I'm going to have to investigate a little further to figure out why the existing exceptions no longer worked or what changed about them.
0
 
John JenningsOwnerCommented:
At least there's progress! It definitely seems that Windows Firewall is the culprit right now, but I'm wondering if something in the networking hiccuped, causing those servers to lose (I assume) their domain connection. Windows Firewall would default to a 'Public' network, and a tighter list of settings.

You could modify your rules to include multiple firewall scopes, such as Public and Domain, and just limit your connections by local subnet or IP range.

Let me know what you find!
0
 
Rob SandersAuthor Commented:
Well, after looking into it a little further, I have discovered in the windows firewall rules that there is for some reason some additional firewall rules that explicitly block Remote Desktop on the domain profile in addition to the conflicting firewall rule that explicitly permits remote desktop on the domain profile. I guess if there are two rules in conflict, "block" wins. I have no idea why these new rules would be there all of a sudden. Its possible a coworker but them there on accident or something. I am trying to figure out how to remove them now. I will create another question for that though.
0
 
Rob SandersAuthor Commented:
I will go ahead an close this question now. If anyone would like to assist with resolving the rest of my issue, I opened up another question thread that can be read here:

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2008/Q_27854567.html
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

  • 10
  • 5
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now