Remote Desktop 6.0 putting server name in front of user name

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
TimSr. System AdminAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

lnkevinCommented:
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
Rob WilliamsCommented:
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
TimSr. System AdminAuthor Commented:
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
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

Rob WilliamsCommented:
>"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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
TimSr. System AdminAuthor Commented:
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
Rob WilliamsCommented:
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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.