Remote Desktop timeout even though sessions set to Never

[jacksondorado]

I don't know why, but my clients' remote desktops disconnect very quickly if they do not use the screen for a few minutes. I have set the policy for Terminal Server Sessions to Never for Idle Session limit and Active Session limit.

Is there another policy I could set that would affect this?

 

[LaforcE]

I remember having the same trouble ...

And it was because it was set to do so at another place ... yes.

Check the Group wich the user belong to. If there is another policy applied to that group, they the more restrictif is appllied ... so check that out ...

Think you can also specified it in the AD on the user properties ... so check that out too ...

And my opinion, it is not a good thing to set Sessions to Never for Idle Session limit and Active Session limit. One for security reason, and two for the ressource took by a user if he forgot to log off before leaving to home.

I strongly suggest you to set it to a more long period of time, but leave a limit, like 2 hour ...

Good luck. Hope it helped.






- Security is a never ending job.

 

[jacksondorado]

I don't understand what you meant by "the more restrictif is applied"

What exact policy am I looking for in the user properties? I have no problem setting the limits to something reasonable. I had only been trying to fix the timeout problem.

Can you please re-state you suggstions? I don't quite understand what to try.

thanks.

 

[jacksondorado]

Oh, one other thing,

? Is there somewhere to configure the session timeout besides

Computer configuration > Admin Templates > Windows Components > Terminal Services > Sessions

and

User Configuration > Admin Templates > Windows Components > Terminal Services > Sessions

 

[LaforcE]

Ok, sry, english in not my first languague and somethimes, I dont make it clear enough

If you go in the active Directory, and you right click on the user to see his properties, check under "session", there is a setting there also ...

also check the Start menu| Programs| Admin Tools| Terminal Services Config| and then click on the properties of the RDP connector. Check under session youll see other setting there. Also check the server setting, the box under

Hope it help you out!
Later.

- Security is a never ending job.

 

[jacksondorado]

Thanks for the help. I set the Session to 1 day but it still disconnects automatically after a few minutes. I'm stuck. I have tried sending a help ticket to Microsoft but the automatic website submission tells me my product country and product ID do not match, which is not the case so I will try to call them.

thanks again.

 

[LaforcE]

Hummm your problem seems to be more a firewall or misrouting information issue than a terminal disconnection.

You should also check that out !!!
Any packet losts between the client and the server ?

Good luck!

- Security is a never ending job.

 

[jacksondorado]

Thanks!

The firewall had the setting that needed to be fixed. It had its' user service access timeout set to 5 minutes.

Thanks for helping me weed through to the solution!

 

[LaforcE]

Np you welcome ...

We are all here to help !

Good day.

- Security is a never ending job.