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?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Most of everything you have sounds fine.  Maybe it's me, but I can't figure out why you even have DynIP in use if you have DSL with a static IP address and you have static IP addresses on your internal network PCs.  I'm not sure why the PC name is even important to you when you have all of the static IP address information you need to make it all happen regardless of what the PC name is.

The key should be the router port forwarding to that one internal static IP address and the enabling of Remote Desktop on that one PC so that it is ready to accept incoming requests.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
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.
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

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?
I have run into problems with macafee firewall for some unknown reason even after I punched a hole for port 3389 (Have seen this happen with norton also)
I found that zoneAlarm worked great, and opened the port with no problem and has more features than macafee and norton ( )

try connecting from within your local network, if no joy with this, try disabeling your firewalls and try again. If you connect after disabeling than the problem is with your firewall.
if you can connect from interal network, then double check your router port-forwarding and static IP assignment for you internal network.

also make sure you have enabled remote desktop and added the users you wish to have connect remotely (they must use passwords to log into computer)

if you want to resolve your ip address from your isp to an easy to remember name try using no-ip, it's free and works great


Any luck here?
try or

either will allow remote access and be safer, since they use port 80, and will go past firewalls.

Good Luck,
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.