RDP changing user

[Guest]

I have a client that has two RDP sessions pointed to the same terminal
server. He uses a separate user ID for each session because the server
force-runs a specific app depending on which user ID he uses. However, when
he saves the user ID for Session #1, it also changes the user ID for session
#2 (i.e. they are always both the same). This happens even when I log onto
his PC as a domain admin, and it never happens on the other five computers in
the office that function the same way for their respective users.

In fact, when I delete the RDP session and attempt to create a new one, the
last-saved user name is already there. Is there a setting somewhere that
locks in all RDP sessions to a single user ID (or a registry hack to set it
back to the way it should be)? This is, of course, RDP client 6.0 that was
just released.

 

[Sooner Al [MVP]]

I have a client that has two RDP sessions pointed to the same terminal
server. He uses a separate user ID for each session because the server
force-runs a specific app depending on which user ID he uses. However,
when
he saves the user ID for Session #1, it also changes the user ID for
session
#2 (i.e. they are always both the same). This happens even when I log onto
his PC as a domain admin, and it never happens on the other five computers
in
the office that function the same way for their respective users.

In fact, when I delete the RDP session and attempt to create a new one,
the
last-saved user name is already there. Is there a setting somewhere that
locks in all RDP sessions to a single user ID (or a registry hack to set
it
back to the way it should be)? This is, of course, RDP client 6.0 that was
just released.

Brian,

I suggest you post this to the microsoft.public.windows.terminal_services
news group.

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...

 

[Guest]

Thanks. I will post there. However, I must note that this is the
workstation's problem, not the server's. All the other workstations in the
office function correctly. This one workstation seems to be able to handle
only a single reference to a particular terminal server for all remote
sessions saved. There must be something messed up in the registry.