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

RDP to Windows XP in company-network not possible

Hallo,
I have a problem with the setup of Remote Desktop for a Client PC on our company-network. It's like this: Windows Server 2003 gives fixed IP to XP Client (SP 3). The firewall forwards the port (mine 3386) to the Client-IP. On the Client, I have enabled RDP, added some users and changed the RDP port to 3386 in registry.

The error is not very helpful: "This computer can't connect to the remote copmuter. Try connecting again. If the problem continues ..."

Any idea what could be the problem? Do I need to enable/install something on the Server? Thanks in advance for your help.
0
skiaholic
Asked:
skiaholic
  • 4
  • 2
1 Solution
 
John JenningsOwnerCommented:
Are you trying to connect FROM XP to Server 2003?

If so, have you enabled Remote Desktop on Server 2003?
0
 
wolfcamelCommented:
first confirm you can rdp to it, on that port, from another PC locally - this will eliminate any router issues. and confirm your reg changes worked
0
 
skiaholicAuthor Commented:
I'm trying to connect from another XP client to the XP client with RDP enabled.
On Server 2003 RDP is enabled also and works.
0
Cloud Class® Course: CompTIA Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

 
John JenningsOwnerCommented:
On the client machine that you want to connect to, is Windows Firewall enabled?
If so, did you make an exception for port 3386?

Also, is this an internal-to-internal RDP connection? Are you going over the LAN or from the WAN?
0
 
John JenningsOwnerCommented:
Also, as just a note in case you didn't know, once you modify the port in the registry, you have to explicitly define it in Remote Desktop Connection.

For example, when typing in the address you want to connect to, it would look like:
192.168.3.100:3386
0
 
skiaholicAuthor Commented:
That was fast, thanks a lot!
The XP client had the firewall on also, I added the exception for the port and now it's working.
0
 
John JenningsOwnerCommented:
Awesome skiaholic! Glad it worked for you. :)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: MCSA MCSE Windows Server 2012

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

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