ports 3260-3261 are open, why?

If someone knows of a more appropriate group to ask this, please let me
know. I have a windows XP service pack 2 box, with fairly recent updates.
Just for grins, I wanted to run a port scan against myself from another
machine on the net to make sure only the ports I wanted open were open, and
that all others were closed.
My test of all ports on my machine showed my FTP port open, as expected,
and most other ports closed. I say most other ports, because ports 3260 and
3261 came up as open. The only server I'm running is my FTP server on the
standard 21. Does anyone know why on earth ports 3260 and 3261 would be
open? What would they be used for, and what service should I shut down to
make those ports closed as they should be?

Re: ports 3260-3261 are open, why?

P2PDude wrote:
> If someone knows of a more appropriate group to ask this, please let me
> know. I have a windows XP service pack 2 box, with fairly recent updates.
> Just for grins, I wanted to run a port scan against myself from another
> machine on the net to make sure only the ports I wanted open were open, and
> that all others were closed.
> My test of all ports on my machine showed my FTP port open, as expected,
> and most other ports closed. I say most other ports, because ports 3260 and
> 3261 came up as open. The only server I'm running is my FTP server on the
> standard 21. Does anyone know why on earth ports 3260 and 3261 would be
> open? What would they be used for, and what service should I shut down to
> make those ports closed as they should be?
Googled for "port 3260" and found this:
iSCSI... scsi over internet

If you are not using this, you don't need it.

Re: ports 3260-3261 are open, why?

netstat -anbo

Re: ports 3260-3261 are open, why?

none wrote:

> Googled for "port 3260" and found this:
> iSCSI... scsi over internet
>
> If you are not using this, you don't need it.

iSCSI Initiator is not available for Windows XP.
Beside that, it seems like you don't understand the concept of port
number associations. When you're using iSCSI, you're supposed to use
that port - the contrary doesn't hold.

Re: ports 3260-3261 are open, why?

Sebastian Gottschalk wrote in news:4ceqagF154c3gU2
@news.dfncis.de:

> netstat -anbo
>

That command helped me alot, thanks. Ports 3260 and 3261 appear to be open
by something called StarWindService.exe. Now I'm off to find out what on
earth that is, since I've never heard of it before, but at least I know
what program is opening those ports for connections, even if I don't yet
know what on earth that service does. Thanks for that command.

Re: ports 3260-3261 are open, why?

P2PDude wrote:
> Ports 3260 and 3261 appear to be open
> by something called StarWindService.exe. Now I'm off to find out what on
> earth that is, since I've never heard of it before,

It's a service installed by Alcohol 120%. Get rid of this crap.

Re: ports 3260-3261 are open, why?

Sebastian Gottschalk wrote:
> none wrote:
>
>
>>Googled for "port 3260" and found this:
>>iSCSI... scsi over internet
>>
>>If you are not using this, you don't need it.
>
>
> iSCSI Initiator is not available for Windows XP.
Apologies if my attempt to help was inaccurate. Fortunately you helped
the OP find the problem, and I guess that all's well that ends well.
> Beside that, it seems like you don't understand the concept of port
> number associations. When you're using iSCSI, you're supposed to use
> that port - the contrary doesn't hold.
Indeed. I do realise this, just jumped to conclusions.. was on my way
out and did not think, not that that is any excuse.

Re: ports 3260-3261 are open, why?

P2PDude wrote:
> Does anyone know why on earth ports 3260 and 3261 would be
> open?

C:\> netstat -anb | more

Yours,
VB.
--
At first there was the word. And the word was Content-type: text/plain

Re: ports 3260-3261 are open, why?

Volker Birk wrote:

> C:\> netstat -anb | more

If your list isn't obscenely long, you can simply use the scrolling of
the command window instead of 'more'...