Remote Desktop Connection Fails

K

Karine Rivet

I have my home computer configured to allow Remote Desktop connections. I'm
using the Windows Firewall and I've confirmed that Remote Desktop is allowed
in Windows Firewall and I've even gone so far as to go into the advanced
settings for the local area connection and specifically allow the Remote
Desktop service yet every time I try to connect to my home PC using a Remote
Desktop connection the connection attempt fails. I've also confirmed with
my ISP that port 3389 is not blocked in any way. Does anyone know why this
isn't working and what I need to do to get it working?
 
S

Steven Umbach

If RDP is enabled on your computer the command netstat -an will show that port
3389 TCP is listening. If it is try connecting to your computer by entering the
IP address of your public IP in the RDP connection box that your ISP issues to
you to make the connection. You can go to the site below to find your current
public IP address and also to scan your computer which should show port 3389
open if your computer and firewall is configured to allow RDP access. --- Steve
 
K

Karine Rivet

Netstat -an reported "TCP 0.0.0.0:3389 0.0.0.0:0
LISTENING" for port 3389. I have tried establishing an RDP connection using
my ISP's issued public IP address and it always fails. You didn't provide
the site link to check my IP address or ports, so I went to ShieldsUp and
confirmed that I do have the right public IP address, however, ShieldsUp
reported that port 3389 was in stealth mode meaning I believe that it's
inaccessible. If I read the information correctly from Netstat -an it
appears that port 3389 is only available internally which of course would
explain why I can't connect and why ShieldsUp reports it as being in stealth
mode. Is this correct? If it is correct, how do I get port 3389 available
over the Internet?




If RDP is enabled on your computer the command netstat -an will show that
port
3389 TCP is listening. If it is try connecting to your computer by entering
the
IP address of your public IP in the RDP connection box that your ISP issues
to
you to make the connection. You can go to the site below to find your
current
public IP address and also to scan your computer which should show port 3389
open if your computer and firewall is configured to allow RDP access. ---
Steve
 
B

Backup

As I work for and deal with many ISP's well known and some not that popular;
I have knowledge that some ISP's are blocking inbound connections to
services that are considered to be server related.



Such as RDP (this is used mostly for terminal services) this is considered a
server services, VPN (virtual private networking) this is also blocked.
SMTP (we all or should know that most ISP's now block this on the inbound to
your connection).



Now ISP are blocking outbound also SMTP (forcing you to use theirs to send
email) NNTP (Usenet) also forcing you to use theirs. In both cases you must
pay more, thus upgrading your account to use them. Say good by to your
(what you ISP will call) 3rd party email providers and Usenet providers.



Many other things that people don't notice that are now blocked. Over the
internet UNC mappings. No more \\your.freidns.address.com\c$ to share
files.



Some ISP's are also blocking SQL, SNMP ports in and outbound. But if you
want them you must pay.



I know all this cause I have to block theses as well.



It sucks . and what do most ISP's claim still. "Unlimited Internet" this is
just bill *$^#.
 
S

Steven L Umbach

Sorry I forgot the link but you did well on your own. If it was reported
that your port 3389 TCP is blocked then you need to make sure your firewall
is allowing inbound traffic to port 3389 TCP. For a typical cable/dsl NAT
router you also need to "port forward" port 3389 TCP to your computer to be
able to accept RDP connections. --- Steve
 
K

Karine Rivet

I've already checked with my ISP and they are not blocking RDP or port 3389.




As I work for and deal with many ISP's well known and some not that popular;
I have knowledge that some ISP's are blocking inbound connections to
services that are considered to be server related.



Such as RDP (this is used mostly for terminal services) this is considered a
server services, VPN (virtual private networking) this is also blocked.
SMTP (we all or should know that most ISP's now block this on the inbound to
your connection).



Now ISP are blocking outbound also SMTP (forcing you to use theirs to send
email) NNTP (Usenet) also forcing you to use theirs. In both cases you must
pay more, thus upgrading your account to use them. Say good by to your
(what you ISP will call) 3rd party email providers and Usenet providers.



Many other things that people don't notice that are now blocked. Over the
internet UNC mappings. No more \\your.freidns.address.com\c$ to share
files.



Some ISP's are also blocking SQL, SNMP ports in and outbound. But if you
want them you must pay.



I know all this cause I have to block theses as well.



It sucks . and what do most ISP's claim still. "Unlimited Internet" this is
just bill *$^#.
 
K

Karine Rivet

K

Karine Rivet

At the moment I am using just the built in Windows Firewall and it has been
configured to allow Remote Desktop/port 3389. Perhaps I should have
mentioned early on that I am running SP2. And, I've noticed many posts in
these newsgroups from people that are running SP2 who are unable to get
Remote Desktop running. I fear I'm having the same problem as a result of
SP2. Any other thoughts?




Sorry I forgot the link but you did well on your own. If it was reported
that your port 3389 TCP is blocked then you need to make sure your firewall
is allowing inbound traffic to port 3389 TCP. For a typical cable/dsl NAT
router you also need to "port forward" port 3389 TCP to your computer to be
able to accept RDP connections. --- Steve
 
S

Sooner Al [MVP]

If your running NAV 2005 on the PC that may be the problem. Some folks report the NAV 2005 antiworm
protection blocks Remote Desktop connections. Disabling the worm protection solves the issue...

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights...
 
K

Karine Rivet

Not running NAV 2005.




If your running NAV 2005 on the PC that may be the problem. Some folks
report the NAV 2005 antiworm
protection blocks Remote Desktop connections. Disabling the worm protection
solves the issue...

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual
benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
S

Steven L Umbach

I have no problem using RDP to an XP SP2 computer. What you should try is to
disable the firewall to see if access is allowed then. However I would not
suggest that if you do not have another firewall such as a NAT router
protecting your computer/network. The best thing to try is possible is to
try to connect to RDP from another computer on the local network that has
proper connectivity to your XP Pro computer while it has the firewall
disabled. That way you can determine for sure if the problem is the Windows
firewall, internet connection, or other problem and proceed from there. You
should also go to System Properties/Remote to make sure that RDP is enabled
and that the necessary users are listed as having access. By default local
administrators will have access. Also check Local Security Policy
[secpol.msc] and go to security settings/local policies/user rights and make
sure that administrators and Remote Desktop Users are included in the user
right for "allow access through Terminal Services" and that there are no
entries in "deny access through Terminal Services". If your computer is a
member of an Active Directory domain, then there may be policy applied at
the domain level to prevent access. --- Steve
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Remote Desktop breaks down everytime - getting unusable! 6
Remote Desktop Connection to SBS 2003 with ISA 2004 5
security question regarding opening up ports 6
Problem Allowing Remote Desktop Through Software Firewall 2
Remote control from Vista laptop to XP desktop 1
Remote Desktop not working anymore 9
Remote desktop and SP2 1
Remote Desktop Connection, not working now... 2

Top