I thought this was controlled with Connection Authorization Policies, with
the Remote Desktop Gateway Manager tool.  You should be able to manipulate
the timeout values as well as enable silent re-authorization - so you avoid
clients from getting that message.

YMMV: It's been a while, and I could be misreading or applying my notes on
the subject.

--
Espi


On Tue, May 9, 2017 at 9:11 PM, Bill Humphries <[email protected]> wrote:

> Wouldn’t it just disconnect the session if that was the case, rather than
> provide the message below?
>
>
>
> *From:* [email protected] [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *Michael B. Smith
> *Sent:* Tuesday, May 9, 2017 11:00 AM
> *To:* [email protected]
> *Subject:* [NTSysADM] RE: RDS timeout issues
>
>
>
> Just guessing, but I would take a look at the remote router and/or
> firewall to see if it has TCP timeouts configured.
>
>
>
> *From:* [email protected] [mailto:listsadmin@lists.
> myitforum.com <[email protected]>] *On Behalf Of *Bill
> Humphries
> *Sent:* Tuesday, May 9, 2017 9:12 AM
> *To:* [email protected]
> *Subject:* [NTSysADM] RDS timeout issues
>
>
>
> Hi all,
>
>
>
> I am once again, seeking wisdom from the group.
>
>
>
> I have a single RDS server running on 2012 R2 for a client.  Most users
> are in local office and connect to the RDS session on LAN.  A few users are
> remote.  We are using TSPrint as a printing solution because  users need to
> be able to print to each other’s local printers, even if they are in
> different locations.  To allow this printing, the user must be logged into
> the RDS server so that other users can print to the local printer.
>
>
>
> I have two users that are at a location in a different state.  These
> users’ remote sessions keep ending with “Your remote desktop services
> session has ended because the remote computer didn’t receive any input from
> you.”  I need this to not happen so that the printers remain available.  No
> one else complains about the time out issue.
>
>
>
> On the RDS server I have gone to:
>
>    - *Computer Configuration\Policies\Administrative Templates\Windows
>    Components\Remote Desktop Services\Remote Desktop Session Host\Session Time
>    Limits*
>    - *User Configuration\Policies\Administrative Templates\Windows
>    Components\Remote Desktop Services\Remote Desktop Session Host\Session Time
>    Limits*
>
> And set time out limits to never.  But these two users still get
> disconnected.  I do not manage the user PCs on the other end, but my
> understanding is that timeout limits would be managed at the RDS, not at
> the client computer.
>
>
>
> Any help is much appreciated.
>
>
>
> Bill
>
>
>

Reply via email to