EEhab
asked on
Running Remote Desktop from network behind a Linksys router and modem.
I have a DSL subscription with a static IP assigned from my ISP. I use Linksys ADSL2MUE modem, WRT54GS wireless broadband router, and WMP54GS as the wireless PCI adaptors on 2 PCs running WinXP Pro and Win 2003. I have configured the router and the PCs with static IP addresses. I properly configured McAfee Personal Firewall and Windows Firewall to open and unblock port 3389 so I can use RDP to get through to one of my PCs. I believe I properly configured the router to unblock and forward port 3389 to an IP address of one of the PCs. I installed DynIP to be able to resolve PC name to get through while I am away, but unfortunately to no avail. When I try to resolve my PC name from within DynIP website, it fails and comes back with “port 3389 is blocked”. Can anyone help me have Remote Desktop my PC please?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
CarlWarner
BTW, you can try to Remote Desktop from your internal WinXP to your Win2003 Server, just to see if it's working as you think it should be within your internal network. We are assuming it works at all without checking that it works within your own network from machine to machine. [Or if the PC you are trying to get to is the WinXP one, try the same from the Win 2003 PC to it.]
Without even worrying about a PC name, when I come in from outside to get to one of my PCs, all I have to do is to type in my assigned external IP address that my ISP has given me. That's it.
Once I have that done, the request is automatically assumed to use port 3389 and looks to my router at my home to see what internal IP address I have port 3389 assigned to. If there is an active "port forwarding" setup in the router to get to an internal IP address, the request gets passed right through to my local PC and then looks to see that Remote Desktop has been enabled on that PC.
Assuming the firewall stuff has been setup to allow that to happen, the session will either log you in if you already had supplied the user name and password, or will ask you for a login name and password to get the session started.
It works fine for me.
Once I have that done, the request is automatically assumed to use port 3389 and looks to my router at my home to see what internal IP address I have port 3389 assigned to. If there is an active "port forwarding" setup in the router to get to an internal IP address, the request gets passed right through to my local PC and then looks to see that Remote Desktop has been enabled on that PC.
Assuming the firewall stuff has been setup to allow that to happen, the session will either log you in if you already had supplied the user name and password, or will ask you for a login name and password to get the session started.
It works fine for me.
I agree, first though .. can you access the machine from another machine within the network to isolate your problem to router or pc machine config? This will also "Check" your pc config to be properly configured..
what about the machine you are trying FROM the internet? is that firewalled?
what about the machine you are trying FROM the internet? is that firewalled?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
EEhab,
Any luck here?
Any luck here?
try www.gotomypc.com or www.logmein.com
either will allow remote access and be safer, since they use port 80, and will go past firewalls.
Good Luck,
either will allow remote access and be safer, since they use port 80, and will go past firewalls.
Good Luck,