Guest JenC2000 Posted September 27, 2007 Posted September 27, 2007 I do most of our Windows updates on Servers through remote desktop, but when I reboot a server, 20%-30% I am not able to reconnect. The server is up, the resources are accessible, but the Remote Desktop no longer works. Usually if I reboot a second time from the server console directly, Remote Desktop will start allowing connections. Any ideas?
Guest Pegasus \(MVP\) Posted September 27, 2007 Posted September 27, 2007 Re: Remote Desktop will not reconnect after reboot "JenC2000" <JenC2000@discussions.microsoft.com> wrote in message news:5DECC464-C120-4768-8F48-17E740A8FCFB@microsoft.com... >I do most of our Windows updates on Servers through remote desktop, but >when > I reboot a server, 20%-30% I am not able to reconnect. The server is up, > the > resources are accessible, but the Remote Desktop no longer works. Usually > if > I reboot a second time from the server console directly, Remote Desktop > will > start allowing connections. Any ideas? ". . . Remote Desktop no longer works" is a bit vague. What happens when you try? What does the Event Viewer report? Does the Terminal Server service run on the server? Is the server listening on port 3389?
Guest JenC2000 Posted September 27, 2007 Posted September 27, 2007 Re: Remote Desktop will not reconnect after reboot When I hit "Connect" on Remote Desktops, nothing happens, and the screen shows "Disconnected from server". I don't receive an error message nor do the Event logs show any info. I'm not running terminal server from this machine and it does show port 3389 as listening. It's not just this machine, it happens randomly with many servers. I'm also thinking that the server never rebooted, although I can't check any other examples to see if that might have been the case before as well. "Pegasus (MVP)" wrote: > > "JenC2000" <JenC2000@discussions.microsoft.com> wrote in message > news:5DECC464-C120-4768-8F48-17E740A8FCFB@microsoft.com... > >I do most of our Windows updates on Servers through remote desktop, but > >when > > I reboot a server, 20%-30% I am not able to reconnect. The server is up, > > the > > resources are accessible, but the Remote Desktop no longer works. Usually > > if > > I reboot a second time from the server console directly, Remote Desktop > > will > > start allowing connections. Any ideas? > > ". . . Remote Desktop no longer works" is a bit vague. What > happens when you try? What does the Event Viewer report? > Does the Terminal Server service run on the server? Is the > server listening on port 3389? > > >
Guest Pegasus \(MVP\) Posted September 27, 2007 Posted September 27, 2007 Re: Remote Desktop will not reconnect after reboot You write "I'm not running terminal server from this machine". The TS service ***must*** run on the host machine in order to accept Remote Desktop sessions. Next time you experience the problem, run this command from a Command Prompt on a client machine: telnet HostMachine 3389 and this one on the host machine: netstat -an You might also want to have a look at this article: http://support.microsoft.com/?id=909444 "JenC2000" <JenC2000@discussions.microsoft.com> wrote in message news:3C2B4CDA-E526-4D00-81C6-0575A95146B1@microsoft.com... > When I hit "Connect" on Remote Desktops, nothing happens, and the screen > shows "Disconnected from server". I don't receive an error message nor do > the Event logs show any info. I'm not running terminal server from this > machine and it does show port 3389 as listening. It's not just this > machine, > it happens randomly with many servers. I'm also thinking that the server > never rebooted, although I can't check any other examples to see if that > might have been the case before as well. > > "Pegasus (MVP)" wrote: > >> >> "JenC2000" <JenC2000@discussions.microsoft.com> wrote in message >> news:5DECC464-C120-4768-8F48-17E740A8FCFB@microsoft.com... >> >I do most of our Windows updates on Servers through remote desktop, but >> >when >> > I reboot a server, 20%-30% I am not able to reconnect. The server is >> > up, >> > the >> > resources are accessible, but the Remote Desktop no longer works. >> > Usually >> > if >> > I reboot a second time from the server console directly, Remote Desktop >> > will >> > start allowing connections. Any ideas? >> >> ". . . Remote Desktop no longer works" is a bit vague. What >> happens when you try? What does the Event Viewer report? >> Does the Terminal Server service run on the server? Is the >> server listening on port 3389? >> >> >>
Guest JenC2000 Posted September 28, 2007 Posted September 28, 2007 Re: Remote Desktop will not reconnect after reboot Terminal service is started, but the machine is not setup as a terminal server, remote desktop is enabled only. When I try to telnet to the machine it will pause for a couple of seconds but then go back to the command prompt. If I do a netstat during this time on the server, I do not see any connections from the machine that ran telnet. I do see an option port listening on 3389. "Pegasus (MVP)" wrote: > You write "I'm not running terminal server from this machine". > The TS service ***must*** run on the host machine in order > to accept Remote Desktop sessions. Next time you experience > the problem, run this command from a Command Prompt on > a client machine: > telnet HostMachine 3389 > and this one on the host machine: > netstat -an > > You might also want to have a look at this article: > http://support.microsoft.com/?id=909444 > > > "JenC2000" <JenC2000@discussions.microsoft.com> wrote in message > news:3C2B4CDA-E526-4D00-81C6-0575A95146B1@microsoft.com... > > When I hit "Connect" on Remote Desktops, nothing happens, and the screen > > shows "Disconnected from server". I don't receive an error message nor do > > the Event logs show any info. I'm not running terminal server from this > > machine and it does show port 3389 as listening. It's not just this > > machine, > > it happens randomly with many servers. I'm also thinking that the server > > never rebooted, although I can't check any other examples to see if that > > might have been the case before as well. > > > > "Pegasus (MVP)" wrote: > > > >> > >> "JenC2000" <JenC2000@discussions.microsoft.com> wrote in message > >> news:5DECC464-C120-4768-8F48-17E740A8FCFB@microsoft.com... > >> >I do most of our Windows updates on Servers through remote desktop, but > >> >when > >> > I reboot a server, 20%-30% I am not able to reconnect. The server is > >> > up, > >> > the > >> > resources are accessible, but the Remote Desktop no longer works. > >> > Usually > >> > if > >> > I reboot a second time from the server console directly, Remote Desktop > >> > will > >> > start allowing connections. Any ideas? > >> > >> ". . . Remote Desktop no longer works" is a bit vague. What > >> happens when you try? What does the Event Viewer report? > >> Does the Terminal Server service run on the server? Is the > >> server listening on port 3389? > >> > >> > >> > > >
Recommended Posts