Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Remote Desktop 6.0 putting server name in front of user name

Posted on 2007-03-28
7
Medium Priority
?
310 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 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
Does Your Cloud Backup Use Blockchain Technology?

Blockchain technology has already revolutionized finance thanks to Bitcoin. Now it's disrupting other areas, including the realm of data protection. Learn how blockchain is now being used to authenticate backup files and keep them safe from hackers.

 
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 250 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

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

Question has a verified solution.

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

Have you considered what group policies are backwards and forwards compatible? Windows Active Directory servers and clients use group policy templates to deploy sets of policies within your domain. But, there is a catch to deploying policies. The…
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…
This tutorial will teach you the special effect of super speed similar to the fictional character Wally West aka "The Flash" After Shake : http://www.videocopilot.net/presets/after_shake/ All lightning effects with instructions : http://www.mediaf…
Want to learn how to record your desktop screen without having to use an outside camera. Click on this video and learn how to use the cool google extension called "Screencastify"! Step 1: Open a new google tab Step 2: Go to the left hand upper corn…

670 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