You cannot run tracert to TCP port. Tracert uses ICMP.
I'm pretty sure your 3389 is blocked on one of your routers or firewalls.
Main Topics
Browse All TopicsI have a server running server 2008r2. I'm trying to setup Terminal Services or Remote Desktop, as it's called in server 2008. I have a static IP running thru a DSL modem in full bridge mode, or pass thru. I have a Cisco ASA 5505 Firewall. I have Crosstel DSL, My problem is that I can not connect RDP when I am on another ISP yet I can connect when I'm on a computer with Crosstel that is the ISP. Example: I have another customer in the same area using Crosstel, he also has a static IP. When I try RDP there, I connect just fine, I believe I'm correct in assuming that the ASA 5505 is listening on port 3389 and is forwarding RDP requests to the proper place. Yet when I try to connect from my shop which is on Windstream DSL I can not connect. I have been on the phone with Cisco and they say no traffic is reaching the ASA on port 3389. I have also tried this connectionn from an AT&T connection with no luck. I can ping the server from all locations but can't connect from anywhere but the Crosstel Connection. I have contacted Crosstel an they tell me they have no blocks on port 3389?
One other thing, when I run a tracert it tracks just fine, I tried running tracert like telnet where I specified a port. (tracert 000.00.00.00 3389) I don't know if this is practical but the trace makes it to a level 13 in Dallas where it dies?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I can run tracert 000.00.00.00 and get a complete path, I'm trying to find out where the 3389 port is being blocked. I have trouble understanding how the port could be blocked on my router orfirewall, they allow RDP from a connection that is on a Crosstell ISP so that tells me it isn't being blocked by either one of them. Doesn't it??
Simple solution would be to forward another external port to 3389 internally. That would reveal if the ISP is involved. It's not that great of an idea to expose RDP to the Internet. Putting it on a non-standard port will hide it from all of the script-kiddies looking for Windows machines to mess with. You could choose an obscure high port like 65324 or something. It's a good idea to make sure the port you are using isn't used by another commonly exploited port, for example 445.
The best way would be to connect via VPN which would tunnel all traffic transparently and if the VPN connects, so will RDP.
Business Accounts
Answer for Membership
by: oleggoldPosted on 2009-09-16 at 07:09:06ID: 25345717
try tracert 000.00.00.00