Remote desktop: Problems reconnecting to an existing session.

[Guest s7b@americancentury.com]

Good afternoon,

We are having a persistent issue with Remote Desktop at our company.

I have only recently been asked to help with this issue, but it has

been happening for around a year.

The symptoms are as follows:

 

A user locks their machine and later tries to remote in (either from

home or from within the same building/network)

They put in the computer name and click OK.

They reach the target machine and are prompted from their password.

They put in their password and click ok.

The dialogue box goes gray, as though it is about to proceed to the

Desktop.

The box stays gray for 10 seconds or so, and the just goes away. No

error message.

I see no events created in the Application or System logs while the

issue is occurring.

I do see an event in the Security log, stating that the login was

successful. (Success Audit for the users ID, event ID 528, and a

Success Audit 576 immediately afterword) The next event is a

successful logoff, event id 538.

If a user with Admin right remotes to the machine, they are able to

force the original user off.

Once that is done the original user can remote in successfully.

All machines are running Windows XP SP3 with updates applied monthly.

We have had the same issue with both NVidia and ATI Video cards.

Some machines are running multiple displays, some have a single

monitor.

All machines are Dells, Including GX270s, GX280s, GX620s and GX745s.

All machine have at least 2 gigs of RAM.

 

We have tried adding the problem user to the Administrator group,

which had no effect.

We have tried setting the TS and RDP services on the target machine to

Restart after first failure, which had no effect.

We have monitored the machines resourse utilization. The machines are

not running out of memory or processor.

Some of these machines have 4 gigs of RAM. They still have the issue.

We have had some success with having the users close some of their

more memory intensive application before they leave. Although this

does seem to work, it is really just a workaround. We would like to

discover the root cause and deliver a solid fix.

Please let me know if there is any other information that I could post

to provide more data.

I appreciate any help that anyone can provide! (especially you Vera :)

[Guest Vera Noest [MVP]]

Re: Remote desktop: Problems reconnecting to an existing session.

 

Yes, I do have some more questions:

* are you sure about XP SP3? and if so, did the issue also exist

under SP1 and SP2?

* which version of the rdp client are both the host and the client

machines running?

* does the issue also occur when the host is *not* locked?

* does the issue also occur when you configure the screensaver to

not need a password (I just assume that it needs one now)?

* and when you disable the screensaver alltogether?

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

s7b@americancentury.com wrote on 21 feb 2008 in

microsoft.public.windows.terminal_services:

> Good afternoon,

> We are having a persistent issue with Remote Desktop at our

> company. I have only recently been asked to help with this

> issue, but it has been happening for around a year.

> The symptoms are as follows:

>

> A user locks their machine and later tries to remote in (either

> from home or from within the same building/network)

> They put in the computer name and click OK.

> They reach the target machine and are prompted from their

> password. They put in their password and click ok.

> The dialogue box goes gray, as though it is about to proceed to

> the Desktop.

> The box stays gray for 10 seconds or so, and the just goes away.

> No error message.

> I see no events created in the Application or System logs while

> the issue is occurring.

> I do see an event in the Security log, stating that the login

> was successful. (Success Audit for the users ID, event ID 528,

> and a Success Audit 576 immediately afterword) The next event

> is a successful logoff, event id 538.

> If a user with Admin right remotes to the machine, they are able

> to force the original user off.

> Once that is done the original user can remote in successfully.

> All machines are running Windows XP SP3 with updates applied

> monthly. We have had the same issue with both NVidia and ATI

> Video cards. Some machines are running multiple displays, some

> have a single monitor.

> All machines are Dells, Including GX270s, GX280s, GX620s and

> GX745s. All machine have at least 2 gigs of RAM.

>

> We have tried adding the problem user to the Administrator

> group, which had no effect.

> We have tried setting the TS and RDP services on the target

> machine to Restart after first failure, which had no effect.

> We have monitored the machines resourse utilization. The

> machines are not running out of memory or processor.

> Some of these machines have 4 gigs of RAM. They still have the

> issue. We have had some success with having the users close

> some of their more memory intensive application before they

> leave. Although this does seem to work, it is really just a

> workaround. We would like to discover the root cause and

> deliver a solid fix. Please let me know if there is any other

> information that I could post to provide more data.

> I appreciate any help that anyone can provide! (especially you

> Vera :)

[Guest s7b@americancentury.com]

Re: Remote desktop: Problems reconnecting to an existing session.

 

On Feb 21, 2:19 pm, s...@americancentury.com wrote:

> Good afternoon,

> We are having a persistent issue with Remote Desktop at our company.

> I have only recently been asked to help with this issue, but it has

> been happening for around a year.

> The symptoms are as follows:

>

> A user locks their machine and later tries to remote in (either from

> home or from within the same building/network)

> They put in the computer name and click OK.

> They reach the target machine and are prompted from their password.

> They put in their password and click ok.

> The dialogue box goes gray, as though it is about to proceed to the

> Desktop.

> The box stays gray for 10 seconds or so, and the just goes away. No

> error message.

> I see no events created in the Application or System logs while the

> issue is occurring.

> I do see an event in the Security log, stating that the login was

> successful. (Success Audit for the users ID, event ID 528, and a

> Success Audit 576 immediately afterword)  The next event is a

> successful logoff, event id 538.

> If a user with Admin right remotes to the machine, they are able to

> force the original user off.

> Once that is done the original user can remote in successfully.

> All machines are running Windows XP SP3 with updates applied monthly.

> We have had the same issue with both NVidia and ATI Video cards.

> Some machines are running multiple displays, some have a single

> monitor.

> All machines are Dells, Including GX270s, GX280s, GX620s and GX745s.

> All machine have at least 2 gigs of RAM.

>

> We have tried adding the problem user to the Administrator group,

> which had no effect.

> We have tried setting the TS and RDP services on the target machine to

> Restart after first failure, which had no effect.

> We have monitored the machines resourse utilization. The machines are

> not running out of memory or processor.

> Some of these machines have 4 gigs of RAM.  They still have the issue.

> We have had some success with  having the users close some of their

> more memory intensive application before they leave.  Although this

> does seem to work, it is really just a workaround.  We would like to

> discover the root cause and deliver a solid fix.

> Please let me know if there is any other information that I could post

> to provide more data.

> I appreciate any help that anyone can provide! (especially you Vera :)

 

Hi Vera, Thanks for responding.

Question 1) We are running Windows XP SP2. No one here is on SP3.

(sorry for the typo

Question 2) We have seen this issue on both 5.x clients and 6.0

clients.Some of the machines have 5.x, some have 6.0.

Question 3) I have not been able to test whether or not unlocking the

workstation locally would then allow the user to get in. The issue is

imtermittent. (of course we don't hear from them if it works).

The users are sometimes on the road (coming in through either Citrix

or SSLVPN) somtimes in the same building, and sometimes at one of our

branch offices, which are WAN connected. It doesn' appear to matter

what version of the client or where you are connecting from.

Question 4) I have not thought to test this.I am sure I can have a

user or two excluded from our domain policy for testing . I can try

one user with no password and one with no screensaver.

 

Thanks again for you help.

I will try your suggestions.

Please post any other thoughts you may have.

 

I will post the results the screensaver/password tests.

[Guest s7b@americancentury.com]

Re: Remote desktop: Problems reconnecting to an existing session.

 

On Feb 21, 6:58 pm, s...@americancentury.com wrote:

> On Feb 21, 2:19 pm, s...@americancentury.com wrote:

>

>

>

>

>

> > Good afternoon,

> > We are having a persistent issue with Remote Desktop at our company.

> > I have only recently been asked to help with this issue, but it has

> > been happening for around a year.

> > The symptoms are as follows:

>

> > A user locks their machine and later tries to remote in (either from

> > home or from within the same building/network)

> > They put in the computer name and click OK.

> > They reach the target machine and are prompted from their password.

> > They put in their password and click ok.

> > The dialogue box goes gray, as though it is about to proceed to the

> > Desktop.

> > The box stays gray for 10 seconds or so, and the just goes away. No

> > error message.

> > I see no events created in the Application or System logs while the

> > issue is occurring.

> > I do see an event in the Security log, stating that the login was

> > successful. (Success Audit for the users ID, event ID 528, and a

> > Success Audit 576 immediately afterword)  The next event is a

> > successful logoff, event id 538.

> > If a user with Admin right remotes to the machine, they are able to

> > force the original user off.

> > Once that is done the original user can remote in successfully.

> > All machines are running Windows XP SP3 with updates applied monthly.

> > We have had the same issue with both NVidia and ATI Video cards.

> > Some machines are running multiple displays, some have a single

> > monitor.

> > All machines are Dells, Including GX270s, GX280s, GX620s and GX745s.

> > All machine have at least 2 gigs of RAM.

>

> > We have tried adding the problem user to the Administrator group,

> > which had no effect.

> > We have tried setting the TS and RDP services on the target machine to

> > Restart after first failure, which had no effect.

> > We have monitored the machines resourse utilization. The machines are

> > not running out of memory or processor.

> > Some of these machines have 4 gigs of RAM.  They still have the issue.

> > We have had some success with  having the users close some of their

> > more memory intensive application before they leave.  Although this

> > does seem to work, it is really just a workaround.  We would like to

> > discover the root cause and deliver a solid fix.

> > Please let me know if there is any other information that I could post

> > to provide more data.

> > I appreciate any help that anyone can provide! (especially you Vera :)

>

> Hi Vera, Thanks for responding.

> Question 1)  We are running Windows XP SP2. No one here is on SP3.

> (sorry for the typo

> Question 2)  We have seen this issue on both 5.x clients and 6.0

> clients.Some of the machines have 5.x, some have 6.0.

> Question 3)  I have not been able to test whether or not unlocking the

> workstation locally would then allow the user to get in. The issue is

> imtermittent. (of course we don't hear from them if it works).

> The users are sometimes on the road (coming in through either Citrix

> or SSLVPN) somtimes in the same building, and sometimes at one of our

> branch offices, which are WAN connected. It doesn' appear to matter

> what version of the client or where you are connecting from.

> Question 4) I have not thought to test this.I am sure I can have a

> user or two excluded from our domain policy for testing . I can try

> one user with no password and one with no screensaver.

>

> Thanks again for you help.

> I will try your suggestions.

> Please post any other thoughts you may have.

>

> I will post the results the screensaver/password tests.- Hide quoted text -

>

> - Show quoted text -

 

 

Vera, FYI, a user called me this morning and was experiencing the

issue. I killed the screensaver remotely, so the machine was still

locked, but the screensaver was no longer active. He still could not

get in.

As stated previously, he gets these events in this order.

Event ID 528 (successful logon) ->

Event ID 576 (Special priviledges assigned to new logon)

Event ID 682 (Session reconnected to winstation)

Event ID 538 (User logoff)

 

I am working on getting the screensaver policy temporarily removed

from one of the users.

If that does resolve the issue then what is next? Obviously I can't

leave the user out of our screensave policy for security reasons.

[Guest s7b@americancentury.com]

Re: Remote desktop: Problems reconnecting to an existing session.

 

On Feb 22, 9:31 am, s...@americancentury.com wrote:

> On Feb 21, 6:58 pm, s...@americancentury.com wrote:

>

>

>

>

>

> > On Feb 21, 2:19 pm, s...@americancentury.com wrote:

>

> > > Good afternoon,

> > > We are having a persistent issue with Remote Desktop at our company.

> > > I have only recently been asked to help with this issue, but it has

> > > been happening for around a year.

> > > The symptoms are as follows:

>

> > > A user locks their machine and later tries to remote in (either from

> > > home or from within the same building/network)

> > > They put in the computer name and click OK.

> > > They reach the target machine and are prompted from their password.

> > > They put in their password and click ok.

> > > The dialogue box goes gray, as though it is about to proceed to the

> > > Desktop.

> > > The box stays gray for 10 seconds or so, and the just goes away. No

> > > error message.

> > > I see no events created in the Application or System logs while the

> > > issue is occurring.

> > > I do see an event in the Security log, stating that the login was

> > > successful. (Success Audit for the users ID, event ID 528, and a

> > > Success Audit 576 immediately afterword)  The next event is a

> > > successful logoff, event id 538.

> > > If a user with Admin right remotes to the machine, they are able to

> > > force the original user off.

> > > Once that is done the original user can remote in successfully.

> > > All machines are running Windows XP SP3 with updates applied monthly.

> > > We have had the same issue with both NVidia and ATI Video cards.

> > > Some machines are running multiple displays, some have a single

> > > monitor.

> > > All machines are Dells, Including GX270s, GX280s, GX620s and GX745s.

> > > All machine have at least 2 gigs of RAM.

>

> > > We have tried adding the problem user to the Administrator group,

> > > which had no effect.

> > > We have tried setting the TS and RDP services on the target machine to

> > > Restart after first failure, which had no effect.

> > > We have monitored the machines resourse utilization. The machines are

> > > not running out of memory or processor.

> > > Some of these machines have 4 gigs of RAM.  They still have the issue.

> > > We have had some success with  having the users close some of their

> > > more memory intensive application before they leave.  Although this

> > > does seem to work, it is really just a workaround.  We would like to

> > > discover the root cause and deliver a solid fix.

> > > Please let me know if there is any other information that I could post

> > > to provide more data.

> > > I appreciate any help that anyone can provide! (especially you Vera :)

>

> > Hi Vera, Thanks for responding.

> > Question 1)  We are running Windows XP SP2. No one here is on SP3.

> > (sorry for the typo

> > Question 2)  We have seen this issue on both 5.x clients and 6.0

> > clients.Some of the machines have 5.x, some have 6.0.

> > Question 3)  I have not been able to test whether or not unlocking the

> > workstation locally would then allow the user to get in. The issue is

> > imtermittent. (of course we don't hear from them if it works).

> > The users are sometimes on the road (coming in through either Citrix

> > or SSLVPN) somtimes in the same building, and sometimes at one of our

> > branch offices, which are WAN connected. It doesn' appear to matter

> > what version of the client or where you are connecting from.

> > Question 4) I have not thought to test this.I am sure I can have a

> > user or two excluded from our domain policy for testing . I can try

> > one user with no password and one with no screensaver.

>

> > Thanks again for you help.

> > I will try your suggestions.

> > Please post any other thoughts you may have.

>

> > I will post the results the screensaver/password tests.- Hide quoted text -

>

> > - Show quoted text -

>

> Vera, FYI, a user called me this morning and was experiencing the

> issue.  I killed the screensaver remotely, so the machine was still

> locked, but the screensaver was no longer active.  He still could not

> get in.

> As stated previously, he gets these events in this order.

> Event ID 528 (successful logon) ->

> Event ID 576 (Special priviledges assigned to new logon)

> Event ID 682 (Session reconnected to winstation)

> Event ID 538 (User logoff)

>

> I am working on getting the screensaver policy temporarily removed

> from one of the users.

> If that does resolve the issue then what is next? Obviously I can't

> leave the user out of our screensave policy for security reasons.- Hide quoted text -

>

> - Show quoted text -

 

I am still waiting for results from my test of the screensaver

password theory. Anything esle anyone could add would be appreciated.

[Guest s7b@americancentury.com]

Re: Remote desktop: Problems reconnecting to an existing session.

 

On Feb 25, 10:30 am, s...@americancentury.com wrote:

> On Feb 22, 9:31 am, s...@americancentury.com wrote:

>

>

>

>

>

> > On Feb 21, 6:58 pm, s...@americancentury.com wrote:

>

> > > On Feb 21, 2:19 pm, s...@americancentury.com wrote:

>

> > > > Good afternoon,

> > > > We are having a persistent issue with Remote Desktop at our company.

> > > > I have only recently been asked to help with this issue, but it has

> > > > been happening for around a year.

> > > > The symptoms are as follows:

>

> > > > A user locks their machine and later tries to remote in (either from

> > > > home or from within the same building/network)

> > > > They put in the computer name and click OK.

> > > > They reach the target machine and are prompted from their password.

> > > > They put in their password and click ok.

> > > > The dialogue box goes gray, as though it is about to proceed to the

> > > > Desktop.

> > > > The box stays gray for 10 seconds or so, and the just goes away. No

> > > > error message.

> > > > I see no events created in the Application or System logs while the

> > > > issue is occurring.

> > > > I do see an event in the Security log, stating that the login was

> > > > successful. (Success Audit for the users ID, event ID 528, and a

> > > > Success Audit 576 immediately afterword)  The next event is a

> > > > successful logoff, event id 538.

> > > > If a user with Admin right remotes to the machine, they are able to

> > > > force the original user off.

> > > > Once that is done the original user can remote in successfully.

> > > > All machines are running Windows XP SP3 with updates applied monthly..

> > > > We have had the same issue with both NVidia and ATI Video cards.

> > > > Some machines are running multiple displays, some have a single

> > > > monitor.

> > > > All machines are Dells, Including GX270s, GX280s, GX620s and GX745s.

> > > > All machine have at least 2 gigs of RAM.

>

> > > > We have tried adding the problem user to the Administrator group,

> > > > which had no effect.

> > > > We have tried setting the TS and RDP services on the target machine to

> > > > Restart after first failure, which had no effect.

> > > > We have monitored the machines resourse utilization. The machines are

> > > > not running out of memory or processor.

> > > > Some of these machines have 4 gigs of RAM.  They still have the issue.

> > > > We have had some success with  having the users close some of their

> > > > more memory intensive application before they leave.  Although this

> > > > does seem to work, it is really just a workaround.  We would like to

> > > > discover the root cause and deliver a solid fix.

> > > > Please let me know if there is any other information that I could post

> > > > to provide more data.

> > > > I appreciate any help that anyone can provide! (especially you Vera :)

>

> > > Hi Vera, Thanks for responding.

> > > Question 1)  We are running Windows XP SP2. No one here is on SP3.

> > > (sorry for the typo

> > > Question 2)  We have seen this issue on both 5.x clients and 6.0

> > > clients.Some of the machines have 5.x, some have 6.0.

> > > Question 3)  I have not been able to test whether or not unlocking the

> > > workstation locally would then allow the user to get in. The issue is

> > > imtermittent. (of course we don't hear from them if it works).

> > > The users are sometimes on the road (coming in through either Citrix

> > > or SSLVPN) somtimes in the same building, and sometimes at one of our

> > > branch offices, which are WAN connected. It doesn' appear to matter

> > > what version of the client or where you are connecting from.

> > > Question 4) I have not thought to test this.I am sure I can have a

> > > user or two excluded from our domain policy for testing . I can try

> > > one user with no password and one with no screensaver.

>

> > > Thanks again for you help.

> > > I will try your suggestions.

> > > Please post any other thoughts you may have.

>

> > > I will post the results the screensaver/password tests.- Hide quoted text -

>

> > > - Show quoted text -

>

> > Vera, FYI, a user called me this morning and was experiencing the

> > issue.  I killed the screensaver remotely, so the machine was still

> > locked, but the screensaver was no longer active.  He still could not

> > get in.

> > As stated previously, he gets these events in this order.

> > Event ID 528 (successful logon) ->

> > Event ID 576 (Special priviledges assigned to new logon)

> > Event ID 682 (Session reconnected to winstation)

> > Event ID 538 (User logoff)

>

> > I am working on getting the screensaver policy temporarily removed

> > from one of the users.

> > If that does resolve the issue then what is next? Obviously I can't

> > leave the user out of our screensave policy for security reasons.- Hide quoted text -

>

> > - Show quoted text -

>

> I am still waiting for results from my test of the screensaver

> password theory.  Anything esle anyone could add would be appreciated.- Hide quoted text -

>

> - Show quoted text -

 

The No Screensaver setting had no effect.

[Guest CTC G]

Re: Remote desktop: Problems reconnecting to an existing session.

 

Has any information been found about this? I am having the very same trouble

with users getting "you do not have access to this session."

 

 

"s7b@americancentury.com" wrote:

> On Feb 25, 10:30 am, s...@americancentury.com wrote:

> > On Feb 22, 9:31 am, s...@americancentury.com wrote:

> >

> >

> >

> >

> >

> > > On Feb 21, 6:58 pm, s...@americancentury.com wrote:

> >

> > > > On Feb 21, 2:19 pm, s...@americancentury.com wrote:

> >

> > > > > Good afternoon,

> > > > > We are having a persistent issue with Remote Desktop at our company.

> > > > > I have only recently been asked to help with this issue, but it has

> > > > > been happening for around a year.

> > > > > The symptoms are as follows:

> >

> > > > > A user locks their machine and later tries to remote in (either from

> > > > > home or from within the same building/network)

> > > > > They put in the computer name and click OK.

> > > > > They reach the target machine and are prompted from their password.

> > > > > They put in their password and click ok.

> > > > > The dialogue box goes gray, as though it is about to proceed to the

> > > > > Desktop.

> > > > > The box stays gray for 10 seconds or so, and the just goes away. No

> > > > > error message.

> > > > > I see no events created in the Application or System logs while the

> > > > > issue is occurring.

> > > > > I do see an event in the Security log, stating that the login was

> > > > > successful. (Success Audit for the users ID, event ID 528, and a

> > > > > Success Audit 576 immediately afterword) The next event is a

> > > > > successful logoff, event id 538.

> > > > > If a user with Admin right remotes to the machine, they are able to

> > > > > force the original user off.

> > > > > Once that is done the original user can remote in successfully.

> > > > > All machines are running Windows XP SP3 with updates applied monthly..

> > > > > We have had the same issue with both NVidia and ATI Video cards.

> > > > > Some machines are running multiple displays, some have a single

> > > > > monitor.

> > > > > All machines are Dells, Including GX270s, GX280s, GX620s and GX745s.

> > > > > All machine have at least 2 gigs of RAM.

> >

> > > > > We have tried adding the problem user to the Administrator group,

> > > > > which had no effect.

> > > > > We have tried setting the TS and RDP services on the target machine to

> > > > > Restart after first failure, which had no effect.

> > > > > We have monitored the machines resourse utilization. The machines are

> > > > > not running out of memory or processor.

> > > > > Some of these machines have 4 gigs of RAM. They still have the issue.

> > > > > We have had some success with having the users close some of their

> > > > > more memory intensive application before they leave. Although this

> > > > > does seem to work, it is really just a workaround. We would like to

> > > > > discover the root cause and deliver a solid fix.

> > > > > Please let me know if there is any other information that I could post

> > > > > to provide more data.

> > > > > I appreciate any help that anyone can provide! (especially you Vera :)

> >

> > > > Hi Vera, Thanks for responding.

> > > > Question 1) We are running Windows XP SP2. No one here is on SP3.

> > > > (sorry for the typo

> > > > Question 2) We have seen this issue on both 5.x clients and 6.0

> > > > clients.Some of the machines have 5.x, some have 6.0.

> > > > Question 3) I have not been able to test whether or not unlocking the

> > > > workstation locally would then allow the user to get in. The issue is

> > > > imtermittent. (of course we don't hear from them if it works).

> > > > The users are sometimes on the road (coming in through either Citrix

> > > > or SSLVPN) somtimes in the same building, and sometimes at one of our

> > > > branch offices, which are WAN connected. It doesn' appear to matter

> > > > what version of the client or where you are connecting from.

> > > > Question 4) I have not thought to test this.I am sure I can have a

> > > > user or two excluded from our domain policy for testing . I can try

> > > > one user with no password and one with no screensaver.

> >

> > > > Thanks again for you help.

> > > > I will try your suggestions.

> > > > Please post any other thoughts you may have.

> >

> > > > I will post the results the screensaver/password tests.- Hide quoted text -

> >

> > > > - Show quoted text -

> >

> > > Vera, FYI, a user called me this morning and was experiencing the

> > > issue. I killed the screensaver remotely, so the machine was still

> > > locked, but the screensaver was no longer active. He still could not

> > > get in.

> > > As stated previously, he gets these events in this order.

> > > Event ID 528 (successful logon) ->

> > > Event ID 576 (Special priviledges assigned to new logon)

> > > Event ID 682 (Session reconnected to winstation)

> > > Event ID 538 (User logoff)

> >

> > > I am working on getting the screensaver policy temporarily removed

> > > from one of the users.

> > > If that does resolve the issue then what is next? Obviously I can't

> > > leave the user out of our screensave policy for security reasons.- Hide quoted text -

> >

> > > - Show quoted text -

> >

> > I am still waiting for results from my test of the screensaver

> > password theory. Anything esle anyone could add would be appreciated.- Hide quoted text -

> >

> > - Show quoted text -

>

> The No Screensaver setting had no effect.

>

>

[Guest Ratnesh Yadav [MSFT]]

Re: Remote desktop: Problems reconnecting to an existing session.

 

Check following link,

http://support.microsoft.com/kb/246109

 

Ratnesh

 

"CTC G" <CTC G@discussions.microsoft.com> wrote in message

news:CE322D9A-B50F-49A4-811C-AAE8D246EDE0@microsoft.com...

> Has any information been found about this? I am having the very same

> trouble

> with users getting "you do not have access to this session."

>

>

> "s7b@americancentury.com" wrote:

>

>> On Feb 25, 10:30 am, s...@americancentury.com wrote:

>> > On Feb 22, 9:31 am, s...@americancentury.com wrote:

>> >

>> >

>> >

>> >

>> >

>> > > On Feb 21, 6:58 pm, s...@americancentury.com wrote:

>> >

>> > > > On Feb 21, 2:19 pm, s...@americancentury.com wrote:

>> >

>> > > > > Good afternoon,

>> > > > > We are having a persistent issue with Remote Desktop at our

>> > > > > company.

>> > > > > I have only recently been asked to help with this issue, but it

>> > > > > has

>> > > > > been happening for around a year.

>> > > > > The symptoms are as follows:

>> >

>> > > > > A user locks their machine and later tries to remote in (either

>> > > > > from

>> > > > > home or from within the same building/network)

>> > > > > They put in the computer name and click OK.

>> > > > > They reach the target machine and are prompted from their

>> > > > > password.

>> > > > > They put in their password and click ok.

>> > > > > The dialogue box goes gray, as though it is about to proceed to

>> > > > > the

>> > > > > Desktop.

>> > > > > The box stays gray for 10 seconds or so, and the just goes away.

>> > > > > No

>> > > > > error message.

>> > > > > I see no events created in the Application or System logs while

>> > > > > the

>> > > > > issue is occurring.

>> > > > > I do see an event in the Security log, stating that the login was

>> > > > > successful. (Success Audit for the users ID, event ID 528, and a

>> > > > > Success Audit 576 immediately afterword) The next event is a

>> > > > > successful logoff, event id 538.

>> > > > > If a user with Admin right remotes to the machine, they are able

>> > > > > to

>> > > > > force the original user off.

>> > > > > Once that is done the original user can remote in successfully.

>> > > > > All machines are running Windows XP SP3 with updates applied

>> > > > > monthly..

>> > > > > We have had the same issue with both NVidia and ATI Video cards.

>> > > > > Some machines are running multiple displays, some have a single

>> > > > > monitor.

>> > > > > All machines are Dells, Including GX270s, GX280s, GX620s and

>> > > > > GX745s.

>> > > > > All machine have at least 2 gigs of RAM.

>> >

>> > > > > We have tried adding the problem user to the Administrator group,

>> > > > > which had no effect.

>> > > > > We have tried setting the TS and RDP services on the target

>> > > > > machine to

>> > > > > Restart after first failure, which had no effect.

>> > > > > We have monitored the machines resourse utilization. The machines

>> > > > > are

>> > > > > not running out of memory or processor.

>> > > > > Some of these machines have 4 gigs of RAM. They still have the

>> > > > > issue.

>> > > > > We have had some success with having the users close some of

>> > > > > their

>> > > > > more memory intensive application before they leave. Although

>> > > > > this

>> > > > > does seem to work, it is really just a workaround. We would like

>> > > > > to

>> > > > > discover the root cause and deliver a solid fix.

>> > > > > Please let me know if there is any other information that I could

>> > > > > post

>> > > > > to provide more data.

>> > > > > I appreciate any help that anyone can provide! (especially you

>> > > > > Vera :)

>> >

>> > > > Hi Vera, Thanks for responding.

>> > > > Question 1) We are running Windows XP SP2. No one here is on SP3.

>> > > > (sorry for the typo

>> > > > Question 2) We have seen this issue on both 5.x clients and 6.0

>> > > > clients.Some of the machines have 5.x, some have 6.0.

>> > > > Question 3) I have not been able to test whether or not unlocking

>> > > > the

>> > > > workstation locally would then allow the user to get in. The issue

>> > > > is

>> > > > imtermittent. (of course we don't hear from them if it works).

>> > > > The users are sometimes on the road (coming in through either

>> > > > Citrix

>> > > > or SSLVPN) somtimes in the same building, and sometimes at one of

>> > > > our

>> > > > branch offices, which are WAN connected. It doesn' appear to matter

>> > > > what version of the client or where you are connecting from.

>> > > > Question 4) I have not thought to test this.I am sure I can have a

>> > > > user or two excluded from our domain policy for testing . I can try

>> > > > one user with no password and one with no screensaver.

>> >

>> > > > Thanks again for you help.

>> > > > I will try your suggestions.

>> > > > Please post any other thoughts you may have.

>> >

>> > > > I will post the results the screensaver/password tests.- Hide

>> > > > quoted text -

>> >

>> > > > - Show quoted text -

>> >

>> > > Vera, FYI, a user called me this morning and was experiencing the

>> > > issue. I killed the screensaver remotely, so the machine was still

>> > > locked, but the screensaver was no longer active. He still could not

>> > > get in.

>> > > As stated previously, he gets these events in this order.

>> > > Event ID 528 (successful logon) ->

>> > > Event ID 576 (Special priviledges assigned to new logon)

>> > > Event ID 682 (Session reconnected to winstation)

>> > > Event ID 538 (User logoff)

>> >

>> > > I am working on getting the screensaver policy temporarily removed

>> > > from one of the users.

>> > > If that does resolve the issue then what is next? Obviously I can't

>> > > leave the user out of our screensave policy for security reasons.-

>> > > Hide quoted text -

>> >

>> > > - Show quoted text -

>> >

>> > I am still waiting for results from my test of the screensaver

>> > password theory. Anything esle anyone could add would be appreciated.-

>> > Hide quoted text -

>> >

>> > - Show quoted text -

>>

>> The No Screensaver setting had no effect.

>>

>>