Home > Windows Server > Windows Server 2003 Remote Desktop Connection Not Working

Windows Server 2003 Remote Desktop Connection Not Working


This mystified me until Google later helped me find the answer. It also tells me that the "outside" NIC at 206.xxx.xxx.xxx:yyyy may not be the problem. As soon as I setup and"start""Remote Access and Routing," I lose my RDP connection; however once I have the "tunnel," I can create an RDP connection using internal addressing (NetBios name 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 his comment is here

The update took place and gave me a reboot message. I got the "credentials" message, then the can not connect-- contact your network administrator message after that. 'Tis a puzzlement. Browse other questions tagged windows-server-2003 windows-server-2008 remote-desktop or ask your own question. 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.

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

But confirming that the port is open is only half of the battle. asked 7 years ago viewed 28073 times active 3 years ago Blog How We Make Money at Stack Overflow: 2016 Edition Stack Overflow Podcast #94 - We Don't Care If Bret I have a port-forwarding in the NAT settings. Figure 7: Limit Number of Connections setting (click to enlarge) Figure 8: RDP-TCP Properties setting Both of these settings help configure the number of simultaneous connections allowed for a connection.

  1. I don't mind checking again, guess I'm looking for direction from "another pair of eyes".
  2. You have to right click on "Device Manager" and select "Show hidden devices" for it to show up.
  3. So I'm back to the drawing board.
  4. However they are still needed for an old estimating program so I have to keep them up for a little while longer.
  5. Both types of connections were working, now neither is.
  6. I use dameware mini remote ~$100 per admin there are 100's of other Remote clients that work as well.
  7. or should I give it a try during Off working Hrs. @stu I have tried different NIC also with No luck..
  8. Loading a desktop initially on the workstations seemed slow, but once up, workstations seemed "normal".
  9. 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.
  10. No changes have been made other than an automatic security update.

The device is TDTCP and tdtcp.sys failed to load. wedor, Sep 20, 2009 #12 Sponsor This thread has been Locked and is not open to further replies. Can you please confirm if the issue is resolved? Rdp This Computer Can't Connect To The Remote Computer share|improve this answer answered Jun 28 '09 at 21:28 Le Comte du Merde-fou 9,34811427 Hmm, I'm going to have to try this.

Advertisement Recent Posts Recovery drive full DaveA replied Nov 16, 2016 at 11:55 AM Word Association dotty999 replied Nov 16, 2016 at 11:53 AM A -W inside Schools Gr3iz replied Nov can you please also check the Remote Desktops firewall exception setting? Remote connections might not be enabled or the computer might be too busy to accept new connections. In Terminal ServicesConfiguration\ Connections, deleted"RDP-TCP" and then created a new connection using defaults Rebooted server Attempted to restore an older version of the terminal server key in the registry by exporting

Users can browse shares but not RDP. Remote Desktop Connection Windows Server 2003 To diagnose this problem, you not only want to check whether the default RDP port (3389) is blocked; you also want to make sure that it's being used by the appropriate It turns out that the server begins to shut down various services including the service that handles RDP connections however the server hangs before it actually stops all services - so 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...

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

I was afraid to make changes as settings previously worked for such a long time. I need NAT to have TCP port forwarding to Workstation IP - Those settings are correct. This Computer Can't Connect To The Remote Computer Server 2003 Marked as answer by 4ndrew Monday, June 28, 2010 9:49 PM Monday, June 28, 2010 9:49 PM Reply | Quote 0 Sign in to vote We usually assume that the server Rdp Not Working Server 2008 Please ensure the firewall does not block the port traffic.

Based on our experience and trends we've seen, we've put together a cheat sheet of the most common causes of these problems: ·         Misunderstood terminologies and settings ·         Incorrect permissions and\or this content Any suggestions or tips that lead me to a resolution are greatly appreciated! Click OK. I tried SFC /scannow and it din't work. Windows Server 2003 Remote Desktop Connection Limit

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? Regards, Lionel ChenThis posting is provided "AS IS" with no warranties, and confers no rights. I cannot tell you which update exactly to blame couse I dont remember but it is documented. weblink Suggestions on what I should be testing/checking/changing would be much appreciated.

Privacy statement  © 2016 Microsoft. The Client Could Not Connect To The Remote Computer But this problem is still bothering me. Thanks for letting me know.

If he has it in Terminal Server mode, this would allow the connection screen up and then give a Windows error about licensing. –Matt Jun 29 '09 at 2:46 add a

Related Reading: Top 10: Remote Desktop Keyboard Shortcuts Enable Remote Desktop Over a Network On Demand Print reprints Favorite EMAIL Tweet Please Log In or Register to post comments. DHCP is running on server, each workstation has reserved internal IP from this server based on MAC. I also toggled "Allow remote connection" off and on as well as re-activated Terminal license server 0 Habanero OP B-C Apr 18, 2013 at 4:38 UTC   clamberth Windows Server 2012 Remote Desktop Not Working It was used for the occasional after-hours backup job check, a peek at Virus Vault, or to see if a connection was happening if the owner/manager called when they could not

I deleted existing rdp connection and created new one but the same thing is happening. Marked as answer by Wilson Jia Thursday, September 02, 2010 8:22 AM Tuesday, August 10, 2010 11:07 AM Reply | Quote 0 Sign in to vote Hi Amir, How are you? Regards, Wilson JiaThis posting is provided "AS IS" with no warranties, and confers no rights. http://powerglobaldesigns.com/windows-server/windows-server-2003-unc-not-working.html Out of the box, Remote Desktop supports two concurrent connections to remotely administer a computer.

I know you already mentioned changing the registry for the port value but I thought I send it anyway. I have tried to rdp to the problem server from several different 2003 servers as well as windows xp desktops. How can I troubleshoot Bluetooth detection and connectivity problems in Windows XP Service Pack 2? If the RD Session Host role service is installed on a DC, the security settings of the DC will need to be adjusted to allow users to have remote access to

or to the workstations? Have you guys hadany problem just like this, ever? Our box when running in Server Administrator mode, just outright doesn't let you connect. Note that Remote Desktop Licensing (RD Licensing)—formerly Terminal Services Licensing (TS Licensing)—is a role service in the Remote Desktop Services server role included with Windows Server 2008 R2.

mattsonberg replied Nov 16, 2016 at 11:51 AM Loading... I haven't been able to sort out what's causing it. Unfortunately I can't remember which specific one it was; I've checked and it does seem that this happens occasionaly with different patches. Logon as administrator, click Start -> Run, type "rsop.msc" in the text box, and click OK.

I did not think of restarting more than once. As always, our ISA server has two interfaces, for the internet and the internal LAN. Beyond that things have been stable and working well. Any assistance would be greatly appreciated.

Suppose you have three administrators in your IT team.