cgtyoder
asked on
Cannot connect via Remote Desktop to W2K3 server
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.
Any suggestions here as to what to try next? Thanks for any assistance.
what happens if you telnet into the server on 3389???
c:>telnet IPADDRESS 3389
do you get a blank screen?
c:>telnet IPADDRESS 3389
do you get a blank screen?
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
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
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\
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.
You can double check the following registry key to make sure that it's set properly: HKEY_LOCAL_MACHINE\SYSTEM\
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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
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
Well that will do 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).