Home > Connect To > Win 2003 Rdp Not Working

Win 2003 Rdp Not Working


I updated the video driver on the remote desktop host (not client), and after doing so, it allowed remote connections in. Our box when running in Server Administrator mode, just outright doesn't let you connect. Vinman, Sep 16, 2009 #7 wedor Joined: Nov 7, 1999 Messages: 4,504 There was an issue a while back related the video drivers on some systems creating symptoms like that, do To allow remote access to the RD Session Host server for users who aren't members of the Administrators group, you should grant the Remote Desktop Users group the Allow log on http://nadrp.com/connect-to/win-2003-remote-desktop-not-working.html

This is a file server.I must admit that i didn't try to connect remotely to my FS before enabling Routing & Remote Access. I have a similar issue to the poster but this hadn't even registered in our radar! –Mark Henderson♦ Jun 28 '09 at 21:36 add a comment| Your Answer draft saved dBforumsoffers community insight on everything from ASP to Oracle, and get the latest news from Data Center Knowledge. The update took place and gave me a reboot message.

This Computer Can't Connect To The Remote Computer Server 2003

Should I change either of these? By creating an account, you're agreeing to our Terms of Use and our Privacy Policy Not a member? Advertisement Vinman Thread Starter Joined: Feb 19, 2005 Messages: 10 Windows Server 2003 SP2 Enterprise Edition Had RDP up and running for well over a year now.

  2. Solved: Server 2003-RDP suddenly stopped working Discussion in 'Windows Server' started by Vinman, Sep 9, 2009.
  3. Text Quote Post |Replace Attachment Add link Text to display: Where should this link go?
  4. Also, any Client PC can connect via RD to any other Client PC, even the Server can connect to any Client PC.

Join our site today to ask your question. http://forums.techarena.in/windows-server-help/541656.htm 0 Poblano OP Hakim Hakimji Oct 17, 2012 at 9:48 UTC @stu I've tried this my dear. It looks like it might, but nothing ever comes up. Rdp Tcp Properties Network Adapter Hangs Here's a quick test that uses the Netstat and Tasklist commands, which you run on the server that you're trying to connect to remotely: C:\Users\Administrator.CONTOSOONE>netstat -a -o Active Connections Proto Local

even i tried netsh command to see if this port is listening or not.. Rdp Not Working Server 2008 I may be wrong but......I am sure by default Win 2K3 will only accept 2 Remote connectionsCheck the "Users" Tab in "Task Manager" to ensure that there are no allocated but you configure routing and remote access?Admin tools Routing and Remote Access. 0Votes Share Flag Collapse - No by Diego · 10 years ago In reply to Did I don't believe that https://support.microsoft.com/en-us/kb/2477023 share|improve this answer edited Jun 27 '09 at 18:18 answered Jun 27 '09 at 18:12 David Spillett 20.1k2658 add a comment| up vote 2 down vote Out of Remote Desktop/Terminal Server

It is an HP and has that stupid "HP Network Configuration Utility 7" in the NIC stack. Unable To Rdp To Server 2012 The "Terminal Services Session Directory" is set to disabled. ipconfig /all shows those on each station and on server are correct. Tech Support Guy is completely free -- paid for by advertisers and donations.

Rdp Not Working Server 2008

There could be legitimate reasons for reassigning the default RDP port to a different application, but then you need to determine which port is assigned to RDP. https://community.spiceworks.com/topic/268257-remote-desktop-in-server-2003-not-working C:>telnet -a ServerName 3389 Connecting To ServerName...Could not open connection to the host, on port 3389: Connect failed C:>telnet -a 3389 Connecting To not open connection to the host, This Computer Can't Connect To The Remote Computer Server 2003 Or is it inevitable once a certain point in development is reached? This Computer Can't Connect To The Remote Computer Server 2008 and though you've probably done it already, a chkdsk /f has resolved odd problems like this.  Of course, I trust you have a working backup. . .

I haven't been able to sort out what's causing it. If telnet succeeds, then it's security related- GPO?   0 Jalapeno OP spacewalker Mar 19, 2012 at 2:28 UTC Brian - The "Terminal Services" service is Started and Message that users get when trying to remote desktop toa Windows 2003 R2 server: "The client could not connect to the remote computer. Both types of connections were working, now neither is. The Client Could Not Connect To The Remote Computer

I need NAT to have the ports for RDP open - Those settings are correct. When I tried to connect to it, there was no timeout, and no other reaction. Also the sfc /scannow does not do anything. this content After that everything works.nikki Tuesday, October 26, 2010 2:59 PM Reply | Quote Microsoft is conducting an online survey to understand your opinion of the Technet Web site.

TECHNOLOGY IN THIS DISCUSSION Dell 120198 Followers Follow Microsoft Windows Server 2003 Remote Administrator Join the Community! Rdp This Computer Can't Connect To The Remote Computer Should I change either of these? 0 Jalapeno OP spacewalker Mar 19, 2012 at 2:29 UTC Hi Joe - I can ping the server. 0 JoinAFCOMfor the best data centerinsights.

Your continued help has been great.

This service, although it is set to Manual, will start if Remote Desktop for Administration is enabled. By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. I also toggled "Allow remote connection" off and on as well as re-activated Terminal license server Using RDP to work not just for administration. Windows 2003 Rdp Service Thanks.

This box of yours Dell/HP/Virtual?     0 Habanero OP B-C Apr 18, 2013 at 4:40 UTC probably best to start a new question referencing this thread... Figure 2: Enabling a Remote Desktop Connection Another common misunderstanding involves knowing what permissions are necessary to allow a user to log on to a remote computer. So I'm back to the drawing board. I made sure RD is enabled on the server by going to the Remote tab of the System Properties Control panel and making sure allow remote desktop is checked off, I

Check that any other firewall you have in place has a hole in it for rdp. It might be worth your while checking to see if you had a patch update just before the RDP failed and then remove them to see if that fixes the issue It is also possible that network problems are preventing your connection" Remote desktop is enabled (system control panel, remote tab) Proposed as answer by dannybui Thursday, December 19, Loading a desktop initially on the workstations seemed slow, but once up, workstations seemed "normal".

That did it! Email Reset Password Cancel Need to recover your Spiceworks IT Desktop password? Join Now Our Windows 2003 File Server will no longer allow RDP it seems.  I can RDP to our other servers, but no longer into this box. C:\Users\Administrator.CONTOSOONE>tasklist /svc | findstr "2252" Image Name PID Services svchost.exe 2252 TermService These results tell you that the port is being used by the right service (Termservice, in this case).

Remote connections might not be enabled or the computer might be too busy to accept new connections. JING also allows for some markup (arrows, boxes, text boxes, highlighting, and up to 5 minutes of video with sound.) 0 Datil OP Brian_Noga Mar 19, 2012 at So try restart couple of times. Do i have to restart the machine after sfc or no need.

quick search of community turns up this post  (Would try that before crapping an install) 0 Sonora OP clamberth Apr 18, 2013 at 4:34 UTC I'm having the RDP from where to where? Trigg Gayle - Thanks for the link straight into the registry to find the listening port.  That turned out to be the key!  (Sorry Joe925 - I'd have found this on Friday, June 18, 2010 4:43 PM Reply | Quote 0 Sign in to vote "Terminal Services" is started on the server that has the problem The windows firewall is off on

I need NAT to allow RDP to server for the above user, That port is listed. The first thing I noticed is that PING -t continued to get responses which meant that the server was not going down at all.