terminal server issue

cybersans · 18th January 2007

hello guys. i am a new user here.

lets go to the issue. i experience something when did windowsupdate on windows2000 using terminal server. when i do windowsupdate, and disconnect the terminal server session, and after that assuming windowsupdate installing all the updates selected, after that i try to connect back to the terminal server, it says that my password is incorrect. seems like windowsupdate change of disable logon through windowsupdate using the user that i used for logon before.

i hope you guys understand what i'm trying to tell. i just want to know whether windowsupdate change the password for logon using terminal server or what?

thank you

**Steve R Jones** · 18th January 2007

No the update didn't change the password.

But it did probably install the new RDC (remote desktop connection) software. When connecting you probably need to retype the computer name or IP whichever you use.

mflynn · 18th January 2007

Hello cybersans

Welcome to the best The Windows BBS.

Can't tell from your description of your problem. But I think it is on your end.

Just a note: I hope you didn't not just go to Win update and do it.

Terminal Server needs to be in "Install Mode" to do these things.

Any programs installed and windows update should be run from Add/Remove.

If done properly you will get a prompt to click Finish when finished if the install completed or not.

M$ has released RDP 6.0 (RDP from Vista) a few weeks ago via win update for XP 2K.

But in this case I believe on your end you recently downloaded RDP ver 6.0 which has many more config settings some of which are security settings, that require you to re-enter and save the password again on your end.

Well on second thought you now probably have it on the Terminal server also. Next chance I get I will check one of my clients 2K Terminal server and do the update and see if it does in fact update the RDP.

Will try to let you know!

I do know that it ups to RDP 6.0 on 2003 Server (not Terminal Server). But even here I will need to check one of my 2003 Terminal servers to see if it is updated on Terminal server or not.

Perhaps someone on the BBS has noticed.

Mike

cybersans · 19th January 2007

guys, thank you for the quick reply. i don't think the new "remote desktop client" caused this problem, it is because i try 2 windows 2000 server machine, the same way, updating using windowsupdate.microsoft.com from remote session (terminal server).

after i disconnect (while windowsupdate is downloading and updating on the remote machine) and after an hour, assuming that windowsupdate installation is complete and ask for restart, and when i try to remote back the machine, it says that my password is incorrect. and i try to use another username for authentication, it can. lets say i have user: administrator, ABC, DEF.
and i using ABC to remote the terminal server. i cannot connect back using user ABC (the user that i used for windowsupdate remotely), but can use administrator or DEF.

mflynn · 19th January 2007

OK that makes it clear what is happening. I understand now.

OK so answer this.

When does it let you back in under the original login and password?

After a reboot?

When you do get back in with the original login/password if you do not disconnect but log off properly. Does it give same problem when you try to connect again.

If it allows you to reconnect after a logoff (not disconnect) then there is a problem with the disconnect. This problem may show up in the event logs of the server.

If it is only on disconnects it may be a policy/restriction of having 2 logons of the same user/password. If a proper disconnection occured then you should be able to get back in. If a proper dissconnection did not occur then you are in fact trying to logon again as the same user for the 2nd time.

So answer the above:
1. what clears the error reboot...
2. does it work ok if a log off

Mike

cybersans · 22nd January 2007

mflynn: sorry for the late reply. yes you are right, the password for username that i used for remote the terminal server only can be used after rebooting.

If it is only on disconnects it may be a policy/restriction of having 2 logons of the same user/password. If a proper disconnection occured then you should be able to get back in. If a proper dissconnection did not occur then you are in fact trying to logon again as the same user for the 2nd time.

if there is limitation for only 2 logons per user, it will show an error like "too many user" or whatever.
but i get error "wrong password" which mean, the password is wrong. or is this one of windows 2000 "security feature" when updating using terminal server?

mflynn · 22nd January 2007

Hi Cyber

Clarify the below now that you have rebooted..

You logon do something and you logoff properly (not didconnect).

Can you then get back on?

Since reboot.

You logon do something then didconnect (not logoff).

Can you now get back on? If so it is not allowing you to reconnect to the disconnected session.

You should logon as another user and look at the status of the dissconected session.

Clarify the above and get back to us.

Mike