Re: Listening To Ports
From: Joseph Whalen (jwhalen_at_ourbasement.net)
Date: Mon, 21 Jul 2003 10:46:14 -0400
You can also configure another application that starts on boot to bind to
that port (such as a personal web server). The two will conflict, and
depending on which starts first your mysterious application may shoot off an
error identifying itself. Not the cleanest way to flush it out, but it's
been effective for me in times when all other options have failed.
"Don Kelloway" <firstname.lastname@example.org> wrote in message
> "Bill Bradshaw" <email@example.com> wrote in message
> > I do not really know anything about this. I am running 98SE on a dial
> > machine. When I run netstat -an I get the following:
> > Proto Local Address Foreign Address State
> > TCP 0.0.0.0:1603 0.0.0.0:0 LISTENING
> > TCP 127.0.0.1:1025 0.0.0.0:0 LISTENING
> > Does anybody see a problem with my computer listing to ports 1603 and
> > If there is a problem what would I do about it?
> > Thanks.
> Port 1025 is listening on the loopback, which I wouldn't be too concerned
> with. What I would be concerned with is port 1603. Check to see what
> sort of applications are configured to run on startup by using the
> 'msconfig' utility. Though you may have to disable one at a time to
> determine the source.
> Best regards,
> Don Kelloway
> Commodon Communications
> Visit http://www.commodon.com to learn about the "Threats to Your Security
> on the Internet".