Remote connection timed out

[Guest Marvin Bordelon]

We have a dozen or so users who connect to our Windows 2000 terminal server

via VPN using remote desktop. One particular user gets the message"The remote

connection timed out. Please try connecting to the remote computer again."

when trying to connect to the terminal server. However, this user is able to

remote to other servers on our network. Anyone have any idea why this user

would be able to connect to other servers and Not the terminal server?

[Guest Vera Noest [MVP]]

Re: Remote connection timed out

 

Are all the other servers also running W2K TS? And same SP level?

Can the user ping the server?

_________________________________________________________

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:

> We have a dozen or so users who connect to our Windows 2000

> terminal server via VPN using remote desktop. One particular

> user gets the message"The remote connection timed out. Please

> try connecting to the remote computer again." when trying to

> connect to the terminal server. However, this user is able to

> remote to other servers on our network. Anyone have any idea why

> this user would be able to connect to other servers and Not the

> terminal server?

[Guest Marvin Bordelon]

Re: Remote connection timed out

 

Actually the other servers are 2003 sp2. And the user can ping the server and

I can ping the user's workstation from the term server. This is a user

working from home which may mean a slow connection. So, I am hoping the

TCP/IP and NBT parameters you referenced in your reply to Scott Kelley's post

will help.I just find it odd that the user can connect to one server and not

the other. Thanks for your response, I will keep you updated as soon as these

changes can be made.

 

 

"Vera Noest [MVP]" wrote:

> Are all the other servers also running W2K TS? And same SP level?

> Can the user ping the server?

> _________________________________________________________

> 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:

>

> > We have a dozen or so users who connect to our Windows 2000

> > terminal server via VPN using remote desktop. One particular

> > user gets the message"The remote connection timed out. Please

> > try connecting to the remote computer again." when trying to

> > connect to the terminal server. However, this user is able to

> > remote to other servers on our network. Anyone have any idea why

> > this user would be able to connect to other servers and Not the

> > terminal server?

>

[Guest Vera Noest [MVP]]

Re: Remote connection timed out

 

Don't forget to check the EventLog on the W2K TS. Could be a

problem with the MTU size of the connection, causing problems in

transferring a TS CAL.

_________________________________________________________

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:

> Actually the other servers are 2003 sp2. And the user can ping

> the server and I can ping the user's workstation from the term

> server. This is a user working from home which may mean a slow

> connection. So, I am hoping the TCP/IP and NBT parameters you

> referenced in your reply to Scott Kelley's post will help.I just

> find it odd that the user can connect to one server and not the

> other. Thanks for your response, I will keep you updated as soon

> as these changes can be made.

>

>

> "Vera Noest [MVP]" wrote:

>

>> Are all the other servers also running W2K TS? And same SP

>> level? Can the user ping the server?

>> _________________________________________________________

>> 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:

>>

>> > We have a dozen or so users who connect to our Windows 2000

>> > terminal server via VPN using remote desktop. One particular

>> > user gets the message"The remote connection timed out. Please

>> > try connecting to the remote computer again." when trying to

>> > connect to the terminal server. However, this user is able to

>> > remote to other servers on our network. Anyone have any idea

>> > why this user would be able to connect to other servers and

>> > Not the terminal server?

[Guest Marvin Bordelon]

Re: Remote connection timed out

 

I have checked the event logs for the time frame when I know we were testing

this connection and getting failures. But, I don't see any warnings or errors.

 

"Vera Noest [MVP]" wrote:

> Don't forget to check the EventLog on the W2K TS. Could be a

> problem with the MTU size of the connection, causing problems in

> transferring a TS CAL.

> _________________________________________________________

> 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:

>

> > Actually the other servers are 2003 sp2. And the user can ping

> > the server and I can ping the user's workstation from the term

> > server. This is a user working from home which may mean a slow

> > connection. So, I am hoping the TCP/IP and NBT parameters you

> > referenced in your reply to Scott Kelley's post will help.I just

> > find it odd that the user can connect to one server and not the

> > other. Thanks for your response, I will keep you updated as soon

> > as these changes can be made.

> >

> >

> > "Vera Noest [MVP]" wrote:

> >

> >> Are all the other servers also running W2K TS? And same SP

> >> level? Can the user ping the server?

> >> _________________________________________________________

> >> 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:

> >>

> >> > We have a dozen or so users who connect to our Windows 2000

> >> > terminal server via VPN using remote desktop. One particular

> >> > user gets the message"The remote connection timed out. Please

> >> > try connecting to the remote computer again." when trying to

> >> > connect to the terminal server. However, this user is able to

> >> > remote to other servers on our network. Anyone have any idea

> >> > why this user would be able to connect to other servers and

> >> > Not the terminal server?

>

[Guest Vera Noest [MVP]]

Re: Remote connection timed out

 

Can the user map a shared drive on the server?

Connect to another TS or an XP client?

Connect to the server by IP address?

 

_________________________________________________________

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:

> I have checked the event logs for the time frame when I know we

> were testing this connection and getting failures. But, I don't

> see any warnings or errors.

>

> "Vera Noest [MVP]" wrote:

>

>> Don't forget to check the EventLog on the W2K TS. Could be a

>> problem with the MTU size of the connection, causing problems

>> in transferring a TS CAL.

>> _________________________________________________________

>> 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:

>>

>> > Actually the other servers are 2003 sp2. And the user can

>> > ping the server and I can ping the user's workstation from

>> > the term server. This is a user working from home which may

>> > mean a slow connection. So, I am hoping the TCP/IP and NBT

>> > parameters you referenced in your reply to Scott Kelley's

>> > post will help.I just find it odd that the user can connect

>> > to one server and not the other. Thanks for your response, I

>> > will keep you updated as soon as these changes can be made.

>> >

>> >

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

>> >

>> >> Are all the other servers also running W2K TS? And same SP

>> >> level? Can the user ping the server?

>> >> _________________________________________________________

>> >> 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:

>> >>

>> >> > We have a dozen or so users who connect to our Windows

>> >> > 2000 terminal server via VPN using remote desktop. One

>> >> > particular user gets the message"The remote connection

>> >> > timed out. Please try connecting to the remote computer

>> >> > again." when trying to connect to the terminal server.

>> >> > However, this user is able to remote to other servers on

>> >> > our network. Anyone have any idea why this user would be

>> >> > able to connect to other servers and Not the terminal

>> >> > server?