Re: Remote Connection has Timed Out error

[Guest Marvin Bordelon]

Re: Remote Connection has Timed Out error

 

Is this only for XP 64 edition?

 

"Vera Noest [MVP]" wrote:

> Great! Thanks for the feedback!

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> =?Utf-8?B?U2NvdHQgS2VsbGV5?=

> <ScottKelley@discussions.microsoft.com> wrote on 07 okt 2005 in

> microsoft.public.windows.terminal_services:

>

> > It looks like the patch is working, I haven't had any complaints

> > on the terminal server I've applied it to. Thanks again!

> >

> > "Vera Noest [MVP]" wrote:

> >

> >> Check if this helps:

> >>

> >> 898060 - Network connectivity between clients and servers may

> >> not work after the installation of security update MS05-019 or

> >> Windows Server 2003 Service Pack 1

> >> http://support.microsoft.com/?kbid=898060

> >>

> >> _________________________________________________________

> >> Vera Noest

> >> MCSE, CCEA, Microsoft MVP - Terminal Server

> >> TS troubleshooting: http://ts.veranoest.net

> >> ___ please respond in newsgroup, NOT by private email ___

> >>

> >> =?Utf-8?B?U2NvdHQgS2VsbGV5?=

> >> <ScottKelley@discussions.microsoft.com> wrote on 23 sep 2005 in

> >> microsoft.public.windows.terminal_services:

> >>

> >> > I have 4 Windows 2003 terminal servers and 2 Windows 2000

> >> > terminal servers. My company has several sites that are

> >> > located in small communities which using anything from a

> >> > point-to-point line to cable and DSL for connectivity. They

> >> > all use VPN tunnels from the sites to connect into our main

> >> > office site using the same routers. Each site connects back

> >> > to the office using Remote Desktop connections to one of the

> >> > Windows 2003 servers and one of the Windows 2000 servers.

> >> >

> >> > Some of the sites (usually the ones with the lower end

> >> > connectivity but not always) will get dumped from the Windows

> >> > 20003 terminal server and if they try reconnecting they get a

> >> > "The remote connection has timed out" errer from remote

> >> > desktop.

> >> > The site still has network connectivity and the Windows 2000

> >> > terminal session will not have been broken. If I point the

> >> > user to another Windows 2003 server then they can connect.

> >> > If I reboot the server that gave them the time out issue,

> >> > they can get back in. They can also get back into the

> >> > problematic server the following day with no reboot to the

> >> > server. When someone gets kicked off and receives this

> >> > message, it usually takes out a whole site's access to this

> >> > server and sometimes it will affect 2 or 3 sites.

> >> >

> >> > This problem is not isolated to just one of the Windows 2003

> >> > servers, it's happened to more than 1 (I have one site that

> >> > got the message when trying to connect to all 4 2003 servers

> >> > once). The problem is not consistant to one or a few sites

> >> > though it seems to plague lower bandwidth sites more (my

> >> > in-town point-to-point sites don't seem to have the issue)

> >> > and it only happens a few times a week.

> >> >

> >> > I've tried looking for networks issues but as I've said, the

> >> > Windows 2000 terminal session will remain active as well as

> >> > the VPN. I've tried adjusting several of options in terminal

> >> > services but to no avail. Any input or thoughts would be

> >> > helpful.

>

[Guest Vera Noest [MVP]]

Re: Remote Connection has Timed Out error

 

Re: Remote Connection has Timed Out error

 

No. Here's the "Applies to" section of the article:

 

• Microsoft Windows Server 2003 SP1, when used with:

Microsoft Windows Server 2003, Standard Edition (32-bit x86)

Microsoft Windows Server 2003, Enterprise Edition

Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)

Microsoft Windows Server 2003, Web Edition

Microsoft Windows Server 2003, Enterprise Edition for Itanium-

based Systems

Microsoft Windows Server 2003, Datacenter Edition for Itanium-

Based Systems

 

• Microsoft Windows Server 2003, Standard x64 Edition

• Microsoft Windows Server 2003, Enterprise x64 Edition

• Microsoft Windows Server 2003, Datacenter x64 Edition

• Microsoft Windows Server 2003, Enterprise Edition for Itanium-

based Systems

• Microsoft Windows Server 2003, Datacenter Edition for Itanium-

Based Systems

• Microsoft Windows Server 2003, Standard Edition (32-bit x86)

• Microsoft Windows Server 2003, Enterprise Edition

• Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)

• Microsoft Windows Server 2003, Web Edition

• Microsoft Windows XP Home Edition

• Microsoft Windows XP Home Edition

• Microsoft Windows XP Professional

• Microsoft Windows XP Professional

• Microsoft Windows 2000 Advanced Server

• Microsoft Windows 2000 Advanced Server

• Microsoft Windows 2000 Service Pack 3

• Microsoft Windows 2000 Datacenter Server

• Microsoft Windows 2000 Service Pack 3

• Microsoft Windows 2000 Professional Edition

• Microsoft Windows 2000 Service Pack 3

• Microsoft Windows 2000 Service Pack 4

• Microsoft Windows XP Professional x64 Edition

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

=?Utf-8?B?TWFydmluIEJvcmRlbG9u?=

<MarvinBordelon@discussions.microsoft.com> wrote on 27 nov 2007 in

microsoft.public.windows.terminal_services:

> Is this only for XP 64 edition?

>

> "Vera Noest [MVP]" wrote:

>

>> Great! Thanks for the feedback!

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting: http://ts.veranoest.net

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> =?Utf-8?B?U2NvdHQgS2VsbGV5?=

>> <ScottKelley@discussions.microsoft.com> wrote on 07 okt 2005 in

>> microsoft.public.windows.terminal_services:

>>

>> > It looks like the patch is working, I haven't had any

>> > complaints

>> > on the terminal server I've applied it to. Thanks again!

>> >

>> > "Vera Noest [MVP]" wrote:

>> >

>> >> Check if this helps:

>> >>

>> >> 898060 - Network connectivity between clients and servers may

>> >> not work after the installation of security update MS05-019

>> >> or Windows Server 2003 Service Pack 1

>> >> http://support.microsoft.com/?kbid=898060

>> >>

>> >> _________________________________________________________

>> >> Vera Noest

>> >> MCSE, CCEA, Microsoft MVP - Terminal Server

>> >> TS troubleshooting: http://ts.veranoest.net

>> >> ___ please respond in newsgroup, NOT by private email ___

>> >>

>> >> =?Utf-8?B?U2NvdHQgS2VsbGV5?=

>> >> <ScottKelley@discussions.microsoft.com> wrote on 23 sep 2005

in

>> >> microsoft.public.windows.terminal_services:

>> >>

>> >> > I have 4 Windows 2003 terminal servers and 2 Windows 2000

>> >> > terminal servers. My company has several sites that are

>> >> > located in small communities which using anything from a

>> >> > point-to-point line to cable and DSL for connectivity.

They

>> >> > all use VPN tunnels from the sites to connect into our main

>> >> > office site using the same routers. Each site connects

back

>> >> > to the office using Remote Desktop connections to one of

the

>> >> > Windows 2003 servers and one of the Windows 2000 servers.

>> >> >

>> >> > Some of the sites (usually the ones with the lower end

>> >> > connectivity but not always) will get dumped from the

Windows

>> >> > 20003 terminal server and if they try reconnecting they get

a

>> >> > "The remote connection has timed out" errer from remote

>> >> > desktop.

>> >> > The site still has network connectivity and the Windows

2000

>> >> > terminal session will not have been broken. If I point the

>> >> > user to another Windows 2003 server then they can connect.

>> >> > If I reboot the server that gave them the time out issue,

>> >> > they can get back in. They can also get back into the

>> >> > problematic server the following day with no reboot to the

>> >> > server. When someone gets kicked off and receives this

>> >> > message, it usually takes out a whole site's access to this

>> >> > server and sometimes it will affect 2 or 3 sites.

>> >> >

>> >> > This problem is not isolated to just one of the Windows

2003

>> >> > servers, it's happened to more than 1 (I have one site that

>> >> > got the message when trying to connect to all 4 2003

servers

>> >> > once). The problem is not consistant to one or a few sites

>> >> > though it seems to plague lower bandwidth sites more (my

>> >> > in-town point-to-point sites don't seem to have the issue)

>> >> > and it only happens a few times a week.

>> >> >

>> >> > I've tried looking for networks issues but as I've said,

the

>> >> > Windows 2000 terminal session will remain active as well as

>> >> > the VPN. I've tried adjusting several of options in

terminal

>> >> > services but to no avail. Any input or thoughts would be

>> >> > helpful.