This content has been marked as final. Show 4 replies
Difficult to answer without knowing what computer systems are involved here, but it sounds like remote access services are unavailable, blocked by a firewall or not started on the target host. Did it work before, what is the target OS?
I suggest you try 'nmap' to scan your target open ports
yum install nmap
or you can try
if you are connecting from outside the network to your inside LAN,
and check for port 3389, to see if it is blocked.
Run nmap and this was the result:
[user1@acer ~]$ nmap 192.168.1.100
Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2010-05-28 15:12 PET
mass_dns: warning: Unable to determine any DNS servers. Reverse DNS is disabled. Try using system-dns or specify valid servers with dns_servers
Interesting ports on 192.168.1.100:
Not shown: 1675 closed ports
PORT STATE SERVICE
135/tcp open msrpc
139/tcp open netbios-ssn
443/tcp open https
445/tcp open microsoft-ds
912/tcp open unknown
How to open port 3389...?
Google is your friend.
dear JLK, I must agree with herb: 'google is your friend'.1 person found this helpful
To give you a few pointers:
- The nmap output shows no 3389/tcp open, which means you will not be able to use the terminal server on that host, even if it where active.
- Check if the windows host you are trying to reach has a terminal server running (which is the windows server component which is responsible for serving remote desktop connectons), or has windows desktop sharing enabled (which is the windows client/non server variant responsible for serving remote desktop connections)
- Check if the windows host your are trying to reach has a firewall of some sort (the windows embedded one, or a 3rd party one) enabled.
- Also, can other machines use remote desktop on that machine?