Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 632
  • Last Modified:

Unable to connect to a remote desktop PC host via internal network or remotely off site

Hi this is my first posted question so let me know if I am missing any required information.
The issue that I am encountering is with a XP Professional SP2 desktop with remote desktop setup on it as a host.
It is setup to listen on port 3399 this was changed through the registry via instructions on MS site.
But when I try to connect to the machine via the remote desktop application I get no errors, the application goes Grey for a second then the connect button just lights back up and you can click it till you are blue in the face but nothing happens.
I have the port forwarding rules setup on the router and am able to see the connection via www.canyouseeme.org.
I have also ran the prtqry tool from Microsoft and the port shows as listening and all the terminal server services are running.
I have also tried a different network card to rule out faulty hardware and still same issue.
Windows firewall is disabled, I have also tried enabling it and adding the custom port as an exception but still same issue,  have tried changing the port back to the default 3389 and it doesnt make a difference.
I have checked the group policies on the local machine and everything looks correct, the user that needs access is the local account with admin privileges and is a member of the remote desktop users.
I have 5 other machines on the same network setup (different ports of course) and they work without issue and I never ran into any problems in setup on any of them.
Any ideas or suggestions would be appreciated as I have pretty much exhausted all of the ones I can think of.
Thanks in advance

0
Whisper_cat
Asked:
Whisper_cat
1 Solution
 
KCTSCommented:
Have you checked the obvious - is Remote Desktop enabled on the target machine? Is remote desktop enabled as an exception in the firewall on the target machine ?
0
 
cyberseanCommented:
Add the different port number after the servername when connecting from the client.  The client will try to connect on 3389 by default, but you changed the port to 3399 on the server.

servername:3399
0
 
Whisper_catAuthor Commented:
Thanks for the quick responses
Remote desktop is enabled on the target machine and firewall exceptions are added for the specified port.
The firewall is currently disabled but have tried connecting with it on as well and it makes no difference.
When i connect I am typing it in as 192.168.1.91:3399 but it doesn't work.
Thanks again for the quick responses and hope I can find a resolve to this issue.
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!

 
cyberseanCommented:
If you go into Administrative Tools, Terminal Services Manager, is the RDP-Tcp protocol enabled?
Could also try to Reset it?
0
 
Whisper_catAuthor Commented:
Hi cybersean thanks for the reply
It is on an XP professional computer and I don't have the Terminal services manager as an option in the administrative tools unfortunately.
Thanks though
0
 
venom96737Commented:
the host is sp2 are the remote pc's sp3? there is an issue with it not being able to connect to remote desktop.
0
 
Whisper_catAuthor Commented:
Thanks for the reply venom, all of the systems on the network are running SP2.
0
 
Whisper_catAuthor Commented:
As I have not received a response in a few weeks I think my only resolve is going to be a a full system format and reinstall.
Thanks for all the replies.
0

Featured Post

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

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