[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

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

Still can't connect to the remote computer using RDP

The Linksys BEFSR41 is set to port forward Application named "TSGreg" with port # 3393 (Protocol-Both) to the user's desktop at 192.168.0.22.  

I have set the desktop's ip to 192.168.0.22 and I have turned off the XP firewall for testing but i still get "This computer can't connect to the remote computer.."  

I am entering the RDP address like this xxx.xxx.xxx.xxx:portnumber

It worked fine before we re-installed XP on the machine. Other users can still ge to their PCs.

Any ideas?
0
akus1
Asked:
akus1
  • 5
  • 5
  • 2
1 Solution
 
pauratCommented:
Is remote desktop enabled in CONTROL PANEL > SYSTEM > REMOTE?

There should be a check box to allow connections.
0
 
akus1Author Commented:
Yes, it is enabled. How about under "Select Remote Users". Currently there is only the user and I added Domain Admins. Do i need Everyone or anything like that?
0
 
pauratCommented:
By default, any member of the Administrators group can RDP. You could try adding yourself into the 'allowed' list.

Are you doing this internally or externally?
0
Independent Software Vendors: 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!

 
pauratCommented:
Has the computer been restarted since you changed the listening port? Try a "netstat -a" to confirm it is listening on the right port.
0
 
akus1Author Commented:
I am remoting on to the systems using Kaseya's VNC.
0
 
pistolslapperCommented:
If i have taken you up right, the PC is now fresh formatted and not working. I see you are using a different port - 3393. Have you went into the registry inside the target machine and changed the port there?

http://support.microsoft.com/kb/306759 - this will show you how to change it properly.
0
 
pauratCommented:
Sorry, |'m a little confused. Kaseya (as far as I know) requires a server side installation. You would not need to change the listening ports of the separate pc's as the server would handle the transactions.

Have you simply tried using RDP, type mstsc at the run command and try putting in the xxx.xxx.xxx.xxx:portnumber and see what happens. Make sure you are internal to the network to rule out the firewall. As stated earlier, can you check that the PC is listening on the correct port.
0
 
akus1Author Commented:
Brilliant! Thank you. My client will be happy again.
0
 
pauratCommented:
Incorrectly awarded in my opinion, as the listening port was pointed out earlier.
0
 
akus1Author Commented:
I apologise paurat. I didn't catch that. Too many hours today. Pistolslapper did get what was going on through my thick skull.
0
 
pistolslapperCommented:
I have a feeling that akus1 changed the listening port incorrectly by typing in 3393 under hex and not decimal. That article explained the procedure for doing it step by step. I think the points are deserved if this was indeed the issue.

Have you tested this fix yet akus1?
0
 
akus1Author Commented:
Yes - that was the final stumbling block. The port needed to be set up custom on the PC as described in the article so that it would match the custom port used in the router port forwarding. All is well now.
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

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