Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Cannot connect via Remote Desktop to W2K3 server

Posted on 2010-09-09
7
Medium Priority
?
857 Views
Last Modified: 2012-05-10
Running Win Server 2003 Std (x32) SP2.  Trying to connect via RDC.  I have tried via an XP SP3 client, and a W7 x64 Ultimate client - I get errors that it cannot connect.  I do have connection to the server - I am on the LAN when I do this, and I can access the shared folders on the server.  I have tried both via server name and IP address.  On the server, in System Properties->Remote Tab, "Enable Remote Desktop on this computer" is checked.  (When I click the Connect button in the RDC client, I can't even get to the point to enter a username/password.)  IPv6 is not running on the server or on either of the above clients.  Terminal Services is not installed on the server.  I don't see any errors in the logs on the server.  Firewalls are off on all computers.

Any suggestions here as to what to try next?  Thanks for any assistance.
0
Comment
Question by:cgtyoder
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
7 Comments
 
LVL 9

Expert Comment

by:esmith69
ID: 33640341
You may need to simply reboot the server.  I have seen a couple of instances where the terminal server service (the one responsible for RDP requests) simply fails to respond properly to incoming requests.  Unfortunately, MS won't let you manually start/stop/restart that particular service.  You have to reboot the server to cycle it.

I would definitely try that if possible.  It sounds like you've already done everything else that I was going to suggest (verify all firewalls are turned off, check the event logs for related errors, try connecting with IP address instead of just DNS name).

0
 
LVL 3

Expert Comment

by:chris-burns
ID: 33640434
what happens if you telnet into the server on 3389???


c:>telnet IPADDRESS 3389

do you get a blank screen?
0
 
LVL 8

Expert Comment

by:ConUladh
ID: 33640509
Launch gpedit.msc on target machine

Local Computer Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Deny Log on through remote desktop service

Make sure thats empty

There's a few other policies in there that might be relevant as well
0
Industry Leaders: 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!

 
LVL 9

Expert Comment

by:esmith69
ID: 33640557
If it were a policy issue, he most likely would have received at least the logon screen.  Since he's not even making it that far, I don't think that's going to have an effect.  Certainly wouldn't hurt to double check though.

You can double check the following registry key to make sure that it's set properly:  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\fDenyTSConnections

it should be set to 0, and if you have to change it from 1 to 0, you'll need to reboot for the change to take effect.
0
 

Accepted Solution

by:
cgtyoder earned 0 total points
ID: 33640593
I am such an idiot.  Just figured it out.  Totally forgot I changed the RDC port a long time ago.  Working now.
0
 
LVL 3

Expert Comment

by:Bogeholm
ID: 33640608
Hi,

Test 1)
To check if the server is actually listening for this type of traffic - open a command prompt and do a:
netstat -a | findstr "3389"

This should output something like:
TCP myserver:3389 myserver.mydomain.com:0 LISTENING

If it is not listening, the server configration is not correct - or you are expierincing some server defect

Test 2)
Next try to telnet the port from the XP client (W7 doesn't have telnet) - open a command prompt and do a:
Telnet <server-ip> 3389

If the test is successful you will get a blank window with a blinking cursor i the top left hand corner.
If it fails, something in the network is blocking.
You state that there are no firewall(s) in the network path. What about security software? Antivirus and similar could block a port.

Please let me know how far the above get you


-M


0
 
LVL 3

Expert Comment

by:chris-burns
ID: 33640755
Well that will do it :-)
0

Featured Post

Back Up Your Microsoft Windows Server®

Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article, I'll explain how to setup a Plex Media Server (https://plex.tv/) on a Redhat (Centos) 7 based NAS with screenshots to help those looking for assistance.  What is Plex? If you aren't familiar with Plex, it’s a DLNA media serv…
Like many organizations, your foray into cloud computing may have started with an ancillary or security service, like email spam and virus protection. For some, the first or second step into the cloud was moving email off-premise. For others, a clou…
How to install and configure Citrix XenApp 6.5 - Part 1. In this video tutorial we have explained step by step installation of Citrix XenApp 6.5 Server on Windows Server 2008 R2 is explained in this video. We have explained the difference between…
Want to learn how to record your desktop screen without having to use an outside camera. Click on this video and learn how to use the cool google extension called "Screencastify"! Step 1: Open a new google tab Step 2: Go to the left hand upper corn…

721 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question