Re: saving password in rdp file

You can get the version from inside the rdp client.
Click in the small icon at the left hand side of the rdp client's
title bar. In the system menu, click "About" to see the version.

Where *exactly* are the rdp files stored? What's the search path to
them?
Do the users have roaming profiles?

Can you try if you can reproduce the problem by starting
connections from different workstations, with different OS + rdp
client version?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

"Greg Hubers" <greg.hubers@xxxxxxxxxxxxx> wrote on 20 nov 2006:

Hi Vera,
Yes there are different O/S's and different versions of the rdp
client in use. I'm not sure how to tell the versions of the rdp
client software. The only O/S that I have to load the client
rdp software is on my Win2k boxes, WinXP is built in. The O/S's
are WinXP and Win2k but all the clients are able to set/save the
password. The client computer remains the same, they don't try
to use the .rdp file from a different computer. It makes sense
to me that someone wouldn't be able to fire up the .rdp file
from another computer. But nothing here is changing on the
client side. It just simply works for a while and then stops
working.
It's difficult to troubleshoot as well since I can not
reproduce the
problem. I just have to wait until it decides to loose the
password because I can't figure out what would be doing that.
Could it have anything to do with group policies on the domain?
I am not a domain admin. I simply work in a small group with a
Win2003 server and workstations that are all on the larger
novell/windows network. "Vera Noest [MVP]"
<vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:Xns9881DD5564F8Averanoesthemutforsse@xxxxxxxxxxxxxxxx
This behaviour (password works only on same client) is by
design. For security reasons, the password is encrypted in such
a way that only the same user on the same client can decrypt
and use it.

But that doesn't explain your main problem, that the password
in the rdp file works for a couple of weeks and then suddenly
stops working.
The user account is the same, I assume?

Not all versions of the rdp client can save passwords at all.
Are your users using different versions of the rdp client, on
different client OS versions? I haven't tested it, but maybe
their password gets lost when they use an older version on some
machines?
_________________________________________________________ Vera
Noest MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Greg Hubers" <greg.hubers@xxxxxxxxxxxxx> wrote on 20 nov 2006
in microsoft.public.windows.terminal_services:

The same type of problem occurs if I copied the .RDP file to
another computer. The password is no longer saved. That is
why I created the .RDP file from the client computers. But
the password only works for a few weeks at most. So it seems
like the .RDP file is not recognizing the client for some
reason after a certain amount of time. I'm not heavily into
how the security works for the whole thing...

"Greg Hubers" <greg.hubers@xxxxxxxxxxxxx> wrote in message
news:4561c9d1$0$61929$815e3792@xxxxxxxxxxxxxxxxx
Hi Vera,
Thanks for the post. Actually this has nothing to do with
changed passwords as far as I can tell. I create an RDP file
from the client machine using a user name and password that
are local to the Win2003 box and save it with the password
saved. The domain selected is the name of the local TS box.
It works great for a few weeks and then out of the blue it
stops working and the RDP file no longer contains the
password and the save password box is unchecked. I have
tried changing the network passwords (novell and windows)
with no effect on the RDP file working. It still works fine.
I can not figure out why the password dissapears. The
happens with every client O/S and ts client software that I
have tried. The RDP file simply will not hold the password in
it for some reason. To be honest it's a real drag, because
now I have to give all users and administrative account with
a password. So much for trying to be secure with a microsoft
product :(


"Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message
news:Xns987F88236A6F5veranoesthemutforsse@xxxxxxxxxxxxxxxx
This will always happen when users change their password,
because the rdp file still contains the old password.
So after a password change the login box will show up, and
users will have to type in the new password and then save
the new settings, overwriting the old rdp file.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Greg Hubers" <greg.hubers@xxxxxxxxxxxxx> wrote on 18 nov
2006 in microsoft.public.windows.terminal_services:

Oh btw, I forgot to mention...
The clients and the Windows 2003 server box all have a
novell client running.

"Greg Hubers" <greg.hubers@xxxxxxxxxxxxx> wrote in message
news:455e5a9d$0$10306$815e3792@xxxxxxxxxxxxxxxxx
Windows 2003 TS sessions:
When I create an RDP file and have the save password box
checked it works fine for a while but every few weeks it
looses the password and prompts the user to login. I have
been unable to reproduce anything that causes this problem
so I'm not sure what is causing it. I have even tried
making the RDP files read only. I need to have the clients
have their own profiles/user directories but do not want
to have them log in with a user id and password. I want
this to happen automatically via RDP file. Any idea what
is causing the RDP files to lose the password?
The clients are using Win2000 Pro and WinXP Pro.
.

Relevant Pages

  • Re: Cant connect RDP to Windows 2003 server?
    ... Then I'd uninstall the rdp 6.0 client again. ... Vera Noest ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • Re: Printing to a TCP/IP printer
    ... update to RDP 5.2. ... > The remote Windows XP client can print to this printer, ... > MCSE, CCEA, Microsoft MVP - Terminal Server ... >> to other IP's at the remote site. ...
    (microsoft.public.win2000.termserv.clients)
  • Re: RDP 6 Does not work
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Since CredSSP only exists as of Vista and RDP 6.0, ... specific .RDP file to launch the connection to your server, ... If you are manually opening the Remote Desktop Client using ...
    (microsoft.public.windows.terminal_services)
  • Re: RDP 6 Does not work
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Since CredSSP only exists as of Vista and RDP 6.0, ... specific .RDP file to launch the connection to your server, ... If you are manually opening the Remote Desktop Client using ...
    (microsoft.public.windows.terminal_services)
  • Re: Is this setup possible to redirect client printer ?
    ... The Client printer driver exists on the terminal server ... The Terminal Server Fallback Printer Driver is enabled via GPO ... Example RDP File ... or if you're launching and ICA session ...
    (microsoft.public.windows.terminal_services)