Guest amacam Posted October 8, 2008 Posted October 8, 2008 I am trying to connect from a Windows XP SP3 workstation to a Windows Server 2003 SP2 server using Remote Desktop Connection client. I have version 6.0.6001 on the XP workstation. On connection, I receive the following error: "This computer can't connect to the remote computer. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator." After receiving the message, we logon to the server from the console and run a netstat and see that 3389 is not listening. Also, if we run tsadmin and go to sessions, we do not see an RDP-Tcp session listed. I do not always receive this message, sometimes I can connect and other times I can't. Nobody else is remoted into the server at the time that I am trying to connect. I am a domain administrator on the server, which means that I have rights to remote desktop to the server. If I restart the server, I can normally then remote in. Other times, it clears itself up without any action and I can then remote in. Also, if I use RemotelyAnywhere to connect to the server and use the Remote Control tool, this normally starts the RDP-Tcp session again so that I can then remote to the server using Remote Desktop, not sure how. It is very flaky and there doesn't seem to be an explanation as to why or when the error is received. We do not receive any errors in the event logs on the client or the server. It is not a DNS issue because we try connecting using an IP when this happens. We have been racking our brains for months trying to figure this out and we are now getting pushed to move to Remote Desktop vice RemotelyAnywhere. We need to get this error resolved before we can fully migrate over. Any help you can give is much appreciated!!!
Guest srinathhc Posted October 13, 2008 Posted October 13, 2008 RE: Terminal Services intermittently stops listening Hi Amacam, Its common error in for me in windows 2003 sp1. check sessions are not properly closing for this error. Also check in terminal services configuration-->connections--->tcp-rdp---check proper network adapter is bounded. and set policys for sessions such to end disconnected sessions,set 2/5 minutes to end idle sessions. and if possible if server is not much critical/non production apply service pack-2 which might work. Thanks & Regards, Srinath -- Srinath Windows Server Management "amacam" wrote: > I am trying to connect from a Windows XP SP3 workstation to a Windows Server > 2003 SP2 server using Remote Desktop Connection client. I have version > 6.0.6001 on the XP workstation. On connection, I receive the following error: > > "This computer can't connect to the remote computer. Try connecting again. > If the problem continues, contact the owner of the remote computer or your > network administrator." > > After receiving the message, we logon to the server from the console and run > a netstat and see that 3389 is not listening. Also, if we run tsadmin and go > to sessions, we do not see an RDP-Tcp session listed. I do not always > receive this message, sometimes I can connect and other times I can't. > Nobody else is remoted into the server at the time that I am trying to > connect. I am a domain administrator on the server, which means that I have > rights to remote desktop to the server. If I restart the server, I can > normally then remote in. Other times, it clears itself up without any action > and I can then remote in. Also, if I use RemotelyAnywhere to connect to the > server and use the Remote Control tool, this normally starts the RDP-Tcp > session again so that I can then remote to the server using Remote Desktop, > not sure how. It is very flaky and there doesn't seem to be an explanation > as to why or when the error is received. > > We do not receive any errors in the event logs on the client or the server. > It is not a DNS issue because we try connecting using an IP when this happens. > > We have been racking our brains for months trying to figure this out and we > are now getting pushed to move to Remote Desktop vice RemotelyAnywhere. We > need to get this error resolved before we can fully migrate over. > > Any help you can give is much appreciated!!!
Guest srinathhc Posted October 20, 2008 Posted October 20, 2008 RE: Terminal Services intermittently stops listening Install UPH clean tool if sessions are not ending properly this will close disconnected session related process. Thanks Srinth -- Srinath Windows Server Management "srinathhc" wrote: > Hi Amacam, > Its common error in for me in windows 2003 sp1. check sessions are not > properly closing for this error. > > Also check in terminal services > configuration-->connections--->tcp-rdp---check proper network adapter is > bounded. > > and set policys for sessions such to end disconnected sessions,set 2/5 > minutes to end idle sessions. > > and if possible if server is not much critical/non production apply service > pack-2 which might work. > > Thanks & Regards, > Srinath > > > > -- > Srinath > Windows Server Management > > > "amacam" wrote: > > > I am trying to connect from a Windows XP SP3 workstation to a Windows Server > > 2003 SP2 server using Remote Desktop Connection client. I have version > > 6.0.6001 on the XP workstation. On connection, I receive the following error: > > > > "This computer can't connect to the remote computer. Try connecting again. > > If the problem continues, contact the owner of the remote computer or your > > network administrator." > > > > After receiving the message, we logon to the server from the console and run > > a netstat and see that 3389 is not listening. Also, if we run tsadmin and go > > to sessions, we do not see an RDP-Tcp session listed. I do not always > > receive this message, sometimes I can connect and other times I can't. > > Nobody else is remoted into the server at the time that I am trying to > > connect. I am a domain administrator on the server, which means that I have > > rights to remote desktop to the server. If I restart the server, I can > > normally then remote in. Other times, it clears itself up without any action > > and I can then remote in. Also, if I use RemotelyAnywhere to connect to the > > server and use the Remote Control tool, this normally starts the RDP-Tcp > > session again so that I can then remote to the server using Remote Desktop, > > not sure how. It is very flaky and there doesn't seem to be an explanation > > as to why or when the error is received. > > > > We do not receive any errors in the event logs on the client or the server. > > It is not a DNS issue because we try connecting using an IP when this happens. > > > > We have been racking our brains for months trying to figure this out and we > > are now getting pushed to move to Remote Desktop vice RemotelyAnywhere. We > > need to get this error resolved before we can fully migrate over. > > > > Any help you can give is much appreciated!!!
Recommended Posts