• 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.

Need help with ports and remote desktop

mooseracing

Golden Member
I have three computers on a single Netgear router all setup for REmote Desktop. I have the router configured to different ports for each RDP client and what IP to fwd the requests to. Anytime RDP is used we are using a dyndns addy as our ip isn't static.

I have my roomate setup with the RDP port 3389 on the router. Since i have access and i know how to do custom ports my laptop and tower are odd port numbers. My problem is now though that my work doesn't have these odd ports open, so now i can't remote in from work.

I'm not trying to circumvent their security but is there a way to run multiple request on on the 3389 port? It seems if i have the computers all setup to use that port on my router it always connects to his, unless it is random and i haven't done it enough times to bring up mine?

Otherwise i was going to do a portscan at work to see whats open?
 
Follow this guide and then forward the port(s) you chose to the specific IP.

http://support.microsoft.com/kb/306759/

When you connect you'll have to do
youraddress.dyndns.com:3390
youraddress.dyndns.com:3391
etc.

That should get you going.

*EDIT*
Well crud...I just reread your original thread again.
So you are trying to connect to RD to a few PCs at work, correct?
I have to go to class but I will try to get back to you on this if I think of something other than asking them to forward more ports.
 
Actually, if I understand correctly now, what I do with my home PCs is enable remote desktop on the systems that I want. Then, forward one port, 3389, to one specific PC and then from that Remote Desktop screen, I RD into another system from there. I do this to keep from opening so many ports.

I don't know if that would be acceptable for you or not.
 
Originally posted by: TC10284

*EDIT*
Well crud...I just reread your original thread again.
So you are trying to connect to RD to a few PCs at work, correct?
I have to go to class but I will try to get back to you on this if I think of something other than asking them to forward more ports.

trying remote from work to home


Originally posted by: TC10284
Actually, if I understand correctly now, what I do with my home PCs is enable remote desktop on the systems that I want. Then, forward one port, 3389, to one specific PC and then from that Remote Desktop screen, I RD into another system from there. I do this to keep from opening so many ports.

I don't know if that would be acceptable for you or not.


hmm i'm confused on the part where you say you RD in another system from there. When i type in my dyndns addy without specifying the port (this is before i changed ports and they were all regular RDP 3389) it would always bring up my buddys pc an dhis logon box. Are you saying i could put my computer name in there or the dyn dns addy?
 
If you are trying to RD from work to home, then you should be able to do steps in the link that I provided and then forward the ports on your router if you want to do it that way.

As for your confusion, what I mean is, open one RD connection to one of your home PCs using your dyndns address. Then on the PC you just RD into, open the RD client from that PC using your computer name or its local IP address, into another PC on your home network. In other words, having one RD session on top of the main one. I wouldn't stack more than one RD session though.

I hope that sounds a little clearer. I'll try to think it through more if not.
 
another option is vpn,,,

so if you want to rdp from work you would vpn to your home network then rdp anypc on your network and only have to open the vpn port on your router(dont need a port forward for rdp once your in)

downside would be once you vpn your network are joined (random work pc's might see your home pc shares's)

make shure your not on the same ip scheme at home and work 192.168.0.x in both locatations could cause conflicts,,, on second thought its complicated and maybe you shouldnt do vpn lol sry.... but thats what i would do...
 
TC10284.... rdp in the rdp in the rdp is a fun option sometimes at work i go vpn-rdp-pcanywhere-rdp .... spaning mayn networks and dual nic boxes lol
 
Originally posted by: kaleaf
TC10284.... rdp in the rdp in the rdp is a fun option sometimes at work i go vpn-rdp-pcanywhere-rdp .... spaning mayn networks and dual nic boxes lol

Haha...😀
 
Originally posted by: TC10284

As for your confusion, what I mean is, open one RD connection to one of your home PCs using your dyndns address. Then on the PC you just RD into, open the RD client from that PC using your computer name or its local IP address, into another PC on your home network. In other words, having one RD session on top of the main one. I wouldn't stack more than one RD session though.


The only pc setup withthe normal RD port is my roommates. I doubt he wants me connecting to it to get to my pc.

I'm looking into the VPN stuff right now
 
in a nutshell, no

the only way this works (multiple requests on one IP/Port get handled differently) is web servers, and headers (www.example.com and example1.com may both have the same ip and both run on 80)
 
Originally posted by: mooseracing
Originally posted by: TC10284

As for your confusion, what I mean is, open one RD connection to one of your home PCs using your dyndns address. Then on the PC you just RD into, open the RD client from that PC using your computer name or its local IP address, into another PC on your home network. In other words, having one RD session on top of the main one. I wouldn't stack more than one RD session though.


The only pc setup withthe normal RD port is my roommates. I doubt he wants me connecting to it to get to my pc.

I'm looking into the VPN stuff right now

Why don't you just put all computers on the normal rdp port and set the port forward to go to your computer. That way you would have to connect to your computer if you ever wanted to get to his, but you would not have to connect to his to get to any other computers.

You could also use VNC and use a VNC proxy. Whatever computer the VNC proxy service is running on would have to be turned on to get to the other computers, but it would not disturb anyone using the computer, and might be more responsive than rdp-in-rdp.
 
Logmein is definitely worth a look. I've used it for a while now and I've not had any problems with it, regardless of what router configuration I'm behind. It's free also
 
Back
Top