|
|
Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
I have a an issue with clients who RWW into the server then on to the client
computers. Everything works fine but after a while, while still active on
the connection, they get disconnected. I have looked into the logs but I
don't see any reason for this to happen.
Any thoughts on the issue or how to diagnose?
Thanks!
-Richard K
|
|
Richard K wrote:
[Quoted Text] > I have a an issue with clients who RWW into the server then on to the
> client computers. Everything works fine but after a while, while
> still active on the connection, they get disconnected. I have looked
> into the logs but I don't see any reason for this to happen.
>
> Any thoughts on the issue or how to diagnose?
>
> Thanks!
>
> -Richard K
Could be a connectivity connection between remote workstation and the SBS
server, or the SBS server and the internal workstations.
Need more detail. Is this just one SBS instance with just one user from just
one location, or a broader problem?
--
/kj
|
|
This happens in all scenerios (different locations, users, client computers)
so it is not an internet connection issue. Is there something in SBS that
would be timing out after a period of non-activity that could be doing this?
"kj" wrote:
[Quoted Text] > Richard K wrote:
> > I have a an issue with clients who RWW into the server then on to the
> > client computers. Everything works fine but after a while, while
> > still active on the connection, they get disconnected. I have looked
> > into the logs but I don't see any reason for this to happen.
> >
> > Any thoughts on the issue or how to diagnose?
> >
> > Thanks!
> >
> > -Richard K
>
> Could be a connectivity connection between remote workstation and the SBS
> server, or the SBS server and the internal workstations.
>
> Need more detail. Is this just one SBS instance with just one user from just
> one location, or a broader problem?
>
> --
> /kj
>
>
>
|
|
Richard K wrote:
[Quoted Text] > This happens in all scenerios (different locations, users, client
> computers) so it is not an internet connection issue. Is there
> something in SBS that would be timing out after a period of
> non-activity that could be doing this?
>
> "kj" wrote:
There are timeout values for INactivity. I understood your connections were
active.
The default values for RWW session timeout are 10 Minutes on a shared/public
computer connected to RWW and 60 Minutes on a nonshared/nonpublic computer.
Is this what you are refering?
>
>> Richard K wrote:
>>> I have a an issue with clients who RWW into the server then on to
>>> the client computers. Everything works fine but after a while,
>>> while still active on the connection, they get disconnected. I
>>> have looked into the logs but I don't see any reason for this to
>>> happen.
>>>
>>> Any thoughts on the issue or how to diagnose?
>>>
>>> Thanks!
>>>
>>> -Richard K
>>
>> Could be a connectivity connection between remote workstation and
>> the SBS server, or the SBS server and the internal workstations.
>>
>> Need more detail. Is this just one SBS instance with just one user
>> from just one location, or a broader problem?
>>
>> --
>> /kj
--
/kj
|
|
On May 29, 1:17 pm, Richard K <Richa...[ at ]discussions.microsoft.com>
wrote:
[Quoted Text] > I have a an issue with clients who RWW into the server then on to the client
> computers. Everything works fine but after a while, while still active on
> the connection, they get disconnected. I have looked into the logs but I
> don't see any reason for this to happen.
>
> Any thoughts on the issue or how to diagnose?
>
> Thanks!
>
> -Richard K
Richard,
Be sure to check timeout settings for any piece of equipment you have
along the way. For instance, I have a Sonicwall router that has it's
own default inactivity disconnect setting as well as an inactivity
setting for every access rule I created on it. I believe the default
was originally 5 minutes.
|
|
Yes that is what I was looking for but....
1. How can I change those default values to see if that will fix the problem?
2. I have one more piece of info to add. In testing myself I also lost the
connection but I also get a message box stating
VBScript: Remote Desktop Disconnected (in title bar)
An Internal error has occured. (in the msg box)
"kj" wrote:
[Quoted Text] > Richard K wrote:
> > This happens in all scenerios (different locations, users, client
> > computers) so it is not an internet connection issue. Is there
> > something in SBS that would be timing out after a period of
> > non-activity that could be doing this?
> >
> > "kj" wrote:
>
> There are timeout values for INactivity. I understood your connections were
> active.
>
> The default values for RWW session timeout are 10 Minutes on a shared/public
> computer connected to RWW and 60 Minutes on a nonshared/nonpublic computer.
> Is this what you are refering?
>
> >
> >> Richard K wrote:
> >>> I have a an issue with clients who RWW into the server then on to
> >>> the client computers. Everything works fine but after a while,
> >>> while still active on the connection, they get disconnected. I
> >>> have looked into the logs but I don't see any reason for this to
> >>> happen.
> >>>
> >>> Any thoughts on the issue or how to diagnose?
> >>>
> >>> Thanks!
> >>>
> >>> -Richard K
> >>
> >> Could be a connectivity connection between remote workstation and
> >> the SBS server, or the SBS server and the internal workstations.
> >>
> >> Need more detail. Is this just one SBS instance with just one user
> >> from just one location, or a broader problem?
> >>
> >> --
> >> /kj
>
> --
> /kj
>
>
>
|
|
Richard K wrote:
[Quoted Text] > Yes that is what I was looking for but....
>
> 1. How can I change those default values to see if that will fix the
> problem?
> 2. I have one more piece of info to add. In testing myself I also
> lost the connection but I also get a message box stating
>
> VBScript: Remote Desktop Disconnected (in title bar)
> An Internal error has occured. (in the msg box)
Were you then disconnected from the RWW page or only the remote workstation
RDP session?
The values are registry entries but should be set at realistic values.
Extending beyond 60 min for an idle session should be very carefully
considered.
>
>
> "kj" wrote:
>
>> Richard K wrote:
>>> This happens in all scenerios (different locations, users, client
>>> computers) so it is not an internet connection issue. Is there
>>> something in SBS that would be timing out after a period of
>>> non-activity that could be doing this?
>>>
>>> "kj" wrote:
>>
>> There are timeout values for INactivity. I understood your
>> connections were active.
>>
>> The default values for RWW session timeout are 10 Minutes on a
>> shared/public computer connected to RWW and 60 Minutes on a
>> nonshared/nonpublic computer. Is this what you are refering?
>>
>>>
>>>> Richard K wrote:
>>>>> I have a an issue with clients who RWW into the server then on to
>>>>> the client computers. Everything works fine but after a while,
>>>>> while still active on the connection, they get disconnected. I
>>>>> have looked into the logs but I don't see any reason for this to
>>>>> happen.
>>>>>
>>>>> Any thoughts on the issue or how to diagnose?
>>>>>
>>>>> Thanks!
>>>>>
>>>>> -Richard K
>>>>
>>>> Could be a connectivity connection between remote workstation and
>>>> the SBS server, or the SBS server and the internal workstations.
>>>>
>>>> Need more detail. Is this just one SBS instance with just one user
>>>> from just one location, or a broader problem?
>>>>
>>>> --
>>>> /kj
>>
>> --
>> /kj
--
/kj
|
|
On May 29, 3:44 pm, "kj" <k...[ at ]nowhere.com> wrote:
[Quoted Text] > Richard K wrote:
> > Yes that is what I was looking for but....
>
> > 1. How can I change those default values to see if that will fix the
> > problem?
> > 2. I have one more piece of info to add. In testing myself I also
> > lost the connection but I also get a message box stating
>
> > VBScript: Remote Desktop Disconnected (in title bar)
> > An Internal error has occured. (in the msg box)
>
> Were you then disconnected from the RWW page or only the remote workstation
> RDP session?
>
> The values are registry entries but should be set at realistic values.
> Extending beyond 60 min for an idle session should be very carefully
> considered.
>
>
>
>
>
>
>
> > "kj" wrote:
>
> >> Richard K wrote:
> >>> This happens in all scenerios (different locations, users, client
> >>> computers) so it is not an internet connection issue. Is there
> >>> something in SBS that would be timing out after a period of
> >>> non-activity that could be doing this?
>
> >>> "kj" wrote:
>
> >> There are timeout values for INactivity. I understood your
> >> connections were active.
>
> >> The default values for RWW session timeout are 10 Minutes on a
> >> shared/public computer connected to RWW and 60 Minutes on a
> >> nonshared/nonpublic computer. Is this what you are refering?
>
> >>>> Richard K wrote:
> >>>>> I have a an issue with clients who RWW into the server then on to
> >>>>> the client computers. Everything works fine but after a while,
> >>>>> while still active on the connection, they get disconnected. I
> >>>>> have looked into the logs but I don't see any reason for this to
> >>>>> happen.
>
> >>>>> Any thoughts on the issue or how to diagnose?
>
> >>>>> Thanks!
>
> >>>>> -Richard K
>
> >>>> Could be a connectivity connection between remote workstation and
> >>>> the SBS server, or the SBS server and the internal workstations.
>
> >>>> Need more detail. Is this just one SBS instance with just one user
> >>>> from just one location, or a broader problem?
>
> >>>> --
> >>>> /kj
>
> >> --
> >> /kj
>
> --
> /kj- Hide quoted text -
>
> - Show quoted text
Ok, this is probably not the way to jump in, but I have had the same
issue intermittently for a while. It's not due to inactivity settings
- occasionally that VB error pops up and the session drops. The user
(or me, in some instances) is still logged into the RD session, but
dropped from RWW.
Logging back into RWW, the user can reconnect with their session, but
this gets *really* annoying.
Everything that I have seen seems to indicate a temporarily broken
connection between the remote location and the server.
Are there any additional troubleshooting steps recommended that would
be helpful?
Thanks again!
|
|
ATG wrote:
[Quoted Text] > On May 29, 3:44 pm, "kj" <k...[ at ]nowhere.com> wrote:
>> Richard K wrote:
>>> Yes that is what I was looking for but....
>>
>>> 1. How can I change those default values to see if that will fix
>>> the problem?
>>> 2. I have one more piece of info to add. In testing myself I also
>>> lost the connection but I also get a message box stating
>>
>>> VBScript: Remote Desktop Disconnected (in title bar)
>>> An Internal error has occured. (in the msg box)
>>
>> Were you then disconnected from the RWW page or only the remote
>> workstation RDP session?
>>
>> The values are registry entries but should be set at realistic
>> values. Extending beyond 60 min for an idle session should be very
>> carefully considered.
>>
>>
>>
>>
>>
>>
>>
>>> "kj" wrote:
>>
>>>> Richard K wrote:
>>>>> This happens in all scenerios (different locations, users, client
>>>>> computers) so it is not an internet connection issue. Is there
>>>>> something in SBS that would be timing out after a period of
>>>>> non-activity that could be doing this?
>>
>>>>> "kj" wrote:
>>
>>>> There are timeout values for INactivity. I understood your
>>>> connections were active.
>>
>>>> The default values for RWW session timeout are 10 Minutes on a
>>>> shared/public computer connected to RWW and 60 Minutes on a
>>>> nonshared/nonpublic computer. Is this what you are refering?
>>
>>>>>> Richard K wrote:
>>>>>>> I have a an issue with clients who RWW into the server then on
>>>>>>> to the client computers. Everything works fine but after a
>>>>>>> while, while still active on the connection, they get
>>>>>>> disconnected. I have looked into the logs but I don't see any
>>>>>>> reason for this to happen.
>>
>>>>>>> Any thoughts on the issue or how to diagnose?
>>
>>>>>>> Thanks!
>>
>>>>>>> -Richard K
>>
>>>>>> Could be a connectivity connection between remote workstation and
>>>>>> the SBS server, or the SBS server and the internal workstations.
>>
>>>>>> Need more detail. Is this just one SBS instance with just one
>>>>>> user from just one location, or a broader problem?
>>
>>>>>> --
>>>>>> /kj
>>
>>>> --
>>>> /kj
>>
>> --
>> /kj- Hide quoted text -
>>
>> - Show quoted text
>
>
>
> Ok, this is probably not the way to jump in, but I have had the same
> issue intermittently for a while. It's not due to inactivity settings
> - occasionally that VB error pops up and the session drops. The user
> (or me, in some instances) is still logged into the RD session, but
> dropped from RWW.
> Logging back into RWW, the user can reconnect with their session, but
> this gets *really* annoying.
>
> Everything that I have seen seems to indicate a temporarily broken
> connection between the remote location and the server.
> Are there any additional troubleshooting steps recommended that would
> be helpful?
>
> Thanks again!
"Jumping in" is welcome here. Yes, that is one common issue and the focus of
my first inquiry as to who, what, when, and where. Many of the consumer
broadband services have latency and connectivity issues. Some comercial
services too have this problem from time to time.
Ping is the common ts tool, but there are others that can be usefull. First
step is to determine if it's the SBS ISP connection or a remote user's.
(rpcping works well for SBS2003 server with RPC/Http enabled)
--
/kj
|
|
In my case after the VB Script error I am taken back to the original RWW
login screen which makes me think it's a timeout. I have tried this over
several remote broadband connection with the same results so it is at the
server end (possibly ISP broadband). I have not tried to do an internal RWW
connection from internal client to internal client
to take out the ISP broadband. Would that information help?
I would also like to know exactly where the timeout settings are registry
stored so I can check them.
Thanks!
"kj" wrote:
[Quoted Text] > ATG wrote:
> > On May 29, 3:44 pm, "kj" <k...[ at ]nowhere.com> wrote:
> >> Richard K wrote:
> >>> Yes that is what I was looking for but....
> >>
> >>> 1. How can I change those default values to see if that will fix
> >>> the problem?
> >>> 2. I have one more piece of info to add. In testing myself I also
> >>> lost the connection but I also get a message box stating
> >>
> >>> VBScript: Remote Desktop Disconnected (in title bar)
> >>> An Internal error has occured. (in the msg box)
> >>
> >> Were you then disconnected from the RWW page or only the remote
> >> workstation RDP session?
> >>
> >> The values are registry entries but should be set at realistic
> >> values. Extending beyond 60 min for an idle session should be very
> >> carefully considered.
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>> "kj" wrote:
> >>
> >>>> Richard K wrote:
> >>>>> This happens in all scenerios (different locations, users, client
> >>>>> computers) so it is not an internet connection issue. Is there
> >>>>> something in SBS that would be timing out after a period of
> >>>>> non-activity that could be doing this?
> >>
> >>>>> "kj" wrote:
> >>
> >>>> There are timeout values for INactivity. I understood your
> >>>> connections were active.
> >>
> >>>> The default values for RWW session timeout are 10 Minutes on a
> >>>> shared/public computer connected to RWW and 60 Minutes on a
> >>>> nonshared/nonpublic computer. Is this what you are refering?
> >>
> >>>>>> Richard K wrote:
> >>>>>>> I have a an issue with clients who RWW into the server then on
> >>>>>>> to the client computers. Everything works fine but after a
> >>>>>>> while, while still active on the connection, they get
> >>>>>>> disconnected. I have looked into the logs but I don't see any
> >>>>>>> reason for this to happen.
> >>
> >>>>>>> Any thoughts on the issue or how to diagnose?
> >>
> >>>>>>> Thanks!
> >>
> >>>>>>> -Richard K
> >>
> >>>>>> Could be a connectivity connection between remote workstation and
> >>>>>> the SBS server, or the SBS server and the internal workstations.
> >>
> >>>>>> Need more detail. Is this just one SBS instance with just one
> >>>>>> user from just one location, or a broader problem?
> >>
> >>>>>> --
> >>>>>> /kj
> >>
> >>>> --
> >>>> /kj
> >>
> >> --
> >> /kj- Hide quoted text -
> >>
> >> - Show quoted text
> >
> >
> >
> > Ok, this is probably not the way to jump in, but I have had the same
> > issue intermittently for a while. It's not due to inactivity settings
> > - occasionally that VB error pops up and the session drops. The user
> > (or me, in some instances) is still logged into the RD session, but
> > dropped from RWW.
> > Logging back into RWW, the user can reconnect with their session, but
> > this gets *really* annoying.
> >
> > Everything that I have seen seems to indicate a temporarily broken
> > connection between the remote location and the server.
> > Are there any additional troubleshooting steps recommended that would
> > be helpful?
> >
> > Thanks again!
>
> "Jumping in" is welcome here. Yes, that is one common issue and the focus of
> my first inquiry as to who, what, when, and where. Many of the consumer
> broadband services have latency and connectivity issues. Some comercial
> services too have this problem from time to time.
>
> Ping is the common ts tool, but there are others that can be usefull. First
> step is to determine if it's the SBS ISP connection or a remote user's.
> (rpcping works well for SBS2003 server with RPC/Http enabled)
>
> --
> /kj
>
>
>
|
|
Richard K wrote:
[Quoted Text] > In my case after the VB Script error I am taken back to the original
> RWW login screen which makes me think it's a timeout. I have tried
> this over several remote broadband connection with the same results
> so it is at the server end (possibly ISP broadband). I have not
> tried to do an internal RWW connection from internal client to
> internal client
> to take out the ISP broadband. Would that information help?
>
> I would also like to know exactly where the timeout settings are
> registry stored so I can check them.
If your connection is not idle, these timeout settings won't help you. If
you are being disconnected from an active session and dumped back to the RWW
login screen, then your connection to the server is being disrupted. If all
users (from different ISP locations) are similarly being disconnected, then
it most likely is the Server Internet connection(NIC, cable, router?)/ISP.
If just one user, it's probably their local ISP/Internet connection.
>
> Thanks!
> "kj" wrote:
>
>> ATG wrote:
>>> On May 29, 3:44 pm, "kj" <k...[ at ]nowhere.com> wrote:
>>>> Richard K wrote:
>>>>> Yes that is what I was looking for but....
>>>>
>>>>> 1. How can I change those default values to see if that will fix
>>>>> the problem?
>>>>> 2. I have one more piece of info to add. In testing myself I
>>>>> also lost the connection but I also get a message box stating
>>>>
>>>>> VBScript: Remote Desktop Disconnected (in title bar)
>>>>> An Internal error has occured. (in the msg box)
>>>>
>>>> Were you then disconnected from the RWW page or only the remote
>>>> workstation RDP session?
>>>>
>>>> The values are registry entries but should be set at realistic
>>>> values. Extending beyond 60 min for an idle session should be very
>>>> carefully considered.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> "kj" wrote:
>>>>
>>>>>> Richard K wrote:
>>>>>>> This happens in all scenerios (different locations, users,
>>>>>>> client computers) so it is not an internet connection issue.
>>>>>>> Is there something in SBS that would be timing out after a
>>>>>>> period of non-activity that could be doing this?
>>>>
>>>>>>> "kj" wrote:
>>>>
>>>>>> There are timeout values for INactivity. I understood your
>>>>>> connections were active.
>>>>
>>>>>> The default values for RWW session timeout are 10 Minutes on a
>>>>>> shared/public computer connected to RWW and 60 Minutes on a
>>>>>> nonshared/nonpublic computer. Is this what you are refering?
>>>>
>>>>>>>> Richard K wrote:
>>>>>>>>> I have a an issue with clients who RWW into the server then on
>>>>>>>>> to the client computers. Everything works fine but after a
>>>>>>>>> while, while still active on the connection, they get
>>>>>>>>> disconnected. I have looked into the logs but I don't see any
>>>>>>>>> reason for this to happen.
>>>>
>>>>>>>>> Any thoughts on the issue or how to diagnose?
>>>>
>>>>>>>>> Thanks!
>>>>
>>>>>>>>> -Richard K
>>>>
>>>>>>>> Could be a connectivity connection between remote workstation
>>>>>>>> and the SBS server, or the SBS server and the internal
>>>>>>>> workstations.
>>>>
>>>>>>>> Need more detail. Is this just one SBS instance with just one
>>>>>>>> user from just one location, or a broader problem?
>>>>
>>>>>>>> --
>>>>>>>> /kj
>>>>
>>>>>> --
>>>>>> /kj
>>>>
>>>> --
>>>> /kj- Hide quoted text -
>>>>
>>>> - Show quoted text
>>>
>>>
>>>
>>> Ok, this is probably not the way to jump in, but I have had the same
>>> issue intermittently for a while. It's not due to inactivity
>>> settings - occasionally that VB error pops up and the session
>>> drops. The user (or me, in some instances) is still logged into the
>>> RD session, but dropped from RWW.
>>> Logging back into RWW, the user can reconnect with their session,
>>> but this gets *really* annoying.
>>>
>>> Everything that I have seen seems to indicate a temporarily broken
>>> connection between the remote location and the server.
>>> Are there any additional troubleshooting steps recommended that
>>> would be helpful?
>>>
>>> Thanks again!
>>
>> "Jumping in" is welcome here. Yes, that is one common issue and the
>> focus of my first inquiry as to who, what, when, and where. Many of
>> the consumer broadband services have latency and connectivity
>> issues. Some comercial services too have this problem from time to
>> time.
>>
>> Ping is the common ts tool, but there are others that can be
>> usefull. First step is to determine if it's the SBS ISP connection
>> or a remote user's. (rpcping works well for SBS2003 server with
>> RPC/Http enabled)
>>
>> --
>> /kj
--
/kj
|
|
Richard K wrote:
[Quoted Text] > In my case after the VB Script error I am taken back to the original
> RWW login screen which makes me think it's a timeout. I have tried
> this over several remote broadband connection with the same results
> so it is at the server end (possibly ISP broadband). I have not
> tried to do an internal RWW connection from internal client to
> internal client
> to take out the ISP broadband. Would that information help?
>
> I would also like to know exactly where the timeout settings are
> registry stored so I can check them.
These settings aren't 'keepalive' values. If your *active* RWW/RDP session
is being disconnected, then your connection to the SBS server is being
disrupted. If ALL users are having the same problem, then likely it is a
Server side Internet connectivity issue (NIC, cable, Router, ISP). If only
one user (or users using the same ISP) then it is likely on the remote users
side.
The registry timeout values are only for idle (inactive) RWW/RDP sessions.
Not keepalive timers.
>
> Thanks!
> "kj" wrote:
>
>> ATG wrote:
>>> On May 29, 3:44 pm, "kj" <k...[ at ]nowhere.com> wrote:
>>>> Richard K wrote:
>>>>> Yes that is what I was looking for but....
>>>>
>>>>> 1. How can I change those default values to see if that will fix
>>>>> the problem?
>>>>> 2. I have one more piece of info to add. In testing myself I
>>>>> also lost the connection but I also get a message box stating
>>>>
>>>>> VBScript: Remote Desktop Disconnected (in title bar)
>>>>> An Internal error has occured. (in the msg box)
>>>>
>>>> Were you then disconnected from the RWW page or only the remote
>>>> workstation RDP session?
>>>>
>>>> The values are registry entries but should be set at realistic
>>>> values. Extending beyond 60 min for an idle session should be very
>>>> carefully considered.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> "kj" wrote:
>>>>
>>>>>> Richard K wrote:
>>>>>>> This happens in all scenerios (different locations, users,
>>>>>>> client computers) so it is not an internet connection issue.
>>>>>>> Is there something in SBS that would be timing out after a
>>>>>>> period of non-activity that could be doing this?
>>>>
>>>>>>> "kj" wrote:
>>>>
>>>>>> There are timeout values for INactivity. I understood your
>>>>>> connections were active.
>>>>
>>>>>> The default values for RWW session timeout are 10 Minutes on a
>>>>>> shared/public computer connected to RWW and 60 Minutes on a
>>>>>> nonshared/nonpublic computer. Is this what you are refering?
>>>>
>>>>>>>> Richard K wrote:
>>>>>>>>> I have a an issue with clients who RWW into the server then on
>>>>>>>>> to the client computers. Everything works fine but after a
>>>>>>>>> while, while still active on the connection, they get
>>>>>>>>> disconnected. I have looked into the logs but I don't see any
>>>>>>>>> reason for this to happen.
>>>>
>>>>>>>>> Any thoughts on the issue or how to diagnose?
>>>>
>>>>>>>>> Thanks!
>>>>
>>>>>>>>> -Richard K
>>>>
>>>>>>>> Could be a connectivity connection between remote workstation
>>>>>>>> and the SBS server, or the SBS server and the internal
>>>>>>>> workstations.
>>>>
>>>>>>>> Need more detail. Is this just one SBS instance with just one
>>>>>>>> user from just one location, or a broader problem?
>>>>
>>>>>>>> --
>>>>>>>> /kj
>>>>
>>>>>> --
>>>>>> /kj
>>>>
>>>> --
>>>> /kj- Hide quoted text -
>>>>
>>>> - Show quoted text
>>>
>>>
>>>
>>> Ok, this is probably not the way to jump in, but I have had the same
>>> issue intermittently for a while. It's not due to inactivity
>>> settings - occasionally that VB error pops up and the session
>>> drops. The user (or me, in some instances) is still logged into the
>>> RD session, but dropped from RWW.
>>> Logging back into RWW, the user can reconnect with their session,
>>> but this gets *really* annoying.
>>>
>>> Everything that I have seen seems to indicate a temporarily broken
>>> connection between the remote location and the server.
>>> Are there any additional troubleshooting steps recommended that
>>> would be helpful?
>>>
>>> Thanks again!
>>
>> "Jumping in" is welcome here. Yes, that is one common issue and the
>> focus of my first inquiry as to who, what, when, and where. Many of
>> the consumer broadband services have latency and connectivity
>> issues. Some comercial services too have this problem from time to
>> time.
>>
>> Ping is the common ts tool, but there are others that can be
>> usefull. First step is to determine if it's the SBS ISP connection
>> or a remote user's. (rpcping works well for SBS2003 server with
>> RPC/Http enabled)
>>
>> --
>> /kj
--
/kj
|
|
kj wrote:
[Quoted Text] > Richard K wrote:
>> In my case after the VB Script error I am taken back to the original
>> RWW login screen which makes me think it's a timeout. I have tried
>> this over several remote broadband connection with the same results
>> so it is at the server end (possibly ISP broadband). I have not
>> tried to do an internal RWW connection from internal client to
>> internal client
>> to take out the ISP broadband. Would that information help?
>>
>> I would also like to know exactly where the timeout settings are
>> registry stored so I can check them.
>
> These settings aren't 'keepalive' values. If your *active* RWW/RDP
> session is being disconnected, then your connection to the SBS server
> is being disrupted. If ALL users are having the same problem, then
> likely it is a Server side Internet connectivity issue (NIC, cable,
> Router, ISP). If only one user (or users using the same ISP) then it
> is likely on the remote users side.
>
> The registry timeout values are only for idle (inactive) RWW/RDP
> sessions. Not keepalive timers.
>
>>
Sorry, I thought that last post got lost.
--
/kj
|
|
In the early days of RWW, there used to be a pop-up box that, when connected
via RWW and getting close to a time-out threshold, would say 'you are about
to get disconnected' blah blah.
I haven't seen that popup for ages, and I'm wondering whether a) it doesn't
work anymore, possibly because of all the browser security enhancements
since 2003, or b) if connected to a workstation in an RWW session and full
screen, it can't show?
It seems to me, that if you ignored that pop-up you'd be kicked out.
I'll have to look into it.
--
Les Connor [SBS MVP]
"kj" <kj[ at ]nowhere.com> wrote in message
news:u6NVqNjoHHA.4424[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text] > kj wrote:
>> Richard K wrote:
>>> In my case after the VB Script error I am taken back to the original
>>> RWW login screen which makes me think it's a timeout. I have tried
>>> this over several remote broadband connection with the same results
>>> so it is at the server end (possibly ISP broadband). I have not
>>> tried to do an internal RWW connection from internal client to
>>> internal client
>>> to take out the ISP broadband. Would that information help?
>>>
>>> I would also like to know exactly where the timeout settings are
>>> registry stored so I can check them.
>>
>> These settings aren't 'keepalive' values. If your *active* RWW/RDP
>> session is being disconnected, then your connection to the SBS server
>> is being disrupted. If ALL users are having the same problem, then
>> likely it is a Server side Internet connectivity issue (NIC, cable,
>> Router, ISP). If only one user (or users using the same ISP) then it
>> is likely on the remote users side.
>>
>> The registry timeout values are only for idle (inactive) RWW/RDP
>> sessions. Not keepalive timers.
>>
>>>
>
> Sorry, I thought that last post got lost.
> --
> /kj
>
|
|
On May 29, 6:13 pm, "Les Connor [SBS MVP]" <les.con...[ at ]DEL.cfive.ca>
wrote:
[Quoted Text] > In the early days of RWW, there used to be a pop-up box that, when connected
> via RWW and getting close to a time-out threshold, would say 'you are about
> to get disconnected' blah blah.
>
> I haven't seen that popup for ages, and I'm wondering whether a) it doesn't
> work anymore, possibly because of all the browser security enhancements
> since 2003, or b) if connected to a workstation in an RWW session and full
> screen, it can't show?
>
> It seems to me, that if you ignored that pop-up you'd be kicked out.
>
> I'll have to look into it.
>
> --
> Les Connor [SBS MVP]
>
> "kj" <k...[ at ]nowhere.com> wrote in message
>
> news:u6NVqNjoHHA.4424[ at ]TK2MSFTNGP03.phx.gbl...
>
>
>
> > kj wrote:
> >> Richard K wrote:
> >>> In my case after the VB Script error I am taken back to the original
> >>> RWW login screen which makes me think it's a timeout. I have tried
> >>> this over several remote broadband connection with the same results
> >>> so it is at the server end (possibly ISP broadband). I have not
> >>> tried to do an internal RWW connection from internal client to
> >>> internal client
> >>> to take out the ISP broadband. Would that information help?
>
> >>> I would also like to know exactly where the timeout settings are
> >>> registry stored so I can check them.
>
> >> These settings aren't 'keepalive' values. If your *active* RWW/RDP
> >> session is being disconnected, then your connection to the SBS server
> >> is being disrupted. If ALL users are having the same problem, then
> >> likely it is a Server side Internet connectivity issue (NIC, cable,
> >> Router, ISP). If only one user (or users using the same ISP) then it
> >> is likely on the remote users side.
>
> >> The registry timeout values are only for idle (inactive) RWW/RDP
> >> sessions. Not keepalive timers.
>
> > Sorry, I thought that last post got lost.
> > --
> > /kj- Hide quoted text -
>
> - Show quoted text -
Thanks for all the replies.
I have learned a tremendous amount through this group already,
hopefully I can contribute :)
I was thinking that, to test the connectivity issue, that I could log
into RWW locally (rather than just mstsc to the desktop), and play
around on it, see if it fails.
If there are no 'hiccups', then it's most certainly a connection
issue.
Given that I have had the issue at home, and a few others have had it
from their home/offices, it then must be a local connection issue, and
I need to call/yell at/make unreasonable demands of my ISP.
If there *are* hiccups locally, then I need to get an old priest and a
young priest to visit my server, and I will report back here with
those results.
:)
|
|
ATG wrote:
[Quoted Text] > On May 29, 6:13 pm, "Les Connor [SBS MVP]" <les.con...[ at ]DEL.cfive.ca>
> wrote:
>> In the early days of RWW, there used to be a pop-up box that, when
>> connected via RWW and getting close to a time-out threshold, would
>> say 'you are about to get disconnected' blah blah.
>>
>> I haven't seen that popup for ages, and I'm wondering whether a) it
>> doesn't work anymore, possibly because of all the browser security
>> enhancements since 2003, or b) if connected to a workstation in an
>> RWW session and full screen, it can't show?
>>
>> It seems to me, that if you ignored that pop-up you'd be kicked out.
>>
>> I'll have to look into it.
>>
>> --
>> Les Connor [SBS MVP]
>>
>> "kj" <k...[ at ]nowhere.com> wrote in message
>>
>> news:u6NVqNjoHHA.4424[ at ]TK2MSFTNGP03.phx.gbl...
>>
>>
>>
>>> kj wrote:
>>>> Richard K wrote:
>>>>> In my case after the VB Script error I am taken back to the
>>>>> original RWW login screen which makes me think it's a timeout. I
>>>>> have tried this over several remote broadband connection with the
>>>>> same results so it is at the server end (possibly ISP broadband).
>>>>> I have not tried to do an internal RWW connection from internal
>>>>> client to internal client
>>>>> to take out the ISP broadband. Would that information help?
>>
>>>>> I would also like to know exactly where the timeout settings are
>>>>> registry stored so I can check them.
>>
>>>> These settings aren't 'keepalive' values. If your *active* RWW/RDP
>>>> session is being disconnected, then your connection to the SBS
>>>> server is being disrupted. If ALL users are having the same
>>>> problem, then likely it is a Server side Internet connectivity
>>>> issue (NIC, cable, Router, ISP). If only one user (or users using
>>>> the same ISP) then it is likely on the remote users side.
>>
>>>> The registry timeout values are only for idle (inactive) RWW/RDP
>>>> sessions. Not keepalive timers.
>>
>>> Sorry, I thought that last post got lost.
>>> --
>>> /kj- Hide quoted text -
>>
>> - Show quoted text -
>
> Thanks for all the replies.
> I have learned a tremendous amount through this group already,
> hopefully I can contribute :)
>
> I was thinking that, to test the connectivity issue, that I could log
> into RWW locally (rather than just mstsc to the desktop), and play
> around on it, see if it fails.
> If there are no 'hiccups', then it's most certainly a connection
> issue.
> Given that I have had the issue at home, and a few others have had it
> from their home/offices, it then must be a local connection issue, and
> I need to call/yell at/make unreasonable demands of my ISP.
>
> If there *are* hiccups locally, then I need to get an old priest and a
> young priest to visit my server, and I will report back here with
> those results.
> :)
You can also have internal network problems which will be evident by local
rww access disconnects. They'll also likely manifest as other quarky local
problems. A local quick check that can help determine this is;
netstat -e -s
Then look for errors (and increasing errors over time) in the results.
Works from a command prompt on either workstations or servers.
--
/kj
|
|
Try timing the interval between the vbscript errors. If the interval lines
up with a value that we recognize as a possible SBS configuration, that
would be a good clue. If the interval is all over the place, then it's more
likely to be in the network layer somewhere, rather than some SBS specific
configuration.
You might also try these few things - a best practices for RWW/connect to
computer connections:
RWW login:
a) select 'private' computer
b) select the slowest connection in the drop down (56k?)
Log onto computer options:
a) rather than full screen - try to match the resolution on the machine
you're connecting to - this cuts way down on translations requied for screen
display. i.e. if the computer at work is 1024x768, then try to match that
when you connect remotely. Some widescreen (especially laptop) can have
really odd native resolutions that are a long way from the desktop
resolution you're connecting to.
b) deselect printers, if you don't need it/them.
c) deselect drive connection, if you don't need it.
The slow speed connection in the RWW login options automatically accounts
for (disables) some things, like sound, background, and some other candy -
so don't be alarmed if the desktop looks and acts a bit differently.
--
Les Connor [SBS MVP]
"ATG" <AegisTitleGroup[ at ]gmail.com> wrote in message
news:1180555259.951955.47200[ at ]u30g2000hsc.googlegroups.com...
[Quoted Text] > On May 29, 6:13 pm, "Les Connor [SBS MVP]" <les.con...[ at ]DEL.cfive.ca>
> wrote:
>> In the early days of RWW, there used to be a pop-up box that, when
>> connected
>> via RWW and getting close to a time-out threshold, would say 'you are
>> about
>> to get disconnected' blah blah.
>>
>> I haven't seen that popup for ages, and I'm wondering whether a) it
>> doesn't
>> work anymore, possibly because of all the browser security enhancements
>> since 2003, or b) if connected to a workstation in an RWW session and
>> full
>> screen, it can't show?
>>
>> It seems to me, that if you ignored that pop-up you'd be kicked out.
>>
>> I'll have to look into it.
>>
>> --
>> Les Connor [SBS MVP]
>>
>> "kj" <k...[ at ]nowhere.com> wrote in message
>>
>> news:u6NVqNjoHHA.4424[ at ]TK2MSFTNGP03.phx.gbl...
>>
>>
>>
>> > kj wrote:
>> >> Richard K wrote:
>> >>> In my case after the VB Script error I am taken back to the original
>> >>> RWW login screen which makes me think it's a timeout. I have tried
>> >>> this over several remote broadband connection with the same results
>> >>> so it is at the server end (possibly ISP broadband). I have not
>> >>> tried to do an internal RWW connection from internal client to
>> >>> internal client
>> >>> to take out the ISP broadband. Would that information help?
>>
>> >>> I would also like to know exactly where the timeout settings are
>> >>> registry stored so I can check them.
>>
>> >> These settings aren't 'keepalive' values. If your *active* RWW/RDP
>> >> session is being disconnected, then your connection to the SBS server
>> >> is being disrupted. If ALL users are having the same problem, then
>> >> likely it is a Server side Internet connectivity issue (NIC, cable,
>> >> Router, ISP). If only one user (or users using the same ISP) then it
>> >> is likely on the remote users side.
>>
>> >> The registry timeout values are only for idle (inactive) RWW/RDP
>> >> sessions. Not keepalive timers.
>>
>> > Sorry, I thought that last post got lost.
>> > --
>> > /kj- Hide quoted text -
>>
>> - Show quoted text -
>
> Thanks for all the replies.
> I have learned a tremendous amount through this group already,
> hopefully I can contribute :)
>
> I was thinking that, to test the connectivity issue, that I could log
> into RWW locally (rather than just mstsc to the desktop), and play
> around on it, see if it fails.
> If there are no 'hiccups', then it's most certainly a connection
> issue.
> Given that I have had the issue at home, and a few others have had it
> from their home/offices, it then must be a local connection issue, and
> I need to call/yell at/make unreasonable demands of my ISP.
>
> If there *are* hiccups locally, then I need to get an old priest and a
> young priest to visit my server, and I will report back here with
> those results.
> :)
>
|
|
I am experiencing the same problem with the RWW disconnects, VBScript: Remote
Desktop Disconnect / An internal error has occurred., and no specific event
id indicating a problem.
I did notice that W3SVC (aka World Wide Web Publising Service) is repeatedly
stopping and starting with 'normal' event ids (7036 and 7035). This is
occurring every minute. Prior to seeing this thread, I have concluded that
this is causing the disconnect.
Check in your system event log. Is the same thing occurring?
I am searching for the process that is causing the repeated stops and starts
of W3SVC. If anyone has suggestions here they would be appreciated!
"Richard K" wrote:
[Quoted Text] > I have a an issue with clients who RWW into the server then on to the client
> computers. Everything works fine but after a while, while still active on
> the connection, they get disconnected. I have looked into the logs but I
> don't see any reason for this to happen.
>
> Any thoughts on the issue or how to diagnose?
>
> Thanks!
>
> -Richard K
|
|
UPDATE
I followed the instructions in Robert Li's 5/27 post to Matt. I found that
the TSweb Timeout steps 3 thru 5 needed to be applied. Then iisreset and
restart computer.
The problem persists with w3svc as described in the previous post.
"Randall Loftis" wrote:
[Quoted Text] > I am experiencing the same problem with the RWW disconnects, VBScript: Remote
> Desktop Disconnect / An internal error has occurred., and no specific event
> id indicating a problem.
>
> I did notice that W3SVC (aka World Wide Web Publising Service) is repeatedly
> stopping and starting with 'normal' event ids (7036 and 7035). This is
> occurring every minute. Prior to seeing this thread, I have concluded that
> this is causing the disconnect.
>
> Check in your system event log. Is the same thing occurring?
>
> I am searching for the process that is causing the repeated stops and starts
> of W3SVC. If anyone has suggestions here they would be appreciated!
>
> "Richard K" wrote:
>
> > I have a an issue with clients who RWW into the server then on to the client
> > computers. Everything works fine but after a while, while still active on
> > the connection, they get disconnected. I have looked into the logs but I
> > don't see any reason for this to happen.
> >
> > Any thoughts on the issue or how to diagnose?
> >
> > Thanks!
> >
> > -Richard K
|
|
Our small office uses RDT to connect to a server hosting our database. Our
connection usually drops after 10-20 minutes of inactivity. The lower end if
the desktop is minimized.
The server admin states timeout is set at 3hours.
Other clients with other isp's, bu not within our geographical area do not
have this issue.
I have tried connecting from other isp's at home & other locations as has my
tech support with same disconnect results.
Server admin has connected as me from theirgeographical location with no
problems w/inactivity
Remote Server admins thinks it is a router somewhere along the line of the
trail our isp & 2 others take from our geographical location to theirs.
- would some type of keepalive program address this?
- any other suggestions?
many thanx
|
|
|