• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 175
  • Last Modified:

Remote Desktop from XP pc to Server 2003 Will not Connect

I have a client with a new pc running server 2003. There is a client that needs remote access to this pc. The server is not in a domain, only a workgroup. The sole purpose of this server install is to have 2 concurrent remote desktop users. The client is not at the location or in the workgroup. There is a Linksys Router acting as a DHCP server and firewall.
  I would like someone to tell me the steps to installing and enabling remote desktop on the server 2003. We have already
setup the router for port forwarding according to the remote clients protocol. I am pretty sure that remote desktop is not setup properly on the server 2003. Ther error message is "The client could not connect to the remote computer"
The client is their tech support. They feel that the problem is on our end. These guys need this store up and running asap!
Therefore, 500 points for the info that gets us honkin. Thank you to all in advance.

       Glenn
0
gpfrank
Asked:
gpfrank
  • 3
2 Solutions
 
naveedbCommented:
You can enable remote desktop on the Server by:

Start, click Control Panel, and then click System.

Click the Remote tab, click to select the Allow users to connect remotely to your computer check box, and then click OK.

http://support.microsoft.com/?kbid=814590

This will allow users who have Administrative rights on the server to connect to it.

Users who are not administrators will not be able to connect unless you install Terminal Service License, which needs to be purchased seperately from Microsoft.

If the server is behind firewall, port 3389 needs to be opened and mapped on the firewall/router and also opened on the windows firewall if it is running.

 
0
 
Rob WilliamsCommented:
A check list:
On the server:
1) Right click on My Computer and choose properties and then the remote tab. Check the box with "allow users to connect remotely to this computer"
2) You have to add an existing user or create a new and add it to the Remote Users group. Administrators are members by default.
3) If using server 2003 with SP1 there is a software firewall installed on your computer. You either need to disable it, or enable the exception for Remote Desktop. You can disable it by going to Control Panel and then Windows Firewall and check "off". Or, choose the Exception tab and then check the box for Remote Desktop to maintain the firewall but allow Remote Desktop connections.
4) If there are any other software firewalls enabled they need to be disabled or configured for remote desktop connections
3) On the firewall/router you need to enable port forwarding on TCP port 3389 to the IP address of the computer. You should assign the computer a static (fixed) IP address rather than getting one automatically from the router or a server using DHCP, as it may change from time to time and you will not be able to connect. Specific instructions for enabling port forwarding for most routers can be found at:
  http://www.portforward.com/english/routers/port_forwarding/routerindex.htm
4) Verify the port is open by logging on to http://www.canyouseeme.org from the server and testing for port 3389

If you are still having problems, try the following :
1-try connecting using the IP of the remote computer not the computer name
2-Depending on the version, on the "Terminal Services Profile" of the users profile. Make sure it is checked appropriately. "Deny the user permission to log on to any terminal server", or "Allow Logon to Terminal Server"
3-Verify the Remote Desktop User group has the rights to log on using Terminal Services. Go to Control Panel | Administrative tools | Local Security Policy | Local Policies | User Rights Assignments ...make sure Remote Desktop Users is included in "allow logon through Terminal Services"
4-The terminal Services service must be running
If you have access to the remote machine make sure it is "listening" for your connection. To do so at a command line enter (substitute port # if not using default 3389):
   netstat -an |find "3389"
You should get the following result:
   TCP 0.0.0.0:3389 0.0.0.0:0 listening
If not go to Start | Run | services.msc and see if Terminal Services is started and set to automatic

0
 
Rob WilliamsCommented:
gpfrank, was the information provided enough to get you "honkin" ? If not let us know what we can do to assist further.
--Rob
0
 
Rob WilliamsCommented:
Thanks Glenn,
--Rob
0

Featured Post

Veeam and MySQL: How to Perform Backup & Recovery

MySQL and the MariaDB variant are among the most used databases in Linux environments, and many critical applications support their data on them. Watch this recorded webinar to find out how Veeam Backup & Replication allows you to get consistent backups of MySQL databases.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now