[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 395
  • Last Modified:

Server 2003 Terminal Services No port 3389

I have a 2003 Terminal Server that started having problems a week ago.  Users would login and just get a grey screen.  If I reboot the terminal server, users can't login at all.  I discovered by running netstat -an that port 3389 wasn't listening.  If I go to terminal services configuration and click on the network adapter tab NOTHING SHOWS UP!  I tried this http://support.microsoft.com/kb/555382, and no luck.  I reload the server from image backup and it works for about a half day and then the same thing happens.  I created a new 2003 load from scratch and again about a half day later the same thing happens (I have done this twice).  The server is very simple and just runs Office 2007.  The server runs on ESXi 4.1 Update 1.  I updated to VMware ESXi5 and the same thing is happening.  Please help!!!
0
etechit
Asked:
etechit
1 Solution
 
L4NetCommented:
Since you're observing port 3389 is not listening from the VM's NIC (internally referenced), it makes me wonder if there isn't some sort of firewall app that's shutting down 3389 from within the terminal server.  Externally, ESX wouldn't have any negative effect on 3389, and even if you limited 3389 by Edge or another firewall, you'd still be seeing the VM listening on 3389 from an internal VM check such as netstat.  That's why I'm thinking of some internal app or function that's disabling 3389 from within the VM.  

Are there any 3rd endpoint apps installed (and maybe recently updated) that provide firewall capabilities?  The regularity of the issue also points to some app or process that's updated every half day or so.
0
 
ChiefITCommented:
There was an issue with SP2 and the Terminal services listening port. Please check out this thread:

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Remote_Desktop-Terminal_Services/Q_23577994.html
0
 
etechitAuthor Commented:
It was a bad printer driver jamming up the print spooler service.  Restart print spooler service and users could log in.
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now