Guest News Group Posted November 15, 2007 Posted November 15, 2007 This has been happening more and more ever since the release of SP1 and SP2. After a system reboot through scheduled tasks (tsshutdn /REBOOT), we are not able to RDP into the server but the server is up and running (no other issues). This doesn't happen every time but it seems to be more frequent. The only way to fix it is to plug-in at the console and reboot the server again. Restarting any RPC related services never helps. We have a mixture of Windows 2003 Standard/Enterprise servers with all updates applied and running the latest RDC console on servers and workstations. Does anyone else run into this problem and if so, any suggestion on how to address this issue?
Guest Brock Hensley Posted November 15, 2007 Posted November 15, 2007 Re: RDP Access Hung after reboot What error are you getting? Can't connect period or sessions full or anything that would help diagnose -B "News Group" <news.group@cqlcorp.net> wrote in message news:OsQf5p4JIHA.5224@TK2MSFTNGP02.phx.gbl... > This has been happening more and more ever since the release of SP1 and > SP2. After a system reboot through scheduled tasks (tsshutdn /REBOOT), we > are not able to RDP into the server but the server is up and running (no > other issues). This doesn't happen every time but it seems to be more > frequent. The only way to fix it is to plug-in at the console and reboot > the server again. Restarting any RPC related services never helps. We > have a mixture of Windows 2003 Standard/Enterprise servers with all > updates applied and running the latest RDC console on servers and > workstations. > > > > Does anyone else run into this problem and if so, any suggestion on how to > address this issue? > >
Guest News Group Posted November 15, 2007 Posted November 15, 2007 Re: RDP Access Hung after reboot When i try to RDP into the box from my workstation i get the below message. "This computer can't connect to the remote computer. The connection was lost due to a network error. Try connecting again. If the problem continues, contact your network admin..." This has nothing to do with firewalls or group policies as when I reboot the server again, everything is back to normal. I see nothing in the Event Viewer either. "Brock Hensley" <brock.hensley@serverintellect.com> wrote in message news:eodSl54JIHA.3516@TK2MSFTNGP02.phx.gbl... > What error are you getting? Can't connect period or sessions full or > anything that would help diagnose > > > -B > > "News Group" <news.group@cqlcorp.net> wrote in message > news:OsQf5p4JIHA.5224@TK2MSFTNGP02.phx.gbl... >> This has been happening more and more ever since the release of SP1 and >> SP2. After a system reboot through scheduled tasks (tsshutdn /REBOOT), we >> are not able to RDP into the server but the server is up and running (no >> other issues). This doesn't happen every time but it seems to be more >> frequent. The only way to fix it is to plug-in at the console and reboot >> the server again. Restarting any RPC related services never helps. We >> have a mixture of Windows 2003 Standard/Enterprise servers with all >> updates applied and running the latest RDC console on servers and >> workstations. >> >> >> >> Does anyone else run into this problem and if so, any suggestion on how >> to address this issue? >> >> > >
Guest Diane Walker Posted November 19, 2007 Posted November 19, 2007 Re: RDP Access Hung after reboot I had the same problem as you. For a while, I still have not figured out a solution. If you find the solution, please let me know. Thanks. "News Group" <news.group@cqlcorp.net> wrote in message news:eYrLdC5JIHA.5160@TK2MSFTNGP05.phx.gbl... > When i try to RDP into the box from my workstation i get the below > message. > > > > "This computer can't connect to the remote computer. The connection was > lost due to a network error. Try connecting again. If the problem > continues, contact your network admin..." > > > > This has nothing to do with firewalls or group policies as when I reboot > the server again, everything is back to normal. I see nothing in the > Event Viewer either. > > > > "Brock Hensley" <brock.hensley@serverintellect.com> wrote in message > news:eodSl54JIHA.3516@TK2MSFTNGP02.phx.gbl... >> What error are you getting? Can't connect period or sessions full or >> anything that would help diagnose >> >> >> -B >> >> "News Group" <news.group@cqlcorp.net> wrote in message >> news:OsQf5p4JIHA.5224@TK2MSFTNGP02.phx.gbl... >>> This has been happening more and more ever since the release of SP1 and >>> SP2. After a system reboot through scheduled tasks (tsshutdn /REBOOT), >>> we are not able to RDP into the server but the server is up and running >>> (no other issues). This doesn't happen every time but it seems to be >>> more frequent. The only way to fix it is to plug-in at the console and >>> reboot the server again. Restarting any RPC related services never >>> helps. We have a mixture of Windows 2003 Standard/Enterprise servers >>> with all updates applied and running the latest RDC console on servers >>> and workstations. >>> >>> >>> >>> Does anyone else run into this problem and if so, any suggestion on how >>> to address this issue? >>> >>> >> >> > >
Guest Ag IT Guy Posted November 21, 2007 Posted November 21, 2007 Re: RDP Access Hung after reboot I've had the same issue when rebooting after installing Windows Updates and I'm not sure of the cause, but what solved the problem for me was initiating a reboot using the shutdown command from the command line prompt. For some reason it seems that Terminal Services don't start after a reboot sometimes. If you find yourself unable to remote desktop into a server, go to the command line and execute the following: shutdown -r -m \\servername "-r" specifies a reboot "-m" following by \\ and then IP address or server name on the domain RECOMMENDED: Also use the option "-t XX" where XX is the time in seconds the server waits to reboot. Allowing a few minutes of buffer time is a good measure to allow for a safe shutdown and also gives you time to abort the shutdown if needed (it happened to me and I'm glad I used that option..."-a" is the abort option) Using the shutdown command means that the reboot is initiated by winlogon.exe instead of wuauclt.exe (Windows Update) or some other process. Hope this helps...
Guest Krish Posted November 21, 2007 Posted November 21, 2007 Re: RDP Access Hung after reboot Hi All, i had a question here are we getting any specific error related to TS login. it might be "Remote logins are currently disabled". If yes please let me know because there is a hotfix for this in KB 842506 Thanks Krish "Ag IT Guy" wrote: > I've had the same issue when rebooting after installing Windows Updates and > I'm not sure of the cause, but what solved the problem for me was initiating > a reboot using the shutdown command from the command line prompt. For some > reason it seems that Terminal Services don't start after a reboot sometimes. > If you find yourself unable to remote desktop into a server, go to the > command line and execute the following: > > shutdown -r -m \\servername > > "-r" specifies a reboot > "-m" following by \\ and then IP address or server name on the domain > > RECOMMENDED: > Also use the option "-t XX" where XX is the time in seconds the server waits > to reboot. Allowing a few minutes of buffer time is a good measure to allow > for a safe shutdown and also gives you time to abort the shutdown if needed > (it happened to me and I'm glad I used that option..."-a" is the abort option) > > Using the shutdown command means that the reboot is initiated by > winlogon.exe instead of wuauclt.exe (Windows Update) or some other process. > > Hope this helps...
Guest Thee Chicago Wolf Posted November 26, 2007 Posted November 26, 2007 Re: RDP Access Hung after reboot >This has been happening more and more ever since the release of SP1 and SP2. >After a system reboot through scheduled tasks (tsshutdn /REBOOT), we are not >able to RDP into the server but the server is up and running (no other >issues). This doesn't happen every time but it seems to be more frequent. >The only way to fix it is to plug-in at the console and reboot the server >again. Restarting any RPC related services never helps. We have a mixture >of Windows 2003 Standard/Enterprise servers with all updates applied and >running the latest RDC console on servers and workstations. > >Does anyone else run into this problem and if so, any suggestion on how to >address this issue? This fix for this issue sounds like what's in this KB article: http://support.microsoft.com/kb/930045 Give it a shot. - Thee Chicago Wolf
Guest News Group Posted November 27, 2007 Posted November 27, 2007 Re: RDP Access Hung after reboot I applied for the Hotfix and will install it when I receive it. I'll let everyone know if that addresses my problem. Thanks, again. "Thee Chicago Wolf" <.@.> wrote in message news:tpklk3hfthgnsk8aec4l48ralitkufe9ot@4ax.com... > >This has been happening more and more ever since the release of SP1 and > >SP2. >>After a system reboot through scheduled tasks (tsshutdn /REBOOT), we are >>not >>able to RDP into the server but the server is up and running (no other >>issues). This doesn't happen every time but it seems to be more frequent. >>The only way to fix it is to plug-in at the console and reboot the server >>again. Restarting any RPC related services never helps. We have a >>mixture >>of Windows 2003 Standard/Enterprise servers with all updates applied and >>running the latest RDC console on servers and workstations. >> >>Does anyone else run into this problem and if so, any suggestion on how to >>address this issue? > > This fix for this issue sounds like what's in this KB article: > http://support.microsoft.com/kb/930045 > Give it a shot. > > - Thee Chicago Wolf
Guest Thee Chicago Wolf Posted November 27, 2007 Posted November 27, 2007 Re: RDP Access Hung after reboot >I applied for the Hotfix and will install it when I receive it. I'll let >everyone know if that addresses my problem. We'll be interested to hear about it. Good luck. - Thee Chicago Wolf
Guest Jack Doyle Posted December 24, 2007 Posted December 24, 2007 Re: RDP Access Hung after reboot News Group wrote: > When i try to RDP into the box from my workstation i get the below message. > > "This computer can't connect to the remote computer. The connection was > lost due to a network error. Try connecting again. If the problem > continues, contact your network admin..." > > This has nothing to do with firewalls or group policies as when I reboot the > server again, everything is back to normal. I see nothing in the Event > Viewer either. I've seen the same thing many times. There is nothing on the server indicating that there is a problem. The problem is exactly what is described above. RDP client simply can't connect. Not sure of a solution other than to reboot from the console. -- Jack Doyle, Systems Engineer ScriptLogic Corporation http://www.scriptlogic.com
Guest News Group Posted January 17, 2008 Posted January 17, 2008 Re: RDP Access Hung after reboot I wanted to let everyone know that the HOTFIX did not fix the problem. "Thee Chicago Wolf" <.@.> wrote in message news:teuok3hs7p8ni1dgjdci6gfmerhlq75s5u@4ax.com... > >I applied for the Hotfix and will install it when I receive it. I'll let >>everyone know if that addresses my problem. > > We'll be interested to hear about it. Good luck. > > - Thee Chicago Wolf
Guest Thee Chicago Wolf Posted January 17, 2008 Posted January 17, 2008 Re: RDP Access Hung after reboot >I wanted to let everyone know that the HOTFIX did not fix the problem. Sorry to hear the patch didn't help. - Thee Chicago Wolf
Guest gmobileuser Posted February 19, 2008 Posted February 19, 2008 Re: RDP Access Hung after reboot Hello, exactly what i'm having problems with these days. I believe it came on after a Citrix update and now it happens to random servers on random days. drives me nutzo. Did you find a fix for this yet? I'm going to reimage to Win2003 SP2 from SP1 to see if this helps. I'll let you know. Let me know if you came up with anything? THANKS Gabe "Thee Chicago Wolf" wrote: > >I wanted to let everyone know that the HOTFIX did not fix the problem. > > Sorry to hear the patch didn't help. > > - Thee Chicago Wolf >
Guest News Group Posted February 21, 2008 Posted February 21, 2008 Re: RDP Access Hung after reboot It still happens to me on random computers (Windows XP & Windows 2003) and random days, no rhyme or reason so far. Maybe they fixed it in Windows 2008, but it did seem to happen (if I recall correctly), after SP2 was released. "gmobileuser" <gmobileuser@discussions.microsoft.com> wrote in message news:BAADB337-E3C2-45D0-BB3C-5A6298E042D6@microsoft.com... > Hello, exactly what i'm having problems with these days. I believe it > came > on after a Citrix update and now it happens to random servers on random > days. > drives me nutzo. Did you find a fix for this yet? > > I'm going to reimage to Win2003 SP2 from SP1 to see if this helps. I'll > let > you know. Let me know if you came up with anything? > > THANKS > > Gabe > > "Thee Chicago Wolf" wrote: > >> >I wanted to let everyone know that the HOTFIX did not fix the problem. >> >> Sorry to hear the patch didn't help. >> >> - Thee Chicago Wolf >>
Guest Thee Chicago Wolf Posted February 21, 2008 Posted February 21, 2008 Re: RDP Access Hung after reboot >It still happens to me on random computers (Windows XP & Windows 2003) and >random days, no rhyme or reason so far. Maybe they fixed it in Windows >2008, but it did seem to happen (if I recall correctly), after SP2 was >released. From a lot of replies I'm getting to telling people to ensure the NIC driver is the latest available, most people with Server 2003 SP2 are finding it does help. Did you also read the info regarding the TCP Chimney from the SNP? - Thee Chicago Wolf
Recommended Posts