Re: Can't connect to Terminal Services following upgrade of Win 2003 to service pack 1

Tech-Archive recommends: Fix windows errors by optimizing your registry


Vera Noest [MVP] wrote:
Anything in the EventLog on the server?
Is the server listening on port 3389? Check by typing "netstat -
an" at a command prompt.

If "no" to both questions, try with a second reboot.

I've done a netstat -an and it says that port 3389 is Established NOT
listening. Is this the probelm? If so, how do I make it listen??? I've
tried a re-boot, but it still looks the same,

Thanks for the advice

Colin

.

Relevant Pages

  • Re: Netstat results - problem?
    ... listening corresponding to a port. ... Luca Vix Visconti wrote: ... >> Have I a trojan or does this look like normal netstat logs? ...
    (comp.security.misc)
  • Re: Best Plan of action for 2 forest.......
    ... PortQry reports the status of a port in one of the following ways: ... ..LISTENING This response indicates that a process is listening on the target ...
    (microsoft.public.windows.server.active_directory)
  • Re: Cant connect to Terminal Services following upgrade of Win 2003 to service pack 1
    ... Is the server listening on port 3389? ... - an" at a command prompt. ... I've done a netstat -an and it says that port 3389 is ...
    (microsoft.public.windows.terminal_services)
  • Re: Tomcat Doesnt Seem To Start In Fedora 8
    ... The result of netstat is ... If I understand the above correctly, something is indeed listening on port 8080...but what? ... I also grepped on '80' to list processes running on any 80xx port. ...
    (Fedora)
  • Re: RealVNC
    ... If we are talking about RealVNC it goes this way ... Then there is default Java listening port on port 5800 on the client machine ...
    (microsoft.public.windows.server.sbs)