ERROR! Some other process is using this port!

[dimpan]

<11/27/06@00:58:57> [SHOUTcast] DNAS/win32 v1.9.5 (Dec 27 2004) starting up...
<11/27/06@00:58:57> [main] loaded config from C:\Program Files\SHOUTcast\sc_serv.ini
<11/27/06@00:58:57> [main] initializing (usermax:32 portbase:8000)...
<11/27/06@00:58:57> [main] No ban file found (sc_serv.ban)
<11/27/06@00:58:57> [main] No rip file found (sc_serv.rip)
<11/27/06@00:58:57> [main] opening source socket
<11/27/06@00:58:57> [main] source thread starting
<11/27/06@00:58:57> [main] opening client socket
<11/27/06@00:58:57> [main] error opening client socket! FATAL ERROR! Some other process is using this port!

[djSpinnerCee]

SrcIP=DestIP=Any

Don't change these unless you're a hosting company and know what you're doing. Changing either of these will not get rid of "cannot see your station..." [NAK] errors.

If you didn't change them, try changing PortBase to 8002 and see what happens. If you really have something running on that port, just choose another one.

The message is somewhat erroneous (the "why" part anyway), just like many of the DNAS error messages -- if you put an IP in SrcIP/DestIP that is not one of the PCs real IP addresses, the DNAS will not be able to bind the listen socket.

[SLR]

Usually, this error means that you are -

a) already running a Shoutcast server on that port
b) or running another programme that utilises a port to communicate to and from the internet

My bet is a). Check your task manager for sc_serv (at least one if not two listings).

[djSpinnerCee]

Here's how you can be pretty sure it's not another DNAS:

<11/27/06@00:58:57> [main] opening source socket
<11/27/06@00:58:57> [main] source thread starting

The source socket [PortBase+1] was opened successfully -- if this is another DNAS running, both the source and client (listener) sockets would fail.

<11/27/06@00:58:57> [main] opening client socket
<11/27/06@00:58:57> [main] error opening client socket! FATAL ERROR! Some other process is using this port!

Most of the time, a broadcaster has changed DestIP to the router's public IP in an atttempt to fix the NAK error -- the socket cannot be bound to an IP that does not exist on the local box.

All used ports can be found with netstat -na | more -- you're looking for TCP ports that are in the LISTENING state, but it is also possible that a client app like the browser has temporarily used one of the DNAS ports for a source (outgoing) socket, and it hasn't been automatically freed at the time the DNAS attempted to start -- extremely rare, but not unlikely.