RDP stops working

[Guest BBJ]

I'm having severel Windows 2003 servers that sometimes stop listening on port

3389 - and RDP stop working. We have to restart the servers when this

happens, and after that it's possible to connet using RDP again. All servers

are running SP2, some as terminal servers and others as "normal" servers with

RDP enabled.

Any ideas as to how to resolve this issue?

[Guest Munindra Das [MSFT]]

Re: RDP stops working

 

Do you have any RDP/Termsrv related errors in the event log?

 

--

This posting is provided "AS IS" with no warranties, and confers no rights.

"BBJ" <BBJ@discussions.microsoft.com> wrote in message

news:A164EA60-DEB2-4F90-9743-7AE55F6D91CF@microsoft.com...

> I'm having severel Windows 2003 servers that sometimes stop listening on

> port

> 3389 - and RDP stop working. We have to restart the servers when this

> happens, and after that it's possible to connet using RDP again. All

> servers

> are running SP2, some as terminal servers and others as "normal" servers

> with

> RDP enabled.

> Any ideas as to how to resolve this issue?

[Guest BBJ]

Re: RDP stops working

 

No, nothing appears in in the log files!

 

"Munindra Das [MSFT]" wrote:

> Do you have any RDP/Termsrv related errors in the event log?

>

> --

> This posting is provided "AS IS" with no warranties, and confers no rights.

> "BBJ" <BBJ@discussions.microsoft.com> wrote in message

> news:A164EA60-DEB2-4F90-9743-7AE55F6D91CF@microsoft.com...

> > I'm having severel Windows 2003 servers that sometimes stop listening on

> > port

> > 3389 - and RDP stop working. We have to restart the servers when this

> > happens, and after that it's possible to connet using RDP again. All

> > servers

> > are running SP2, some as terminal servers and others as "normal" servers

> > with

> > RDP enabled.

> > Any ideas as to how to resolve this issue?

>

>

[Guest Munindra Das [MSFT]]

Re: RDP stops working

 

By "stop listening on port 3389" what exactly do you mean? Is the service

running? Is the listener up (run qwinsta.exe)? Can you see 3389 port being

listened at "netstat -a |findstr /i 3389"?

 

Only case that jumps out at me when you say TS stops listening is if TS is

receiving a lot of bad connection. To prevent attacks, TS will stop

listening for some time if there were X number of bad connections? Can you

check if your systems are receiving bad TS connections? But this is

something that would have logged into the event log.

 

Another issue can be the network itself. May be it is dropping packets or

something. You can try taking a network trace (using netmon) on the server

and see if it is receiving connection packets.

 

--

This posting is provided "AS IS" with no warranties, and confers no rights.

"BBJ" <BBJ@discussions.microsoft.com> wrote in message

news:1A58C69C-1D38-4933-A986-CC00653CDEEA@microsoft.com...

> No, nothing appears in in the log files!

>

> "Munindra Das [MSFT]" wrote:

>

>> Do you have any RDP/Termsrv related errors in the event log?

>>

>> --

>> This posting is provided "AS IS" with no warranties, and confers no

>> rights.

>> "BBJ" <BBJ@discussions.microsoft.com> wrote in message

>> news:A164EA60-DEB2-4F90-9743-7AE55F6D91CF@microsoft.com...

>> > I'm having severel Windows 2003 servers that sometimes stop listening

>> > on

>> > port

>> > 3389 - and RDP stop working. We have to restart the servers when this

>> > happens, and after that it's possible to connet using RDP again. All

>> > servers

>> > are running SP2, some as terminal servers and others as "normal"

>> > servers

>> > with

>> > RDP enabled.

>> > Any ideas as to how to resolve this issue?

>>

>>