Guest Jay Posted October 25, 2007 Posted October 25, 2007 Unable to connect to server using MSTSC.EXE since 'High Priority' server updates installed Server: Dell PE 2600 Win2k3 SP2, stand-alone I recently installed the four 'High Priority' updates on this server. The updates were installed remotely from another PC on my network, using MSTSC.EXE. The updates installed successfully and then requested a reboot, which was done. Since the reboot, I can not connect to the server using MSTSC.EXE. I get the following error dialog: http://orion.neiu.edu/~jbollyn/servers/mstsc_rwlib_err.jpg I have tried connecting remotely from several different PCs, same result everywhere. Everything in the win2k3 Event Logs is normal. I have tried logging on with a different Administrator account, same result. I can log on to the server console just fine. The System Properties -> Remote (tab) -> Remote Desktop -> Enable Remote Desktop on this computer (checkbox) is still checked. Also, the Windows Firewall/ICS service is not running on this server. Any idea how to fix this? Jay MCP
Guest egaskill@gmail.com Posted October 25, 2007 Posted October 25, 2007 Re: Unable to connect using MSTSC.EXE since critical updates installed On Oct 25, 4:08 pm, Jay <J...@discussions.microsoft.com> wrote: > Unable to connect to server using MSTSC.EXE since 'High Priority' server > updates installed > > Server: Dell PE 2600 Win2k3 SP2, stand-alone > > I recently installed the four 'High Priority' updates on this server. The > updates were installed remotely from another PC on my network, using > MSTSC.EXE. The updates installed successfully and then requested a reboot, > which was done. > > Since the reboot, I can not connect to the server using MSTSC.EXE. I get the > following error dialog: > > http://orion.neiu.edu/~jbollyn/servers/mstsc_rwlib_err.jpg > > I have tried connecting remotely from several different PCs, same result > everywhere. Everything in the win2k3 Event Logs is normal. I have tried > logging on with a different Administrator account, same result. > > I can log on to the server console just fine. > > The System Properties -> Remote (tab) -> Remote Desktop -> Enable Remote > Desktop on this computer (checkbox) is still checked. > > Also, the Windows Firewall/ICS service is not running on this server. > > Any idea how to fix this? > > Jay MCP Have you tried pinging the server, also try telnet SERVER 3389 at the run or cmd prompt to see if you even get a response on that port.
Guest Jay Posted October 26, 2007 Posted October 26, 2007 Re: Unable to connect using MSTSC.EXE since critical updates insta Re: Unable to connect using MSTSC.EXE since critical updates insta This morning I rebooted the server again, and the problem has gone away. I guess something did not load properly during the first reboot. Thanks. "egaskill@gmail.com" wrote: > On Oct 25, 4:08 pm, Jay <J...@discussions.microsoft.com> wrote: > > Unable to connect to server using MSTSC.EXE since 'High Priority' server > > updates installed > > > > Server: Dell PE 2600 Win2k3 SP2, stand-alone > > > > I recently installed the four 'High Priority' updates on this server. The > > updates were installed remotely from another PC on my network, using > > MSTSC.EXE. The updates installed successfully and then requested a reboot, > > which was done. > > > > Since the reboot, I can not connect to the server using MSTSC.EXE. I get the > > following error dialog: > > > > http://orion.neiu.edu/~jbollyn/servers/mstsc_rwlib_err.jpg > > > > I have tried connecting remotely from several different PCs, same result > > everywhere. Everything in the win2k3 Event Logs is normal. I have tried > > logging on with a different Administrator account, same result. > > > > I can log on to the server console just fine. > > > > The System Properties -> Remote (tab) -> Remote Desktop -> Enable Remote > > Desktop on this computer (checkbox) is still checked. > > > > Also, the Windows Firewall/ICS service is not running on this server. > > > > Any idea how to fix this? > > > > Jay MCP > > Have you tried pinging the server, also try telnet SERVER 3389 at the > run or cmd prompt to see if you even get a response on that port. > >
Guest Elliott Gaskill Posted October 26, 2007 Posted October 26, 2007 Re: Unable to connect using MSTSC.EXE since critical updates insta Re: Unable to connect using MSTSC.EXE since critical updates insta Awesome, That wouldn't happen to have been 2003 Server x64 would it? I had that problem quite a few times with that version of the OS. ~Elliott Jay <Jay@discussions.microsoft.com> wrote: > This morning I rebooted the server again, and the problem has gone away. I > guess something did not load properly during the first reboot. > > Thanks. > > "egaskill@gmail.com" wrote: > >> On Oct 25, 4:08 pm, Jay <J...@discussions.microsoft.com> wrote: >> > Unable to connect to server using MSTSC.EXE since 'High Priority' server >> > updates installed >> > >> > Server: Dell PE 2600 Win2k3 SP2, stand-alone >> > >> > I recently installed the four 'High Priority' updates on this server. The >> > updates were installed remotely from another PC on my network, using >> > MSTSC.EXE. The updates installed successfully and then requested a reboot, >> > which was done. >> > >> > Since the reboot, I can not connect to the server using MSTSC.EXE. I get the >> > following error dialog: >> > >> > http://orion.neiu.edu/~jbollyn/servers/mstsc_rwlib_err.jpg >> > >> > I have tried connecting remotely from several different PCs, same result >> > everywhere. Everything in the win2k3 Event Logs is normal. I have tried >> > logging on with a different Administrator account, same result. >> > >> > I can log on to the server console just fine. >> > >> > The System Properties -> Remote (tab) -> Remote Desktop -> Enable Remote >> > Desktop on this computer (checkbox) is still checked. >> > >> > Also, the Windows Firewall/ICS service is not running on this server. >> > >> > Any idea how to fix this? >> > >> > Jay MCP >> >> Have you tried pinging the server, also try telnet SERVER 3389 at the >> run or cmd prompt to see if you even get a response on that port. >> >> > -- Elliott Gaskill IT Director ADx, Inc.
Guest Donald C. Burr Posted October 27, 2007 Posted October 27, 2007 Re: Unable to connect using MSTSC.EXE since critical updates insta Re: Unable to connect using MSTSC.EXE since critical updates insta If this happens again, go to the terminal server config console and make sure the connection (MS RDP 5.2) actually exists. If it does delelte and recreate, if not create. -- Donald C. Burr Chief Technology Officer TruckCenter.com, LLC "Elliott Gaskill" wrote: > Awesome, > > That wouldn't happen to have been 2003 Server x64 would it? > > I had that problem quite a few times with that version of the OS. > > ~Elliott > > Jay <Jay@discussions.microsoft.com> wrote: > > > This morning I rebooted the server again, and the problem has gone away. I > > guess something did not load properly during the first reboot. > > > > Thanks. > > > > "egaskill@gmail.com" wrote: > > > >> On Oct 25, 4:08 pm, Jay <J...@discussions.microsoft.com> wrote: > >> > Unable to connect to server using MSTSC.EXE since 'High Priority' server > >> > updates installed > >> > > >> > Server: Dell PE 2600 Win2k3 SP2, stand-alone > >> > > >> > I recently installed the four 'High Priority' updates on this server. The > >> > updates were installed remotely from another PC on my network, using > >> > MSTSC.EXE. The updates installed successfully and then requested a reboot, > >> > which was done. > >> > > >> > Since the reboot, I can not connect to the server using MSTSC.EXE. I get > the > >> > following error dialog: > >> > > >> > http://orion.neiu.edu/~jbollyn/servers/mstsc_rwlib_err.jpg > >> > > >> > I have tried connecting remotely from several different PCs, same result > >> > everywhere. Everything in the win2k3 Event Logs is normal. I have tried > >> > logging on with a different Administrator account, same result. > >> > > >> > I can log on to the server console just fine. > >> > > >> > The System Properties -> Remote (tab) -> Remote Desktop -> Enable Remote > >> > Desktop on this computer (checkbox) is still checked. > >> > > >> > Also, the Windows Firewall/ICS service is not running on this server. > >> > > >> > Any idea how to fix this? > >> > > >> > Jay MCP > >> > >> Have you tried pinging the server, also try telnet SERVER 3389 at the > >> run or cmd prompt to see if you even get a response on that port. > >> > >> > > > -- > Elliott Gaskill > IT Director > ADx, Inc. > >
Recommended Posts