Port 3389 is not listening in Windows 2003 Server
in [Terminal Services]
|
From: John Smith on 26 Oct 2006 02:08 I have a Windows 2003 server with SP1 that used to run Remote Desktop just fine. We rebooted it yesterday and after the reboot, Remote Desktop won't work. 1. We don't have any firewalls (windows or third party) running 2. When I do a netstat -an, port 3389 doesn't show up. 3. When I check the services, terminal services is running, but cannot be stopped or started 4. I deleted and tried recreating the rdp connection under Terminal services configuration but no help 5. I had checked the registry and am sure the port 3389 is configured 6. I am sure Remote Desktop is checked in the Remote property 7. "RDP-Tcp (listener)" does not show up under the TerminalServices Manager Any suggestion? Thanks.
From: Vera Noest [MVP] on 26 Oct 2006 07:47 This problem has been reported here quite a number of times the past few weeks. Have you tried a second reboot? Most posters have reported that that fixes the problem (until the next reboot, that is). _________________________________________________________ Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server TS troubleshooting: http://ts.veranoest.net *----------- Please reply in newsgroup -------------* "John Smith" <nzsms(a)hotmail.com> wrote on 26 okt 2006: > I have a Windows 2003 server with SP1 that used to run Remote > Desktop just fine. We rebooted it yesterday and after the > reboot, Remote Desktop won't work. > > 1. We don't have any firewalls (windows or third party) running > 2. When I do a netstat -an, port 3389 doesn't show up. > 3. When I check the services, terminal services is running, but > cannot be stopped or started > 4. I deleted and tried recreating the rdp connection under > Terminal services configuration but no help > 5. I had checked the registry and am sure the port 3389 is > configured 6. I am sure Remote Desktop is checked in the Remote > property 7. "RDP-Tcp (listener)" does not show up under the > TerminalServices Manager > > Any suggestion? Thanks.
From: Ramon Niese on 30 Oct 2006 09:45 Hi, We had a similar problem. Problem was solved by selecting the correct NIC under terminalservices configuration. Ramon "Vera Noest [MVP]" <Vera.Noest(a)remove-this.hem.utfors.se> schreef in bericht news:Xns98688C4CB1479veranoesthemutforsse(a)207.46.248.16... > This problem has been reported here quite a number of times the past > few weeks. > Have you tried a second reboot? Most posters have reported that that > fixes the problem (until the next reboot, that is). > > _________________________________________________________ > Vera Noest > MCSE, CCEA, Microsoft MVP - Terminal Server > TS troubleshooting: http://ts.veranoest.net > *----------- Please reply in newsgroup -------------* > > "John Smith" <nzsms(a)hotmail.com> wrote on 26 okt 2006: > >> I have a Windows 2003 server with SP1 that used to run Remote >> Desktop just fine. We rebooted it yesterday and after the >> reboot, Remote Desktop won't work. >> >> 1. We don't have any firewalls (windows or third party) running >> 2. When I do a netstat -an, port 3389 doesn't show up. >> 3. When I check the services, terminal services is running, but >> cannot be stopped or started >> 4. I deleted and tried recreating the rdp connection under >> Terminal services configuration but no help >> 5. I had checked the registry and am sure the port 3389 is >> configured 6. I am sure Remote Desktop is checked in the Remote >> property 7. "RDP-Tcp (listener)" does not show up under the >> TerminalServices Manager >> >> Any suggestion? Thanks.
From: pvledoux on 1 Nov 2006 08:23 Hi, we had exactly the same problem with one server. I also tried to delete and recreate the rdp-tcp listener because it was no visible any more in the Terminal Services Manager. But when I recreated it, I named it "TCP", not 'RDP-Tcp'. I don't know if it was the problem, but I delete the 'TCP' listener and recreate a 'RDP-Tcp'. Then I bind it to only one nic interface (like mention in the previous quote), I rebooted, and now it works. I think that RDP still sorcelery! Regards, Pv Ledoux Ramon Niese a écrit : > Hi, > > We had a similar problem. Problem was solved by selecting the correct NIC > under terminalservices configuration. > > Ramon > > "Vera Noest [MVP]" <Vera.Noest(a)remove-this.hem.utfors.se> schreef in bericht > news:Xns98688C4CB1479veranoesthemutforsse(a)207.46.248.16... > > This problem has been reported here quite a number of times the past > > few weeks. > > Have you tried a second reboot? Most posters have reported that that > > fixes the problem (until the next reboot, that is). > > > > _________________________________________________________ > > Vera Noest > > MCSE, CCEA, Microsoft MVP - Terminal Server > > TS troubleshooting: http://ts.veranoest.net > > *----------- Please reply in newsgroup -------------* > > > > "John Smith" <nzsms(a)hotmail.com> wrote on 26 okt 2006: > > > >> I have a Windows 2003 server with SP1 that used to run Remote > >> Desktop just fine. We rebooted it yesterday and after the > >> reboot, Remote Desktop won't work. > >> > >> 1. We don't have any firewalls (windows or third party) running > >> 2. When I do a netstat -an, port 3389 doesn't show up. > >> 3. When I check the services, terminal services is running, but > >> cannot be stopped or started > >> 4. I deleted and tried recreating the rdp connection under > >> Terminal services configuration but no help > >> 5. I had checked the registry and am sure the port 3389 is > >> configured 6. I am sure Remote Desktop is checked in the Remote > >> property 7. "RDP-Tcp (listener)" does not show up under the > >> TerminalServices Manager > >> > >> Any suggestion? Thanks.
|
Pages: 1 Prev: RDP_Tcp (Listener) missing from Terminal Services Manager Next: Shadow Console on XP Pro SP2 |