Re: port 3389 Not listening remote desktop connection
- From: "BishopNB" <BishopNB@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 22 Jul 2005 08:34:02 -0700
Go to a command prompt and type in the following
c:\>netstat -na |more
It should display what IP addresses and ports your machine is mapping.
Something like this:
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:25 0.0.0.0:0 LISTENING
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1040 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1433 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2967 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3908 0.0.0.0:0 LISTENING
Look for the one that says 3389 like what I have above. Is it listed on
yours? Is it listening? If it's not listed then TS isn't running. Let me
know.
"Sooner Al [MVP]" wrote:
> I think that the repair installation is your best option at this point. Note
> the warnings on the page. I also recommend backing up sensitive data as a
> precaution.
>
> --
>
> Al Jarvi (MS-MVP Windows Networking)
>
> Please post *ALL* questions and replies to the news group for the mutual
> benefit of all of us...
> The MS-MVP Program - http://mvp.support.microsoft.com
> This posting is provided "AS IS" with no warranties, and confers no
> rights...
>
>
> "coxwj" <coxwj@xxxxxxx> wrote in message
> news:1121714518.912290.20720@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > Rebooting regsvr32 had no affect. Any other suggestions before I do a
> > repair? I would really like to use that as a last option, as the rest
> > of computer has no problems at all, not to mention it is a server that
> > I use on a daily basis.
> >
> > What about my original thread, is there a way to force that port to
> > listen?
> >
> > Also, is this a problem that other folks do not have? I seem to find
> > many threads on "Port 3389 NOT LISTENING", but no real answers ever
> > surface, or they simply didn't enable Remote Desktop Connection in the
> > first place. I find it strange that instruction on setting up a RDC
> > often ask you to check netstat -a to see if 3389 is listening, but then
> > never tell you how to proceed if it is not. Am I alone on this?
> >
>
>
>
.
- Follow-Ups:
- References:
- port 3389 Not listening remote desktop connection
- From: coxwj
- Re: port 3389 Not listening remote desktop connection
- From: Sooner Al [MVP]
- Re: port 3389 Not listening remote desktop connection
- From: coxwj
- Re: port 3389 Not listening remote desktop connection
- From: Sooner Al [MVP]
- Re: port 3389 Not listening remote desktop connection
- From: coxwj
- Re: port 3389 Not listening remote desktop connection
- From: Sooner Al [MVP]
- port 3389 Not listening remote desktop connection
- Prev by Date: Re: Wireless vnc question
- Next by Date: Re: Wireless vnc question
- Previous by thread: Re: port 3389 Not listening remote desktop connection
- Next by thread: Re: port 3389 Not listening remote desktop connection
- Index(es):
Relevant Pages
|