I have been a bit puzzled by this so I am finally posting a question. I am
posting both here and in the SBS news group....hopefully the proper way!
Situation: SBS2003 Standard with a separate member server running Windows
Server 2003 R2 SP2. This machine was joined to the domain the "SBS2003
way". There are some 20 users who make use of the Terminal Server. Basic
applications installed [Office 2003 and their CRM-client (SysPro)] and all
are working fine. Terminal Server is locked down via GPO. Sessions are
disconnected after one hour of idle time and disconnected sessions can be
reestablished within one hour. Only one session at a time is allowed.
Issue: users complain - alot - that they are getting disconnected with great
frequency after a short period of time.
What we have done: initially the idle time was 15 minutes and the
reestablish time was 15 minutes. This has been modified two or three times
and currently sits at one hour. Issue remains. Looked at their NetGear
Firewall (which I suspect to be at least part of the problem) and noticed
that the "disconnect idle sessions" was set at 10 minutes. Changed that to
one hour. Issue remains.
Users are accessing the Terminal Server via RWW (SBS2003 cool feature) while
on the road with their Dell Laptops making use of the Verizon Wireless
Broadband Card. I suspect that this might also be playing a role.
How to turn 'suspicion' into 'confirmation'. Not sure where to look as far
as SBS2003 logging is concerned (IIS I would suspect...which is enabled).
I would really like to be able to go to them and tell them specifically what
the problem is and what we need to do to resolve it rather than tell them
that I suspect that this and/or that is the problem.
I would suggest you first test the RWW connection and see if that one times
out without connecting to the TS. If you see the same behavior you can
exclude the TS box as the problem.
My suspicion is that the Verizon card is the culprit so I would also suggest
to run a test from a reliable broadband connection.
--
Claus
"Cary W. Shultz" <cshultz@nospam.outsourceitcorp.com> wrote in message
news:eJnL7TJeIHA.5996@TK2MSFTNGP04.phx.gbl...
> Good morning!
>
> I have been a bit puzzled by this so I am finally posting a question. I
> am posting both here and in the SBS news group....hopefully the proper
> way!
>
> Situation: SBS2003 Standard with a separate member server running Windows
> Server 2003 R2 SP2. This machine was joined to the domain the "SBS2003
> way". There are some 20 users who make use of the Terminal Server. Basic
> applications installed [Office 2003 and their CRM-client (SysPro)] and all
> are working fine. Terminal Server is locked down via GPO. Sessions are
> disconnected after one hour of idle time and disconnected sessions can be
> reestablished within one hour. Only one session at a time is allowed.
>
> Issue: users complain - alot - that they are getting disconnected with
> great frequency after a short period of time.
>
> What we have done: initially the idle time was 15 minutes and the
> reestablish time was 15 minutes. This has been modified two or three
> times and currently sits at one hour. Issue remains. Looked at their
> NetGear Firewall (which I suspect to be at least part of the problem) and
> noticed that the "disconnect idle sessions" was set at 10 minutes.
> Changed that to one hour. Issue remains.
>
> Users are accessing the Terminal Server via RWW (SBS2003 cool feature)
> while on the road with their Dell Laptops making use of the Verizon
> Wireless Broadband Card. I suspect that this might also be playing a
> role.
>
> How to turn 'suspicion' into 'confirmation'. Not sure where to look as
> far as SBS2003 logging is concerned (IIS I would suspect...which is
> enabled).
>
> I would really like to be able to go to them and tell them specifically
> what the problem is and what we need to do to resolve it rather than tell
> them that I suspect that this and/or that is the problem.
>
> Thanks,
>
> Cary
>
>
>
>
>
Now, why did I not think about that? Thanks for the hint. Should have come
up with that one on my own. Too much thinking (not enough brains!).
Cary
PS. Do you speak German? Just an off-topic question.
"Claus" <cjobes@nova-tech.org> wrote in message
news:%23zTcTmKeIHA.5560@TK2MSFTNGP04.phx.gbl...
> Cary,
>
> I would suggest you first test the RWW connection and see if that one
> times out without connecting to the TS. If you see the same behavior you
> can exclude the TS box as the problem.
>
> My suspicion is that the Verizon card is the culprit so I would also
> suggest to run a test from a reliable broadband connection.
>
> --
> Claus
> "Cary W. Shultz" <cshultz@nospam.outsourceitcorp.com> wrote in message
> news:eJnL7TJeIHA.5996@TK2MSFTNGP04.phx.gbl...
>> Good morning!
>>
>> I have been a bit puzzled by this so I am finally posting a question. I
>> am posting both here and in the SBS news group....hopefully the proper
>> way!
>>
>> Situation: SBS2003 Standard with a separate member server running
>> Windows Server 2003 R2 SP2. This machine was joined to the domain the
>> "SBS2003 way". There are some 20 users who make use of the Terminal
>> Server. Basic applications installed [Office 2003 and their CRM-client
>> (SysPro)] and all are working fine. Terminal Server is locked down via
>> GPO. Sessions are disconnected after one hour of idle time and
>> disconnected sessions can be reestablished within one hour. Only one
>> session at a time is allowed.
>>
>> Issue: users complain - alot - that they are getting disconnected with
>> great frequency after a short period of time.
>>
>> What we have done: initially the idle time was 15 minutes and the
>> reestablish time was 15 minutes. This has been modified two or three
>> times and currently sits at one hour. Issue remains. Looked at their
>> NetGear Firewall (which I suspect to be at least part of the problem) and
>> noticed that the "disconnect idle sessions" was set at 10 minutes.
>> Changed that to one hour. Issue remains.
>>
>> Users are accessing the Terminal Server via RWW (SBS2003 cool feature)
>> while on the road with their Dell Laptops making use of the Verizon
>> Wireless Broadband Card. I suspect that this might also be playing a
>> role.
>>
>> How to turn 'suspicion' into 'confirmation'. Not sure where to look as
>> far as SBS2003 logging is concerned (IIS I would suspect...which is
>> enabled).
>>
>> I would really like to be able to go to them and tell them specifically
>> what the problem is and what we need to do to resolve it rather than tell
>> them that I suspect that this and/or that is the problem.
>>
>> Thanks,
>>
>> Cary
>>
>>
>>
>>
>>
>
>
Yes, I do speak German - need to concentrate a bit but it is still there.
--
Claus
"Cary W. Shultz" <cshultz@nospam.outsourceitcorp.com> wrote in message
news:ezZNP6KeIHA.4728@TK2MSFTNGP03.phx.gbl...
> Claus,
>
> Thanks. So, simply go to https://mail.mydomain.com/remote and enter
> credentials and sit and wait....
>
> Now, why did I not think about that? Thanks for the hint. Should have
> come up with that one on my own. Too much thinking (not enough brains!).
>
> Cary
>
> PS. Do you speak German? Just an off-topic question.
>
>
> "Claus" <cjobes@nova-tech.org> wrote in message
> news:%23zTcTmKeIHA.5560@TK2MSFTNGP04.phx.gbl...
>> Cary,
>>
>> I would suggest you first test the RWW connection and see if that one
>> times out without connecting to the TS. If you see the same behavior you
>> can exclude the TS box as the problem.
>>
>> My suspicion is that the Verizon card is the culprit so I would also
>> suggest to run a test from a reliable broadband connection.
>>
>> --
>> Claus
>> "Cary W. Shultz" <cshultz@nospam.outsourceitcorp.com> wrote in message
>> news:eJnL7TJeIHA.5996@TK2MSFTNGP04.phx.gbl...
>>> Good morning!
>>>
>>> I have been a bit puzzled by this so I am finally posting a question. I
>>> am posting both here and in the SBS news group....hopefully the proper
>>> way!
>>>
>>> Situation: SBS2003 Standard with a separate member server running
>>> Windows Server 2003 R2 SP2. This machine was joined to the domain the
>>> "SBS2003 way". There are some 20 users who make use of the Terminal
>>> Server. Basic applications installed [Office 2003 and their CRM-client
>>> (SysPro)] and all are working fine. Terminal Server is locked down via
>>> GPO. Sessions are disconnected after one hour of idle time and
>>> disconnected sessions can be reestablished within one hour. Only one
>>> session at a time is allowed.
>>>
>>> Issue: users complain - alot - that they are getting disconnected with
>>> great frequency after a short period of time.
>>>
>>> What we have done: initially the idle time was 15 minutes and the
>>> reestablish time was 15 minutes. This has been modified two or three
>>> times and currently sits at one hour. Issue remains. Looked at their
>>> NetGear Firewall (which I suspect to be at least part of the problem)
>>> and noticed that the "disconnect idle sessions" was set at 10 minutes.
>>> Changed that to one hour. Issue remains.
>>>
>>> Users are accessing the Terminal Server via RWW (SBS2003 cool feature)
>>> while on the road with their Dell Laptops making use of the Verizon
>>> Wireless Broadband Card. I suspect that this might also be playing a
>>> role.
>>>
>>> How to turn 'suspicion' into 'confirmation'. Not sure where to look as
>>> far as SBS2003 logging is concerned (IIS I would suspect...which is
>>> enabled).
>>>
>>> I would really like to be able to go to them and tell them specifically
>>> what the problem is and what we need to do to resolve it rather than
>>> tell them that I suspect that this and/or that is the problem.
>>>
>>> Thanks,
>>>
>>> Cary
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
Great....I do as well. But in the same boat as you. Anyway, thanks for the
tip again. This issue has become critical and your tip is proving to be
quite useful.
Thanks again,
Cary
"Claus" <cjobes@nova-tech.org> wrote in message
news:eSC%23etLeIHA.5552@TK2MSFTNGP06.phx.gbl...
> Cary,
>
> Yes, I do speak German - need to concentrate a bit but it is still there.
>
> --
> Claus
> "Cary W. Shultz" <cshultz@nospam.outsourceitcorp.com> wrote in message
> news:ezZNP6KeIHA.4728@TK2MSFTNGP03.phx.gbl...
>> Claus,
>>
>> Thanks. So, simply go to https://mail.mydomain.com/remote and enter
>> credentials and sit and wait....
>>
>> Now, why did I not think about that? Thanks for the hint. Should have
>> come up with that one on my own. Too much thinking (not enough brains!).
>>
>> Cary
>>
>> PS. Do you speak German? Just an off-topic question.
>>
>>
>> "Claus" <cjobes@nova-tech.org> wrote in message
>> news:%23zTcTmKeIHA.5560@TK2MSFTNGP04.phx.gbl...
>>> Cary,
>>>
>>> I would suggest you first test the RWW connection and see if that one
>>> times out without connecting to the TS. If you see the same behavior you
>>> can exclude the TS box as the problem.
>>>
>>> My suspicion is that the Verizon card is the culprit so I would also
>>> suggest to run a test from a reliable broadband connection.
>>>
>>> --
>>> Claus
>>> "Cary W. Shultz" <cshultz@nospam.outsourceitcorp.com> wrote in message
>>> news:eJnL7TJeIHA.5996@TK2MSFTNGP04.phx.gbl...
>>>> Good morning!
>>>>
>>>> I have been a bit puzzled by this so I am finally posting a question.
>>>> I am posting both here and in the SBS news group....hopefully the
>>>> proper way!
>>>>
>>>> Situation: SBS2003 Standard with a separate member server running
>>>> Windows Server 2003 R2 SP2. This machine was joined to the domain the
>>>> "SBS2003 way". There are some 20 users who make use of the Terminal
>>>> Server. Basic applications installed [Office 2003 and their CRM-client
>>>> (SysPro)] and all are working fine. Terminal Server is locked down via
>>>> GPO. Sessions are disconnected after one hour of idle time and
>>>> disconnected sessions can be reestablished within one hour. Only one
>>>> session at a time is allowed.
>>>>
>>>> Issue: users complain - alot - that they are getting disconnected with
>>>> great frequency after a short period of time.
>>>>
>>>> What we have done: initially the idle time was 15 minutes and the
>>>> reestablish time was 15 minutes. This has been modified two or three
>>>> times and currently sits at one hour. Issue remains. Looked at their
>>>> NetGear Firewall (which I suspect to be at least part of the problem)
>>>> and noticed that the "disconnect idle sessions" was set at 10 minutes.
>>>> Changed that to one hour. Issue remains.
>>>>
>>>> Users are accessing the Terminal Server via RWW (SBS2003 cool feature)
>>>> while on the road with their Dell Laptops making use of the Verizon
>>>> Wireless Broadband Card. I suspect that this might also be playing a
>>>> role.
>>>>
>>>> How to turn 'suspicion' into 'confirmation'. Not sure where to look as
>>>> far as SBS2003 logging is concerned (IIS I would suspect...which is
>>>> enabled).
>>>>
>>>> I would really like to be able to go to them and tell them specifically
>>>> what the problem is and what we need to do to resolve it rather than
>>>> tell them that I suspect that this and/or that is the problem.
>>>>
>>>> Thanks,
>>>>
>>>> Cary
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
--
Claus
"Cary W. Shultz" <cshultz@nospam.outsourceitcorp.com> wrote in message
news:ufiNI5LeIHA.4196@TK2MSFTNGP04.phx.gbl...
> Claus,
>
> Great....I do as well. But in the same boat as you. Anyway, thanks for
> the tip again. This issue has become critical and your tip is proving to
> be quite useful.
>
> Thanks again,
>
> Cary
>
>
> "Claus" <cjobes@nova-tech.org> wrote in message
> news:eSC%23etLeIHA.5552@TK2MSFTNGP06.phx.gbl...
>> Cary,
>>
>> Yes, I do speak German - need to concentrate a bit but it is still there.
>>
>> --
>> Claus
>> "Cary W. Shultz" <cshultz@nospam.outsourceitcorp.com> wrote in message
>> news:ezZNP6KeIHA.4728@TK2MSFTNGP03.phx.gbl...
>>> Claus,
>>>
>>> Thanks. So, simply go to https://mail.mydomain.com/remote and enter
>>> credentials and sit and wait....
>>>
>>> Now, why did I not think about that? Thanks for the hint. Should have
>>> come up with that one on my own. Too much thinking (not enough
>>> brains!).
>>>
>>> Cary
>>>
>>> PS. Do you speak German? Just an off-topic question.
>>>
>>>
>>> "Claus" <cjobes@nova-tech.org> wrote in message
>>> news:%23zTcTmKeIHA.5560@TK2MSFTNGP04.phx.gbl...
>>>> Cary,
>>>>
>>>> I would suggest you first test the RWW connection and see if that one
>>>> times out without connecting to the TS. If you see the same behavior
>>>> you can exclude the TS box as the problem.
>>>>
>>>> My suspicion is that the Verizon card is the culprit so I would also
>>>> suggest to run a test from a reliable broadband connection.
>>>>
>>>> --
>>>> Claus
>>>> "Cary W. Shultz" <cshultz@nospam.outsourceitcorp.com> wrote in message
>>>> news:eJnL7TJeIHA.5996@TK2MSFTNGP04.phx.gbl...
>>>>> Good morning!
>>>>>
>>>>> I have been a bit puzzled by this so I am finally posting a question.
>>>>> I am posting both here and in the SBS news group....hopefully the
>>>>> proper way!
>>>>>
>>>>> Situation: SBS2003 Standard with a separate member server running
>>>>> Windows Server 2003 R2 SP2. This machine was joined to the domain the
>>>>> "SBS2003 way". There are some 20 users who make use of the Terminal
>>>>> Server. Basic applications installed [Office 2003 and their
>>>>> CRM-client (SysPro)] and all are working fine. Terminal Server is
>>>>> locked down via GPO. Sessions are disconnected after one hour of idle
>>>>> time and disconnected sessions can be reestablished within one hour.
>>>>> Only one session at a time is allowed.
>>>>>
>>>>> Issue: users complain - alot - that they are getting disconnected with
>>>>> great frequency after a short period of time.
>>>>>
>>>>> What we have done: initially the idle time was 15 minutes and the
>>>>> reestablish time was 15 minutes. This has been modified two or three
>>>>> times and currently sits at one hour. Issue remains. Looked at their
>>>>> NetGear Firewall (which I suspect to be at least part of the problem)
>>>>> and noticed that the "disconnect idle sessions" was set at 10 minutes.
>>>>> Changed that to one hour. Issue remains.
>>>>>
>>>>> Users are accessing the Terminal Server via RWW (SBS2003 cool feature)
>>>>> while on the road with their Dell Laptops making use of the Verizon
>>>>> Wireless Broadband Card. I suspect that this might also be playing a
>>>>> role.
>>>>>
>>>>> How to turn 'suspicion' into 'confirmation'. Not sure where to look
>>>>> as far as SBS2003 logging is concerned (IIS I would suspect...which is
>>>>> enabled).
>>>>>
>>>>> I would really like to be able to go to them and tell them
>>>>> specifically what the problem is and what we need to do to resolve it
>>>>> rather than tell them that I suspect that this and/or that is the
>>>>> problem.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Cary
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Cary W. Shultz wrote:
>Issue: users complain - alot - that they are getting disconnected with
>great frequency after a short period of time.
Do they tick the option on the RWW logon page that says "this is a private
computer"? RWW by design has a short timeout for "public" computers, and a
longer one for "private" computers.
--
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.
I can not answer that. I have advised them to do this, but you know how end
users can be. ;-)
I changed the time for both (PublicTimeOut and PrivateTimeOut) to 120
minutes, as this is what the client wants (against my recommendation).
Thanks,
Cary
"Steve Foster [SBS MVP]" <steve.foster@picamar.co.uk> wrote in message
news:xn0fmxm7r2qdu21002@msnews.microsoft.com...
> Cary W. Shultz wrote:
>
>>Issue: users complain - alot - that they are getting disconnected with
>>great frequency after a short period of time.
>
> Do they tick the option on the RWW logon page that says "this is a private
> computer"? RWW by design has a short timeout for "public" computers, and a
> longer one for "private" computers.
>
> --
> Steve Foster [SBS MVP]
> ---------------------------------------
> MVPs do not work for Microsoft. Please reply only to the newsgroups.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.