Jonjon2013
asked on
RDP ISSUE. This computer can't connect to the remote computer
I'm having a very frustrating issue that makes little sense. I have a Windows server 2008 R2 that I can't remote into at all. Every time I try to a access I get the message:
"This computer can't connect to the remote computer"
This is what I've tried to no avail.
1. Turned off then back on "Allow remote connection" in remote settings
2. Turn on and off NTLM option
3, turned firewall off
4. Confirm port number in terminal server registry is 3389
5. Ran netstat -a -o to view and confirm its listening on that port
6. View task list to make sure termservice is the service listening on that port.
7. Uninstalled Symantec. The ONLY thing installed on this server is Exchange 2016 with its services shutdown for now.
8. Confirm The "fDenyTSConnections" registry sword is set to: 0
9. I can also successfully telnet into 3389 on that box.
Nothing. I can PING the server just fine. I'm trying all of this from a computer on the same subnet. With an enterprise admin account. Anybody had this before? Please help!
"This computer can't connect to the remote computer"
This is what I've tried to no avail.
1. Turned off then back on "Allow remote connection" in remote settings
2. Turn on and off NTLM option
3, turned firewall off
4. Confirm port number in terminal server registry is 3389
5. Ran netstat -a -o to view and confirm its listening on that port
6. View task list to make sure termservice is the service listening on that port.
7. Uninstalled Symantec. The ONLY thing installed on this server is Exchange 2016 with its services shutdown for now.
8. Confirm The "fDenyTSConnections" registry sword is set to: 0
9. I can also successfully telnet into 3389 on that box.
Nothing. I can PING the server just fine. I'm trying all of this from a computer on the same subnet. With an enterprise admin account. Anybody had this before? Please help!
Last Comment
ASKER
What are FW profiles? Are you referring to the Windows firewall area? Yes that's turned off already and have checked it in the local security policy.
Is this from just one PC or from all PC's on the same LAN?....
ASKER
The issue is affecting just this 1 server. The inability to connect is consistent from all PCs in the LAN to this 1 server.
You have been very thorough so far on your troubleshooting....
On the server itself can you run the following and post the output.
netsh int ipv4 show int
Thanks
On the server itself can you run the following and post the output.
netsh int ipv4 show int
Thanks
ASKER
Yes. Attached is the output of netsh int ipv4 show int
ASKER
I don't see any problems there.
Is this a virtual server?
If it is then consider removing the vNIC and replacing (should be VMXNET3 but if it is already try changing to E1000 for testing purposes). Alternatively build another temporary server as a test to see if this also has issues...
If its physical, can you confirm all of the hardware firmware levels are up to date
Is this a virtual server?
If it is then consider removing the vNIC and replacing (should be VMXNET3 but if it is already try changing to E1000 for testing purposes). Alternatively build another temporary server as a test to see if this also has issues...
If its physical, can you confirm all of the hardware firmware levels are up to date
ASKER
Yes it's virtual but I don't think it's a VMware issue because we have many VM'a on the same box using the same NICS with zero problems. The only difference is that the problematic server is running Windows 2012 while the working servers are running 2008.
Yes It is VMXNET3 like the rest of them. Unfortunately I can't replace the vNIC to E1000 just for testing. I would have to get another department involved whom will give me grief because all signs point to OS since the other vm's are working.
Yes It is VMXNET3 like the rest of them. Unfortunately I can't replace the vNIC to E1000 just for testing. I would have to get another department involved whom will give me grief because all signs point to OS since the other vm's are working.
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
That's one for the knowledge base - glad its working for you!
ASKER
Found the solution.
Exchange
Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.
213K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
Try to edit secpol.msc and disable all the FW profiles.