Logon Timer Expired error.

  • Thread starter Thread starter GW
  • Start date Start date
G

GW

Guest
Hi

We are running Windows 2003 Terminal server with a Windows 2008 domain
controller, which we recently moved from 2003 SBS server, migrating
the Windows accoounts across as we went.

At present, certain remote users are getting the following error
message when they log on -

Logon timer expired, session has now exceeded it's time limit.
Logoff with start in 2 minutes. Save all your files now.

So far I have checked the logon time restrictions which are set to 24
hour access in Active Directory, and have also checked the Active
Session Limit in the Terminal Services Configuration, which currently
set to Never.

Can anyone suggest anything that may cause the problem, and if so, how
to resolve it ?

Many thanks

GW
 
RE: Logon Timer Expired error.

This setting can be activated in different places.
Try RSoP to double check if there is a policy that overridde this specific
setting.
 
Re: Logon Timer Expired error.

Hi GW,

Since yesterday I experience the same problem overhere. I have a
windows 2008 domain and have 5 windows 2003 Terminal Servers.
Some users get the message "Logoff with start in 2 minutes. Save all
your filesnow". Most users do not get a message and can work as
usual...
I getting stuck here, so maybe there is someone that can help...

kind regards,

Maikiemaik

On Jul 7, 3:01 pm, GW <premc...@hotmail.com> wrote:
> Hi
>
> We are running Windows 2003 Terminal server with a Windows 2008 domain
> controller, which we recently moved from 2003 SBS server, migrating
> the Windows accoounts across as we went.
>
> At present, certain remote users are getting the following error
> message when they log on -
>
> Logontimerexpired,sessionhasnowexceededit'stimelimit.
> Logoff with start in 2 minutes. Save all your filesnow.
>
> So far I have checked thelogontimerestrictions which are set to 24
> hour access in Active Directory, and have also checked the ActiveSessionLimitin the Terminal Services Configuration, which currently
> set to Never.
>
> Can anyone suggest anything that may cause the problem, and if so, how
> to resolve it ?
>
> Many thanks
>
> GW
 
Back
Top