Re: Terminal Services Client 6.0 Authentication

TP, I have a question about the saved credentials. The credentials
seem to be saved by *machine* not by RDP file.

In other words, if I want to create two RDP files to connect to the
same machine with two different sets of credentials it does not work.
Every time I changed the saved credentials in the one RDP file, it
changes them in the other file. This used to work. What am I doing
wrong?

TP wrote:
The new client can give roughly the same auth behavior as
the old client, it just works a little different on the front
end. You do not need the enablecredsspsupport option
that I discussed in a prior post:

http://groups.google.com/group/microsoft.public.windows.terminal_services/browse_frm/thread/7048672478cf3141/

I recommended that option because the poster specifically
asked for the old behavior and because he is using the
Novell client.

What behavior would you prefer, exactly?

When you run "mstsc [filename].rdp", would you like it to:

1.) Connect and log you in to your XP Pro machine, without
prompting for username/password at all?

2.) Connect to your XP Pro machine, but stop at the Log On
to Windows prompt, with your user name pre-filled and
the password box blank?

3.) Another option?

I am guessing you want option 2 above, please correct me if
I am wrong. Remove the enablecredsspsupport that you
added before.

In order to do this, you need to open up the client (manually, not
specifiying .rdp file) and connect to your XP Pro machine using
the same computer name stored in your .rdp file. When
prompted for your credentials, enter them exactly as you would
if you were entering them on your XP Pro machine, and check
the save password box.

After you have successfully connected, disconnect from
your XP Pro machine. Open up the client again, make sure
the computer name is still set to your XP Pro machine as used
above, and then click the edit credentials hyperlink. The
credentials screen should have your username as entered
above, with the password box blank. Click the OK button
to save your credentials, do *not* enter a password in the box.

Uncheck "Always ask for credentials". Optionally set all of your
connection preferences and then click the Save As button to
make a fresh .rdp file for this connection.

Click the Connect button. This time it should connect to your XP
Pro machine, but stop at the Log On to Windows screen with
the user name field pre-filled and the password blank. You
should have the same behavior if you use the rdp file as well.

Username and password are no longer stored in the .rdp
file.

Please let me know if you have any questions.

-TP

trev wrote:
I just installed TSC 6.0 on my WinXP Pro and WinXP MCE systems. I use
the MCE system to connect to the Pro system via RDP.

So far, all I've noticed in TSC 6.0 are new annoyances. For example,
I have always used RDP by running the command line "mstsc.exe [file
name].rdp". This always used to make the connection, and then go
right to a "Log On to Windows" dialog. But with TSC 6.0, I always
get a "Remote Desktop Connection" dialog first, and then still have
to enter the (same) credentials again on the "Log On to Windows"
dialog. What is the point to the "Remote Desktop Connection" dialog?

Also, on the "Remote Desktop Connection" dialog: Sometimes, the user
name is pre-filled as simply "User". Other times, it shows up as
"x.x.x.x\User", where x.x.x.x is the IP address. Still other times,
it appears as "User@xxxxxxx". This last case is especially
irritating, because the "User@xxxxxxx" carries over onto the "Log On
to Windows" dialog, where it causes authentication failure. So,
whenever this happens (which seems to be randomly, but often), I have
to manually edit the user name field on the "Log On to Windows"
dialog, changing it from "User@xxxxxxx" to "User". Annoying. Very.

Any info would be appreciated.

.