Can't connect to clients via Windows Remote Desktop Connection - works under Ubuntu

Posted on 2009-04-13
Last Modified: 2013-11-21
Here's just another example of why Ubuntu wipes the floor with Windows:

I have a domain consisting of a domain controller running Windows SBS 2003, Terminal Services, etc., to which are connected approximately 30 Windows Vista Business workstations.

When I'm using Ubuntu, and I want to remote into any of those workstations, I just fire up Terminal Server Client, put in the name of the computer I want to remote into, my login credentials, and the domain IP address (x.x.x.x).  It takes me directly to the desktop of the client machine that I desire.

On Windows, however, I'm trying to do the same thing using the Remote Desktop Connection application, but it only gives me two options: "Computer" and "User name".  Nowhere does it allow me to specify the domain, so when I put my IP address into the "Computer" box, all it allows me to do is log into my small business server, not the actual clients.

This is getting pretty frustrating - I'm sure the Windows program would work, if it would allow me to put in the complete information like I can under Ubuntu, but it just doesn't have the necessary fields.  I've tried putting in things like "Computer: x.x.x.x\computer_name", and various other combinations using slashes, colons, etc., with no success.  This feels like a really dumb question, but how do I RDP connect to my clients?  I've been googling for hours with no success.  :-(

PS - I know I can access all the computers in my domain through the web by going to https://x.x.x.x/remote, but I want to be able to use the Remote Desktop Connection app to save credentials, settings, etc.

I will attach a screenshot, in case the above is confusing.
Question by:comptechmike
  • 5
  • 4
  • 2

Expert Comment

ID: 24131271
In Windows, under Computer:
type in the machine name\ip address. It's the same field as in ubuntu.

The domain, put under username. ie: domainname\username.

It's really that simple. RDP only uses the domain for user authentication to log into the machine

Accepted Solution

asawatzki earned 125 total points
ID: 24131278
In the username field try specifying the domain before the username.  Like\username or blahblah\username .  You shouldn't have to enter the domain name for the computer itself unless you want/need to use the FQDN for the computer to get to it.  

Expert Comment

ID: 24131298
to clarify, under computer: type in the ip address OR the machine name, not machine\ip
You may also need to fully qualify the machine name. ie: if it is called 'computer2' and the domain name is '' you should put ''

My hunch is your not fully qualifying the domain names
Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.


Author Comment

ID: 24131698

I've tried every combination of your suggestions, and just can't get it to work.

Typing just my single static IP address into the "Computer" box remotes me into the server, which is great, but not where I want to be (btw, if it matters - my router is configured to forward port 3389 to the server).

Typing computer_name.x.x.x.x (my ip address) gives me a "this computer can't connect to the remote computer, can't find remote computer, etc." error.

Note that when I use this under Ubuntu, I enter the following information into the fields:
Computer: the computer name
User name: my user name
Password: my password
Domain: my domain IP address (x.x.x.x), not my domain name

Using the above settings, I can remote into any machine on my small business network, as long as they are configured to accept incoming connections.  Windows just doesn't give me the same options.  :-(

Assisted Solution

Matkun earned 125 total points
ID: 24131893
under the computer field, either use the fully qualified computer_name or the ip address, not both.

I'm not sure what you mean by domain IP address. Do you mean the domain controller? Individual domain controllers are identified by ip addresses, but the domain is identified by the domain name, which is typically something like

If you want to test connectivity for RDP at all, open a command prompt and use the command: telnet machinename 3389

If the telnet command times out or the connection is denied, then you have a port/connectivity issue.

Author Comment

ID: 24132033
@asawatzki & Matkun:

I believe I have got this solved.  What a tricky, pain in the ass it was, though, and I used bits from both your responses.

Under new remote desktop connection, this is what I'm doing:

Computer: Computer_name
User name: x.x.x.x (domain ip address, the static address from my ISP to my router) \ user_name

Then I click connect, and it gives me a window asking if I trust this remote connection.  I say "connect", then I get a second window asking for my credentials.  From here I pick the third option, "Use another account", and put in the following:

User name: domain_name \ user_name
Password: password

From here, it does appear to work.  I've successfully logged into five of my different workstations this way.  It's critical to use the third option at that last window, otherwise it doesn't know what domain to log into.

I'm gonna try this from home tonight and confirm that it's working (since I made so many changes to my laptop here in the office, I don't know if I trust it anymore, lol), then will split up the points.  Thanks, guys!  :-)

Expert Comment

ID: 24132098
Good to hear you got it working. Btw: you can enter anything you want in user name. It's just what is copied/pasted in to the login window in your last step

Expert Comment

ID: 24132188
Great to hear that its working for you now.

Author Comment

ID: 24187121
As a side note, this didn't wind up working, after all.  It worked great from the office, inside the domain, but was a no-go outside of the office.  I'm going to close this question out because I don't have time to deal with it at this time, but I'd still like to hear a solution to using Remote Desktop Connection from outside the domain, so I can create auto-logging-in scripts, etc., and don't have to use the Remote Web Workplace through a web browser.  :-(

Maybe one of these days I'll get back to this project, but in the meantime RWW for my users, it is...

Author Closing Comment

ID: 31569589
See note from my last comment.  Both of these users provided good help, I just don't understand why Microsoft has to have such a crappy Remote Desktop Connection approach.  It looks like it would only work if each individual machine within my domain had it's own IP address on the Internet, instead of going through a router/NAT/small business server setup.  *sigh*

Author Comment

ID: 24187158
See note from my last comment.  Both of these users provided good help, I just don't understand why Microsoft has to have such a crappy Remote Desktop Connection approach.  It looks like it would only work if each individual machine within my domain had it's own IP address on the Internet, instead of going through a router/NAT/small business server setup.  *sigh*

Featured Post

Ransomware-A Revenue Bonanza for Service Providers

Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat.  The purpose of this eBook is to educate the reader about ransomware attacks.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Guacamole cut and paste issue 3 95
Can’t delete a file 14 178
Windows Server Backup failing on Windows Server 2016 Standard 2 75
tsadmin.msc on WIndows 2012 R2 4 187
Some time ago I faced the need to use a uniform folder structure that spanned across numerous sites of an enterprise to be used as a common repository for the Software packages of the Configuration Manager 2007 infrastructure. Because the procedu…
On July 14th 2015, Windows Server 2003 will become End of Support, leaving hundreds of thousands of servers around the world that still run this 12 year old operating system vulnerable and potentially out of compliance in many organisations around t…
Email security requires an ever evolving service that stays up to date with counter-evolving threats. The Email Laundry perform Research and Development to ensure their email security service evolves faster than cyber criminals. We apply our Threat…

789 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question