Windows Forum

Ask something
Question Locked

Remote Desktop Connection can't connect

0 helpful
37 replies

by healer 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I tried to connect to an XP Pro computer from XP Home or Vista Home. Both couldn't connect. I have set up the XP Pro according ot the help and so on. Does it need the terminal service running?

37 replies

by healer

I checked and read the help, the Remote Desktop option is available to connect from XP Home and Vista Home but not receiving connection. XP Pro has both ways available. I can see it on the Properties of the My Computer.

by rob miners

I just tested connecting from XP Home to Windows 7 and had no problems. You should be able to connect from either XPHome or Vistato XP Pro. ;)

by thumbsup2

The Remote Desktop option is available in the HOME versions as a way for Tech Support (and MS) to connect TO (into) the Home systems. Why would it not allow someone to remote in? ;)

(edited to add:)

Ooooops... That's Remote Assistance for getting into the Home version... not Remote Desktop.... LOL!!!! ;)

by rob miners

but you have to send an invitation to the person that you want to look at it. It's called Remote Assistance.

by thumbsup2

I'm getting so old I must be turning dyslectic. I get my A's and D's confused! ;)

by rob miners

I learn something new everyday. But whether I remember it is another story. ;)

by rob miners

and its the first time that I've had any problems like this with IE8. I'll have to look into it I suppose. :D

by thumbsup2

I just tried it with IE8 too, first by pasting the URL into the address bar, then by coming to this thread and clicking the link. Neither worked!!!!!

And, to top it off, all systems look normal, nothing blocked, but the compatibility button is missing on that page, so I can't even switch to compatibility mode. :(

Fancy that! One of MS's own web pages blocked by their newest 'toy'! ;)

(edited to add:)

I erased the last part of the URL and can get to

http://www.microsoft.com/windowsxp/using/mobility/getstarted/

The 'getting started' is listed first. I clicked the link and the page is still blank! :(

by rob miners

but not that one. They've really done it this time. Good one M$ ROFLMA

by rob miners

all in the same workgroup and you have Remote Access enabled on the Host System.

To set up the Remote Desktop, start with the host computer, which in this example is your work computer.

1. Verify that you are signed in as the administrator.

2. Click Start, click Control Panel, and then click Performance and Maintenance.

3. Click System.

4. Click the Remote tab, select the Allow users to connect remotely to this computer check box, and then click OK.

Next, make sure you have Windows Firewall set up to allow exceptions.

1. In the Control Panel, click Security Center.

2. Under Manage security settings for, click Windows Firewall.

3. Make sure the Don't allow exceptions check box is not selected.

4. Click the Exceptions tab, and verify that the Remote Desktop check box is selected.

5. Click OK, and then close the Windows Security Center window.

Your host computer is now set up to allow remote access.

You will need the name of the host computer.

6. In Control Panel, click Performance and Maintenance, click System, and then click the Computer Name tab.

7. Write down the full computer name, and then click OK. This is where you will need the IP address.

8. Close Control Panel.

9. Leave this computer running, locked, and connected to the corporate network with Internet access.

Connect your remote computer to the host computer
To connect your home computer, which is the client (or remote) computer to your work (or host) computer, follow these steps:

1. On your home computer, click Start, point to All Programs, and then point to Accessories.

2. In the Accessories menu, point to Communications, and then click Remote Desktop Connection.

3. In the Computer box, type the computer name of your host computer, which you wrote down earlier.

4. Click Connect.

5. When the Log On to Windows dialog box appears, type your user name, password, and domain (if required), and then click OK.

The Remote Desktop window opens, and you see the desktop settings, files, and programs that are on your host computer, which in this example is your work computer. Your host computer remains locked, and nobody can access it without a password. In addition, no one will be able to see the work you are doing remotely.

To end your Remote Desktop session:

1. Click Start, and then click Log Off at the bottom of the Start menu.

2. When prompted, click Log Off.

Tip! If you check the Options you will see that you can connect your Disk Drives to manipulate Files.

When you open the Remote Desktop you will be on the General Page. You will see something like this if it is pre SP3.

Computer: this is where you type in the Name or the IP Address of the PC that you wish to connect to.

User Name: this is the user that was created on the remote PC.

Password: this is the password that was created for the user on the remote PC.

Domain: this is the domain or workgroup that you are using. You will tpe in worrkgroup.

Save my password: you can tick this box if you like.

Save as: this will allow you to save a shortcut to the connection. I normally rename it and place it on the Desktop.

Open: this will allow you to open a saved shortcut.

Display TAB:

Choose the size of your remote desktop. I normally leave it at Full Screen.

Colors: I use 16 bit. I leave the box ticked for Display the connection bar when in full screen mode. It is handy to minimise the screen.

Local Resources TAB:

Remote computer sound: I leave it as Bring to this computer.

Keyboard: Apply windows key combinations. In full screen mode only.

Local Devices: Connect automatically to these local devices when logged on to the remote computer.

Put a tick in the box for Disk drives. You will have access to your local drives.

I normally untick the next two boxes.

Programs: I leave this area blank as I am not running anything from the other PC.

Experience: Choose the connection speed to optimise performance.

Select Lan (10 Mbps or higher)

by healer

I went through the setup on the host computer in accordance with your post and http://www.microsoft.com/windowsxp/using/mobility/getstarted/remoteintro.mspx. I found my previous setup seemed all right. Anyway I tried again from an XP Home computer logged on with a limited account as well as from an XP Pro computer logged on an administrator. Both still came up with an error message of "The domain/workgroup does not contain any Terminal servers" when I clicked on Browse for more and then the workgroup. When I specified the the computer name and user name I got the message of "This computer can't connect to the remote computer." I ensured that the Terminal Services running and it didn't make any difference.

I tried the IP address instead of the name, same problem happened. Then I did the remote desktop connection on the host computer it said "The client could not connect. You are alaready connected to the console of this computer. A new console session cannot be established." When I did "telnet localhost 3389" on the host computer, it said "Could not open connection to the host, on port 3389: Connect failed".

I am testing all these functions on a local peer-to-peer network in the same workgroup. Do I need a domain? Do I need a server running in the network?

by rob miners

On the Host System

Press the WinKey + Pause

Select the Remote Tab

There should be a tick in Allow users to Remotely connect to this Desktop:

Full Computer Name:

underneath you will find the computer name. This is the Name that you are connecting to from the client.

There is a box that says Select Remote Users. Check to see who is listed and try connecting with those credentials. Passwords on the System will have to be enabled.

You don't need to be on a Domain or have access to a File Server for this to work. I always use an Administrative Account when I connect Remotely.

by thumbsup2

It's been a long time since I used Remote Desktop. But, back then, you had to remember to log out of the host computer before the client computer could connect to it.

Did you try that?

by rob miners

"Browse for computers" does not work in a peer environment.

If you enter the wrong name for the remote computer EG: 10.20.20.29 or w8 you will receve a message similar to this.

Remote Desktop Disconnected
This computer can't connect to the remote computer.
Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator.

This what you see if you click on Help

Frequently asked questions about Remote Desktop ConnectionWith Remote Desktop Connection, you can easily connect to a remote computer running Windows. All you need is network access and permissions to connect to the other computer. You can also specify special settings for your connection, and then save the settings for the next time you connect.

What is Remote Desktop Connection?

Remote Desktop Connection is a technology that allows you to sit at a computer and connect to a remote computer in a different location. For example, you can connect to your work computer from your home computer and have access to all of your programs, files, and network resources as though you were in front of your computer at work. You can leave programs running at work and when you get home, you will see your work computer's desktop displayed on your home computer, with the same programs running.

What is a full computer name?

Also known as a fully qualified domain name (FQDN), a full computer name includes the host (computer) name, the domain name, and all the higher level domains. For example, the full computer name of a computer named "host" might be host.example.microsoft.com.

When do I need to use authentication in Remote Desktop Connection?

Use authentication when you want to securely verify that you are connecting to the correct computer. Your network administrator might also require you to use authentication.

What are server authentication options?

In Remote Desktop Connection, server authentication verifies that you are connecting to the correct remote computer, or server. This security measure helps prevent the interception of data by an unauthorized remote computer. There are three available authentication options:

Always connect, even if authentication fails (least secure): With this option, even if Remote Desktop Connection cannot verify the identity of the remote computer, it connects anyway.
Warn me if authentication fails (more secure): With this option, if Remote Desktop Connection cannot verify the identity of the remote computer, it warns you so that you can choose whether to proceed with the connection or not.
Don't connect if authentication fails (most secure): With this option, if Remote Desktop Connection cannot verify the identity of the remote computer, you won't be able to connect.
To change authentication options, open Remote Desktop Connection, click Options, and then click the Advanced tab. If you're not sure which option to choose, ask your system administrator or the owner of the remote computer.

Remote computers that are running Windows Server 2003 with Service Pack 1 (SP1) or earlier operating systems cannot provide their identity for verification. If you know that the remote computer is running one of those operating systems, you can avoid authentication warnings by choosing Always connect, even if authentication fails, and then saving that change by clicking Save or Save As on the General tab.

The default option is "Always connect, even if authentication fails." To change it for future use, select the authentication level you want, and then, on the General tab, click Save or Save As to save your settings to an .rdp file. To connect to the same remote computer in the future, double-click the .rdp file.

What is Network Level Authentication?

Network Level Authentication (NLA) is a new authentication method that completes user authentication before you establish a full Remote Desktop connection and the logon screen appears. This is a more secure authentication method that can help protect the remote computer from hackers and malicious software. The advantages of NLA are:

It requires fewer remote computer resources initially. The remote computer uses a limited number of resources before authenticating the user, rather than starting a full Remote Desktop connection as in previous versions.
It can help provide better security by reducing the risk of denial-of-service attacks (attempts to limit or prevent access to the Internet).
It uses remote computer authentication, which can help protect people from connecting to remote computers that are set up for malicious purposes.
To find out if your computer is running a version of Remote Desktop with NLA
Open Remote Desktop Connection.
Click the icon in the top left corner of the Remote Desktop Connection dialog box, and then click About.
Look for the phrase "Network Level Authentication supported" on the About Remote Desktop Connection dialog box.

What is a Terminal Services Gateway server?

A Terminal Services Gateway (TS Gateway) server is a type of gateway that enables authorized users to connect to remote computers on a corporate network from any computer with an Internet connection. TS Gateway uses Remote Desktop Protocol (RDP) along with HTTPS to help create a more secure, encrypted connection.

In earlier versions of Remote Desktop Connection, people could not connect to remote computers across firewalls and network address translators because port 3389?the port used for Remote Desktop connections?is typically blocked to enhance network security. However, a TS Gateway server uses port 443, which transmits data through a Secure Sockets Layer (SSL) tunnel.

A TS Gateway server provides these benefits:

Enables Remote Desktop connections to a corporate network from the Internet without having to set up a virtual private network (VPN) connection.
Enables connections to remote computers across firewalls.
Allows you to share a network connection with other programs running on your computer. This enables you to use your ISP connection instead of your corporate network to send and receive data over the remote connection.
Ask your network administrator whether you need to specify a TS Gateway server.

To specify a TS Gateway server:

Open Remote Desktop Connection by clicking Start, clicking Programs or All Programs, clicking Accessories, and then clicking Remote Desktop Connection.
Click Options, click the Advanced tab, and then, under Connect from anywhere, click Settings.
Select Use these TS Gateway server settings, and then type the server name (ask your network administrator for this information).
Select one of the three available logon methods:
Allow me to select later. This option lets you select a logon method when you connect.
Ask for password. This option prompts you for a password when you connect.
Smart card. This option prompts you to insert a smart card when you connect.
Select or clear the Bypass TS Gateway server for local addresses check box.
Selecting this check box prevents traffic to and from local network addresses from being routed through the TS Gateway server, which makes your connection faster.

Note

Your network administrator might not allow changes to TS Gateway server settings.

Is there dual monitor support for Remote Desktop Connection?

Remote Desktop Connection supports high-resolution displays that can be spanned across multiple monitors. The monitors must be the same height and aligned side by side. To have the remote computer's desktop span two monitors, type Mstsc /span at a command prompt.

This feature is sometimes called continuous resolution. To toggle in and out of full-screen spanned mode, press CTRL+ALT+BREAK.

How can I change the listening port for Remote Desktop Connection?

For additional security, you can change the port that Remote Desktop Connection uses (or "listens on"), instead of using the standard port 3389. When you log on, type the remote computer name, followed by a colon and the desired port (for example, Computer1:3390).

How does Remote Programs work?

Remote Programs is a feature in Windows that allows you to connect to a remote computer and use programs installed on it. For example, your workplace might have a remote computer that you and other employees can connect to and run Microsoft Word. The experience is the same as running a program installed on your computer.

Remote Programs makes system administration easier because there is only one copy of a program to upgrade or maintain, rather than many copies installed on individual computers.

Notes

To open Remote Desktop Connection, click Start, click Programs or All Programs, click Accessories, and then click Remote Desktop Connection.
To enable your computer to accept remote connections, open System in Control Panel. In Windows XP, click the Remote tab and then select the Allow users to connect remotely to this computer check box. In Windows Server 2003, click the Remote tab and then select the Enable Remote Desktop on this computer check box. Click OK.
To view a list of available computers on a domain, open Remote Desktop Connection, click the arrow next to Computer, and select Browse for more.

by healer

I have read these helps a few times somewhere else too. I will try again later when I have some new ideas.

by healer

When I tried to access another XP Pro system on the same network, I managed to get in with the IP address most of the time but never on the computer name as stated on the Remote pane. What can I check?

by rob miners

the session will be ended as soon as the credentials are supplied. Whoever is logged on will get kicked off.

At a command prompt type in net view

it will give you a list of the Systems and their Names if they are all in the same Workgroup.

by healer

Both the "net view" and and "My Network Places" showed all the relevant computers on the local network. I could access all the shared directories of all the computers in question. Hence there was no network issue.

by healer

The XP Pro was all set up as it should have been. The same errors remain.

I booted up the Windows Server 2003. I managed to get the logon window from the Server 2003 which was one step forward but I couldn't log on even I enter the correct password. Also the "Browse for computers" still wouldn't work. This was a test server so only one user had been set up and it was an administrator. According to the help I didn't need to specifically add the user in.

I booted up the Windows Servers 2000 but there was no remote desktop available.

by healer

I have tried but it made no difference.

by jgirizarry

Allow 3389 port number thru the firewall, your port number 3389 is configure correctly in your router with TCP as the port type.

Assign a static IP on your host computer (WINXP PRO)to prevent DHCP to change it after the leasing has expired. Setup an account for you to access and include it in the remote account members on your host machine.

by healer

I have temporarily turned off the firewall of the host computer and tested it but no luck. I ran ipconfig and worked out the IP address and tested it with the IP address again but it still failed.

by el_duce

can you tell exactly what you do in order to make the connection.
Also is the xp pro SP2 or 3?

by healer

The host is XP Pro SP3 and the clients are XP Home SP3 and XP Pro SP3. They are on a local network in the same workgroup. There is no problem seeing all computers and their shared folders from one another. I brought up the Remote Desktop Connection from Accessories on the client computer. I try to connect with the full computer name as stated under Remote Desktop on the Remote tab of the host computer with the Administrator's user name of the host. I have also tried the IP address of the host. I ascertain the IP addess using ipconfig on the Command Prompt. I always get the error message "This computer can't connect to the remote computer." I always ensured the Windows Firewall has an exception for Remote Desktop checked. I have even tried to have the Firewall of the host computer turned off.

by rob miners

Enable NetBios over TCP/IP in WIndows XP

Click Start, click Control Panel
Click Network Connections.
Right-click "Local Area Connection", and then click "Properties".
Click on (highlight) "Internet Protocol (TCP/IP)", and then click "Properties" button
Click the General tab, and then click "Advanced" button , bottom right.
Click the WINS tab.
Under "NetBIOS setting" section, click Enable NetBIOS over TCP/IP, and then click OK two times, then "close".
( ) Default
(*) Enable NetBios
( ) Disable NetBios

Restart the PC

by healer

The NetBIOS setting had been set to default. According to the explanation the NetBIOS over TCP/IP should be enabled if static IP address is used or the DHCP server does not provide NetBIOS setting. The IP address is not static and the DHCP server does not provide NetBIOS setting. Anyway I have checked Enable NetBIOS over TCP/IP and restarted the computer twice. The full computer name is still not recognized.

by rob miners

new builds or have they previously been used for testing. You were originaly connecting XP Home and Vista to XP Pro.

Check that these Services are Started on all PCs:
Computer Browser
DHCP Client
DNS Client
Network Connections
Network Location Awareness
Remote Procedure Call (RPC)
Server
TCP/IP Netbios helper
Workstation

See what the result from nbtstat -n is from a command prompt.

by healer

This is a fairly newly-installed XP Pro test system. A Vista Home Basic work system is installed alongside in adjacent partition. This is the one I had problem installing XP Pro in the first place because the hard drive is SATA. You were one of them who helped me install. It is mainly a test system though it has a few old applications installed like Dreamweaver 4, Fireworks 4, Office 2003 and so on.

I have checked all the services stated. They are all started and running on both host (XP Pro test) and client (XP Home work) computers.

Upon running the command "nbtstat -n" I noticed the registered name of the host computer is different from what is shown on System Properties under the Computer Name or the Remote. Somehow the registered name is the same as that of the Vista system installed alongside. I can't explain that. I would appreciate if you help me with that. I checked the client computer and the computer name is the same throughout. Then I tried the Remote Desktop Connection again with the newly found registered name of the host computer and it worked all right.

by rob miners

Someone will correct me if I'm wrong but it looks like DHCP is assigning the original hostname. Windows systems do not issue a release packet when exiting or shutting down. This would leave the DHCP lease open, so you can reboot a System and maintain the existing DHCP lease.

by healer

I've always supposed DHCP is repsonsible for issuing IP addresses and WINS is for computer names.

Having done a lot of tests I have found out what the problem was. I switched to the Vista on the same computer. I changed the computer name by adding more characters it said the name only allows 15 bytes. Then it occurred to me that the XP computer name was more than 15 characters long and the first 15 characters are the same as the Vista's. XP doesn't report it was a problem when I had the name too long. I have since changed the name of this XP's and it has worked fine.

Only thing I have noticed so far on the other XPPro computer which has since been re-installed, having the computer name changed rendered further remote connection via the name to fail while connection through the IP address still works okay. Both worked fine initially. I have supposed it might take time to settle down. Then having restarted the computer and waited for a while the situation hasn't been improved.

This discussion is closed to new replies.