Solved

Remote Desktop 6.0 putting server name in front of user name

Posted on 2007-03-28
7
285 Views
Last Modified: 2013-11-21
I have remote desktop 6.0  installed on all my XP Pro machines that are on my network and when the user uses remote desktop to access our terminal server their user name has the server name in front of their user name in the user field. I would like to know how to make it so the server name is not in front of the user name or at least put the domain name in front of the user name. With the server name being in front of the user name it makes the user log on locally to the server and if the user does not have rights to log onto that server locally it denies their login.

Thanks,

Tim
0
Comment
Question by:tparus
  • 4
  • 2
7 Comments
 
LVL 26

Expert Comment

by:lnkevin
ID: 18811268
From the server, right click on my computer --> Remote Tab--> Select Remote Users--> Add Users
You can add as many users as you want. Plus, to have access to the server locally you need to modify Group Policy Object, if you don't have GPO, you need to modify your local policy:

program--> administrative tools--> local sec policy --> security option--> logon locally -->add users group


K
0
 
LVL 77

Expert Comment

by:Rob Williams
ID: 18812562
An irritating function of the ver 6.0 client is to add the server name, or IP address in some cases, in front of the user name by default. It is recommended the user now fill in the domainname\username in the initial RD connection box, when connecting. If the connection is successful, the next time the user connects it will fill it in automatically, when connecting to the same server.
If the user does not put the domain name in the initial RD connection box, you will get a failed connection (no message to this effect) and another logon box appears where you have to "fix" it. This is the box where it adds the computer name or IP. Changing here will allow you to connect but the connection information will not be saved for next logon.
0
 

Author Comment

by:tparus
ID: 18812605
That would work if I had a windows 2003 server but my terminal server is a 2000 machine. I probably should have said that in the beginning. I do have a group policy for this server by I do not see the choice to log on locally.
0
What Is Threat Intelligence?

Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.

 
LVL 77

Expert Comment

by:Rob Williams
ID: 18812644
>"That would work if I had a windows 2003 server "
Ah yes <G>
Log on locally is not recommended from a security point of view, plus they would then not be logging onto the domain.

Not the answer you want, but you could un-install the ver 6.00 client and go back to the old one.
0
 
LVL 77

Accepted Solution

by:
Rob Williams earned 125 total points
ID: 18812704
0
 

Author Comment

by:tparus
ID: 18844660
So I guess there is no way around this problem. After reading the above article is states to always add either the domain name then the user name to log on to a terminal server. Unfortunately, my users aren't that savvy so it looks like I will have to uninstall 6.0 until they get this authentication thing figured out. Reduicuous, Microsoft thinks they are making things better but they only make it better for the administrator and not the user. As an administrator I don't have this problem but my common users do.

Thanks for the help Rob.

Tim
0
 
LVL 77

Expert Comment

by:Rob Williams
ID: 18844700
The new client is really designed for use with Vista and Longhorn, with the new "TS Gateway Server" feature, though it works well with XP and 2003. You are likely right, from a simplicity point of view you are probably best to continue to use the old client. MS no longer supports 2000, so best to stick with the products that were designed for it. There is no real security advantage for 2000 users to switch to the new client anyway.
Cheers! and thanks,
--Rob
0

Featured Post

The curse of the end user strikes again      

You’ve updated all your end user’s email signatures. Hooray! But guess what? They’re playing around with the HTML, adding stupid taglines and ruining the imagery. Find out how you can save your signatures from end users today.

Join & Write a Comment

The environment that this is running in is SCCM 2007 R2 running on a Windows 2008 R2 server. The PXE Distribution point is running on its own Windows 2008 R2 box. This is what Event viewer showed after trying to start the WDS service:  An erro…
Remote Apps is a feature in server 2008 which allows users to run applications off Remote Desktop Servers without having to log into them to run the applications.  The user can either have a desktop shortcut installed or go through the web portal to…
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…

708 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

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now