asked 6 years ago viewed 23481 times active 6 years ago Blog Stack Overflow Podcast #94 - We Don't Care If Bret Is Famous Stack Overflow Job Search: Better, Faster, Stronger Browse other questions tagged networking firewall remote-desktop windows-server-2008-r2 rdp or ask your own question. The goal is to help you identify these problems before calling the Microsoft support team or hitting the search engine. You still need to make sure that the right service is using that port. have a peek here
reply Fix for Can't RDP into 2008 R2 or Windows 7 after Update 2667402 Permalink Submitted by Dave (not verified) on Mon, 09/23/2013 - 11:47pm. From this machine i can RDP to other machines, but from other system i cannot login to this system reply There are links to the Permalink Submitted by ingram on Mon, I also just tested RDP from the 2008 server to my XP SP3 workstation and it works fine. I have followed the same process.
I feel as though this must be a firewall issue but when I turn off all firewalls for testing the same symptoms occur. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.Would you like to participate? However, I am using RDP client v.6.0.6001.18000.
Windows Server 2016 Class Windows Server 2016 Deep Dive with John Savill Live Online Training on November 29th and December 6th Register by November 22ndand Save 20%! The Remote Desktop Services is stopped, and everytime you enable it, it crashes. reply Remote Desktop Stopped working Permalink Submitted by Don (not verified) on Thu, 08/07/2014 - 6:47am. This Computer Can't Connect To The Remote Computer Server 2012 You use Remote Desktop Licensing Manager (RD Licensing Manager) to install, issue, and track the availability of RDS CALs on a Remote Desktop license server.
How can I troubleshoot Bluetooth detection and connectivity problems in Windows XP Service Pack 2? Rdp This Computer Can't Connect To The Remote Computer Delivered Daily Subscribe Best of the Week Our editors highlight the TechRepublic articles, galleries, and videos that you absolutely cannot miss to stay current on the latest IT news, innovations, and This didn't have any noticible effect. Just remember to decline it in WSUS else it will reinstall it.
Join the community Back I agree Powerful tools you need, all for free. This Computer Can't Connect To The Remote Computer Server 2003 I have now disabled the firewall for all 3 networks and have even stopped the Windows Firewall service. share|improve this answer edited Jun 27 '09 at 19:20 answered Jun 27 '09 at 19:13 squillman 33.4k870127 add a comment| up vote 1 down vote I had a desktop (WinXP) on RDP not listening for connections   22 Replies Cayenne OP BoS Jun 14, 2013 at 7:05 UTC What happens when you try to RDP?
up vote 4 down vote favorite 1 What are the most common things that will cause a Windows Server 2003/2008 to stop responding to Remote Desktop connections, even though other services Figure 5: Missing membership to the Remote Desktop Users group Port Assignments Another common scenario we come across is port blocking and/or port assignment conflict. This Computer Can't Connect To The Remote Computer Server 2008 Out of the box, Remote Desktop supports two concurrent connections to remotely administer a computer. This Computer Can't Connect To The Remote Computer Server 2008 R2 I'll get the updated client and try again.
reply Try repairing the update or Permalink Submitted by ingram on Fri, 06/29/2012 - 6:30pm. navigate here share|improve this answer answered Jun 27 '09 at 19:18 Eddie 7,99472946 add a comment| up vote 1 down vote Volume Shadow Copy, believe it or not. If port 3389 isn't listed, the server isn't listening on that port (possibly due to a host-based firewall or another ACL mechanism on the host machine that prevents the usage of Remote Desktop can’t connect to the remote computer for one of these reasons: 1) Remote access to the server is not enabled 2) The remote computer is turned off 3) The This Computer Can't Connect To The Remote Computer Windows 7
On the start menu right click on computer and choose properties. The server is a Dell Poweredge T310 with a Broadcom BCM5716C NetXtreme II GigE NIC. 0 Cayenne OP BoS Jun 14, 2013 at 7:41 UTC TSTSGreg wrote: That goodbye logmein, thanks for the info. Check This Out Are you receiving the specific error code listed above?
So, you grab the Process ID (PID) number from the results and run Tasklist while grep’ing for PID 2252. Because Of A Security Error The Client Could Not Connect To The Remote Computer Powered by Livefyre Add your Comment Editor's Picks 10 ways to advance your IT career Stop work from taking over our lives The many benefits of a formal IT communications plan reply RDP Issue Permalink Submitted by Varma (not verified) on Fri, 08/03/2012 - 8:52am.
Update #2: The same thing happens when I navigate to the default administrative share on the R710 server. Full Bio Contact See all of Rick's content Google+ RickVanover × Full Bio Rick Vanover is a software strategy specialist for Veeam Software, based in Columbus, Ohio. These solutions would be fine but for the fact that I get an "unknown error" message when I try to uninstall the old version of the update. This Computer Can't Connect To The Remote Computer Server 2012 R2 The RDP is not just working.
I have several boxes at different Customer sites, Win2003 32-bit and 64-bit, that on roughly 3 out of 10 boots don't listen for RDP. Have you actually checked if the host is listening on port 3389? (run netstat -a from the command prompt and see if the port 3389 is listed? 0 I had this happen on older servers when all the available RDP sessions were in use, but rebooting should have cleared those. 2 Jalapeno OP Drew5356 Sep 17, this contact form If it is, just alter your RDP login or change it back to the default 3389. Thanks, A.J. 1 Sonora OP Dexter_Slab Oct 17, 2012 at 8:39 UTC
Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the I can't find the patches mention above, netstat-a shows the Terminal service port 3389 listening, What could be problem? Not sure if this applies, but I had a similar problem last year. I had to log into the console, then using the RDP Manager, log off/terminate all the open sessions, There was a specific app to uninstall the Mcafee completely.