Remote Desktop Administration not working
in [Terminal Services]
|
From: CST112 on 28 Aug 2006 18:58 I have a fresh version of Windows 2003 installed and I am trying to get Terminal Services (Remote Administration) to work. In Windows 2003 this is installed by default so all that needs to be done is enable it under the remote tab under System. I do a netstat -a -o and I don't see a listening port on 3389 This Server is running Windows 2003 Server with SP1 with all critical updates. The firewall is not enabled (first thing I checked). When I run firewall.cpl, it asks if I want to enable it. The message I get from the client end is just the regular can't connect message: Remote Desktop Disconnected The client could not connect to the remote computer Remote connections might not be enabled or the computer might be too busy to accept new connections. It is possible that network problems are preventing your connection. Please try connection again later. If the problem continues to occure, contact your administrator. I had tried installing "terminal Services" - multiuser at one point and I think that is when I saw these error messages in the Event Log: Event Type: Error Event Source: TermService Event Category: None Event ID: 1036 Date: 8/22/2006 Time: 12:43:16 PM User: N/A Computer: SERVER2 Description: Terminal Server session creation failed. The relevant status code was 0xC0000034. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. I have since uninstalled "Terminal Services" and just have remote desktop enabled for administration. Is it possible to Reinstall Remote Desktop for Administration somehow??
From: Robert L [MS-MVP] on 28 Aug 2006 23:44 These case studies may help, The client could not connect to the remote computer Symptom: When trying to access TS/RDC, you may receive this error: The client could not connect to the remote computer. Remote connection might not be ... www.chicagotech.net/remoteissues/rdc2.htm Bob Lin, MS-MVP, MCSE & CNE Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com "CST112" <cst112(a)yahoo.com> wrote in message news:OSDNUXvyGHA.4576(a)TK2MSFTNGP06.phx.gbl... I have a fresh version of Windows 2003 installed and I am trying to get Terminal Services (Remote Administration) to work. In Windows 2003 this is installed by default so all that needs to be done is enable it under the remote tab under System. I do a netstat -a -o and I don't see a listening port on 3389 This Server is running Windows 2003 Server with SP1 with all critical updates. The firewall is not enabled (first thing I checked). When I run firewall.cpl, it asks if I want to enable it. The message I get from the client end is just the regular can't connect message: Remote Desktop Disconnected The client could not connect to the remote computer Remote connections might not be enabled or the computer might be too busy to accept new connections. It is possible that network problems are preventing your connection. Please try connection again later. If the problem continues to occure, contact your administrator. I had tried installing "terminal Services" - multiuser at one point and I think that is when I saw these error messages in the Event Log: Event Type: Error Event Source: TermService Event Category: None Event ID: 1036 Date: 8/22/2006 Time: 12:43:16 PM User: N/A Computer: SERVER2 Description: Terminal Server session creation failed. The relevant status code was 0xC0000034. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. I have since uninstalled "Terminal Services" and just have remote desktop enabled for administration. Is it possible to Reinstall Remote Desktop for Administration somehow??
From: CST112 on 29 Aug 2006 12:02 None of those articles seem to help. 1. I don't have any firewalls (windows or third party) running, I have installed VNC temporarily so I can access the server. 2. When I do a netstat -a -o, port 3389 doesn't show up. 3. When I check the services, terminal services is running (C:\WINDOWS\System32\svchost.exe -k termsvcs) 4. I deleted and tried recreating the rdp connection under Terminal services configuration. 5. I had checked the registry to make sure the port that it is supposed to run is 3389. How come there is nothing running on port 3389? Kevin "Robert L [MS-MVP]" <noreply(a)hotmail.com> wrote in message news:%23od3h1xyGHA.3656(a)TK2MSFTNGP04.phx.gbl... These case studies may help, The client could not connect to the remote computer Symptom: When trying to access TS/RDC, you may receive this error: The client could not connect to the remote computer. Remote connection might not be ... www.chicagotech.net/remoteissues/rdc2.htm Bob Lin, MS-MVP, MCSE & CNE Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com "CST112" <cst112(a)yahoo.com> wrote in message news:OSDNUXvyGHA.4576(a)TK2MSFTNGP06.phx.gbl... I have a fresh version of Windows 2003 installed and I am trying to get Terminal Services (Remote Administration) to work. In Windows 2003 this is installed by default so all that needs to be done is enable it under the remote tab under System. I do a netstat -a -o and I don't see a listening port on 3389 This Server is running Windows 2003 Server with SP1 with all critical updates. The firewall is not enabled (first thing I checked). When I run firewall.cpl, it asks if I want to enable it. The message I get from the client end is just the regular can't connect message: Remote Desktop Disconnected The client could not connect to the remote computer Remote connections might not be enabled or the computer might be too busy to accept new connections. It is possible that network problems are preventing your connection. Please try connection again later. If the problem continues to occure, contact your administrator. I had tried installing "terminal Services" - multiuser at one point and I think that is when I saw these error messages in the Event Log: Event Type: Error Event Source: TermService Event Category: None Event ID: 1036 Date: 8/22/2006 Time: 12:43:16 PM User: N/A Computer: SERVER2 Description: Terminal Server session creation failed. The relevant status code was 0xC0000034. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. I have since uninstalled "Terminal Services" and just have remote desktop enabled for administration. Is it possible to Reinstall Remote Desktop for Administration somehow??
From: Robert L [MS-MVP] on 29 Aug 2006 18:30 Do a simple test. Can you access the server self using remote desktop? Bob Lin, MS-MVP, MCSE & CNE Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com "CST112" <cst112(a)yahoo.com> wrote in message news:12f8p9bbc3hhmfa(a)corp.supernews.com... None of those articles seem to help. 1. I don't have any firewalls (windows or third party) running, I have installed VNC temporarily so I can access the server. 2. When I do a netstat -a -o, port 3389 doesn't show up. 3. When I check the services, terminal services is running (C:\WINDOWS\System32\svchost.exe -k termsvcs) 4. I deleted and tried recreating the rdp connection under Terminal services configuration. 5. I had checked the registry to make sure the port that it is supposed to run is 3389. How come there is nothing running on port 3389? Kevin "Robert L [MS-MVP]" <noreply(a)hotmail.com> wrote in message news:%23od3h1xyGHA.3656(a)TK2MSFTNGP04.phx.gbl... These case studies may help, The client could not connect to the remote computer Symptom: When trying to access TS/RDC, you may receive this error: The client could not connect to the remote computer. Remote connection might not be ... www.chicagotech.net/remoteissues/rdc2.htm Bob Lin, MS-MVP, MCSE & CNE Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com "CST112" <cst112(a)yahoo.com> wrote in message news:OSDNUXvyGHA.4576(a)TK2MSFTNGP06.phx.gbl... I have a fresh version of Windows 2003 installed and I am trying to get Terminal Services (Remote Administration) to work. In Windows 2003 this is installed by default so all that needs to be done is enable it under the remote tab under System. I do a netstat -a -o and I don't see a listening port on 3389 This Server is running Windows 2003 Server with SP1 with all critical updates. The firewall is not enabled (first thing I checked). When I run firewall.cpl, it asks if I want to enable it. The message I get from the client end is just the regular can't connect message: Remote Desktop Disconnected The client could not connect to the remote computer Remote connections might not be enabled or the computer might be too busy to accept new connections. It is possible that network problems are preventing your connection. Please try connection again later. If the problem continues to occure, contact your administrator. I had tried installing "terminal Services" - multiuser at one point and I think that is when I saw these error messages in the Event Log: Event Type: Error Event Source: TermService Event Category: None Event ID: 1036 Date: 8/22/2006 Time: 12:43:16 PM User: N/A Computer: SERVER2 Description: Terminal Server session creation failed. The relevant status code was 0xC0000034. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. I have since uninstalled "Terminal Services" and just have remote desktop enabled for administration. Is it possible to Reinstall Remote Desktop for Administration somehow??
From: beatphreek on 30 Aug 2006 11:11 I've had this same problem at a client's office. I've done the things you've done too. The only other clue I have is that this happened right after we installed August's updates. But it didn't affect the other servers. Any other thoughts out there on this? "CST112" wrote: > None of those articles seem to help. > > 1. I don't have any firewalls (windows or third party) running, I have > installed VNC temporarily so I can access the server. > > 2. When I do a netstat -a -o, port 3389 doesn't show up. > 3. When I check the services, terminal services is running > (C:\WINDOWS\System32\svchost.exe -k termsvcs) > 4. I deleted and tried recreating the rdp connection under Terminal > services configuration. > 5. I had checked the registry to make sure the port that it is supposed to > run is 3389. > > How come there is nothing running on port 3389? > > Kevin > > > "Robert L [MS-MVP]" <noreply(a)hotmail.com> wrote in message > news:%23od3h1xyGHA.3656(a)TK2MSFTNGP04.phx.gbl... > These case studies may help, > > The client could not connect to the remote computer Symptom: When trying to > access TS/RDC, you may receive this error: The client could not connect to > the remote computer. Remote connection might not be ... > www.chicagotech.net/remoteissues/rdc2.htm > > > Bob Lin, MS-MVP, MCSE & CNE > Networking, Internet, Routing, VPN Troubleshooting on > http://www.ChicagoTech.net > How to Setup Windows, Network, VPN & Remote Access on > http://www.HowToNetworking.com > "CST112" <cst112(a)yahoo.com> wrote in message > news:OSDNUXvyGHA.4576(a)TK2MSFTNGP06.phx.gbl... > I have a fresh version of Windows 2003 installed and I am trying to get > Terminal Services (Remote Administration) to work. In Windows 2003 this is > installed by default so all that needs to be done is enable it under the > remote tab under System. I do a netstat -a -o and I don't see a listening > port on 3389 > > This Server is running Windows 2003 Server with SP1 with all critical > updates. The firewall is not enabled (first thing I checked). When I run > firewall.cpl, it asks if I want to enable it. > > The message I get from the client end is just the regular can't connect > message: > > Remote Desktop Disconnected > The client could not connect to the remote computer > Remote connections might not be enabled or the computer might be too busy to > accept new connections. > It is possible that network problems are preventing your connection. > Please try connection again later. If the problem continues to occure, > contact your administrator. > > > I had tried installing "terminal Services" - multiuser at one point and I > think that is when I saw these error messages in the Event Log: > > Event Type: Error > Event Source: TermService > Event Category: None > Event ID: 1036 > Date: 8/22/2006 > Time: 12:43:16 PM > User: N/A > Computer: SERVER2 > Description: > Terminal Server session creation failed. The relevant status code was > 0xC0000034. > > For more information, see Help and Support Center at > http://go.microsoft.com/fwlink/events.asp. > > I have since uninstalled "Terminal Services" and just have remote desktop > enabled for administration. > > Is it possible to Reinstall Remote Desktop for Administration somehow?? > > >
|
Next
|
Last
Pages: 1 2 Prev: Active Terminal Connections Count Next: Roaming Profiles v Terminal Server Profiles |