Archived from groups: microsoft.public.broadbandnet.hardware (
More info?)
Except that the error message makes me think that the application that wants
to listen on 6515 is not able to do so and therefore may not be running...
Hence, it won't show up on netstat.
I would suggest grabbing a copy of "autoruns" from
http://www.sysinternals.com/ntw2k/freeware/autoruns.shtml
and then compare what you actually have running to the list of things that
autoruns tells you will run during startup. The missing application(s) will
narrow down the suspect list for the application that wants to use 6515 and
might help you figure out what to do next.
HTH
"Jason Tsang" <jason-onlineDEL@ETEmvps.org> wrote in message
news:uXBafyRJEHA.3712@TK2MSFTNGP09.phx.gbl...
> To see what is using port 6515, use netstat -ao from the command prompt
>
> You should then be able to see the PID that is listening on port 6515.
> Record that PID, and then type "tasklist" and see what task is using port
> 6515.
>
> --
> Jason Tsang - Microsoft MVP
>
> Find out about the MS MVP Program -
>
http://mvp.support.microsoft.com/default.aspx
>
> "KN" <anonymous@discussions.microsoft.com> wrote in message
> news:075d01c42517$4e4c8650$a601280a@phx.gbl...
> > My system when booting up is giving the message "Unable to
> > listen to Port 6515. Make sure that the TCP/IP transport
> > is set up correctly and no other application is already
> > listening to the port"
> >
> > If anyone cud help me solve this problem, that wud be gr8
> >
> > Regards
> >
> > KN
>
>
Facebook
Twitter
Instagram