M
Miguel Sanchez Sanchez
Hi
We have a w2k domain with windows xp users. When a user had a problem, I
connected remotely to his session using the command "shadow console" from
the w2k server.
But I decided to install SP2 in users machines. With great surprise, I can't
do the remote connection, despite to use a domain administrator user to
connect, add this user to local remote desktops users, check group policy
about terminal server, check user' remote access properties in the Active
Directory, remote access allowed, remote assistance allowed, firewall
disabled. Everything seem to be right, but the following errors appear when
I try to connect:
shadow console /server ... : Error to open Terminal Server ...
query session /server: Error to open Terminal Server ... Error [5]: Denied
Access.
What is the reason of this change of behaviour after installing Windows XP
SP2?
We have a w2k domain with windows xp users. When a user had a problem, I
connected remotely to his session using the command "shadow console" from
the w2k server.
But I decided to install SP2 in users machines. With great surprise, I can't
do the remote connection, despite to use a domain administrator user to
connect, add this user to local remote desktops users, check group policy
about terminal server, check user' remote access properties in the Active
Directory, remote access allowed, remote assistance allowed, firewall
disabled. Everything seem to be right, but the following errors appear when
I try to connect:
shadow console /server ... : Error to open Terminal Server ...
query session /server: Error to open Terminal Server ... Error [5]: Denied
Access.
What is the reason of this change of behaviour after installing Windows XP
SP2?