• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Remote Desktop Issues

J

jimbofoxman

Senior member
I am having problems trying to connect from my home PC into our server at work using Remote Desktop. At home I have Win 7 Pro and the machine at work is XP Pro (I know, XP Pro server is not a good setup but that's another issue).

I can Remote Desktop from my work PC to the server no problem using the internal IP address. I've done some looking around and I guess I need to do some port forwarding but I got a couple different port numbers and none of them let me in.

Router is a Linksys WRT150N and I configured the port forwarding at first to forward port ??3389?? for TCP to the internal ip address. NO GO

Then I found one that said to open port 6279 and 7279 for TCP.

So in the applications and gaming tab, single port fowarding I forward both those ports to the internal IP address. But it gives me two inputs, and EXTERNAL PORT and an INTERNAL PORT. Right now I have both those filled with the same port number.

But I am still not getting anywhere.

Any suggestions, or a recommended site I can look at?

Thanks
 
Nothinman said:
3389 is the correct TCP port for RDP, if it's not working then something is up with your router or ISP.
Click to expand...

Yup, you only need to forward 3389 with TCP to the IP of the server.

Make sure you have the 'enabled' check box ticked to activate it.

And make sure you have the correct external IP for your office, so you can connect to it from home. The internal (NAT) IP is different from the external (public) IP.

I like whatismyip.com or ipchicken.com

I'd also recommend using an account on the computer that has a non-standard name with a STRONG password. You will get people doing random port scans, and if they find an open RDP port, they'll start trying random logins. I've actually locked our RDP port down with a more capable firewall, so only a few select IP's can pass through.
 
Last edited:
Thanks dawks.....that might be it. I ran whatsmyip and ipchicken and it gave me a different IP than what IPConfig did. So maybe the equipment TDS metro installed gives us another address. I will try the new one tongiht.
 
jimbofoxman said:
Thanks dawks.....that might be it. I ran whatsmyip and ipchicken and it gave me a different IP than what IPConfig did. So maybe the equipment TDS metro installed gives us another address. I will try the new one tongiht.
Click to expand...

Yea, ipconfig will give you your internal NAT IP. Your Linksys gateway/router gets an IP from your ISP. This is your public IP. Its what identifies you on the internet. The IP from ipchicken.com is what you need at home to connect to work.
 
I guess I'll have to call TDS Metro because it still isn't working.

When I look at the confit screen on the linksys wrt150 it gives me a space for an INTERNAL and a EXTERNAL port. I have them both filled with 3389. Is that correct?
 
yup port forward:
from: 3389
protocol: tcp
ip address: (static ip of your internal box)
port to: 3389

(taken from dd-wrt)
 
StlCardinals...........I just signed up with LogMeIn. For some reason I was thinking it was a pay service and I was trying to avoid that for the time being. But I saw they had a free version too. It's all setup and running and verified from my home PC.

Thanks!
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top