[Assuming a Unix box]

It seems possible that there are processes or resources still
holding onto port 1500, preventing the new instance to bind to
that port. You can determine what, if any, processes are attached
to a particular port with the 'fuser' command:

  fuser hostname:1500/tcp

This will list all processes using sockets bound or connected to
the specified port. You can also use the fuser command to send a
SIGKILL signal to each of those processes:

  fuser -k hostname:1500/tcp

(this will of course have no effect if you are not either (a) the
 owner of those processes or (b) the super-user, i.e. root).

Did the ADSM server go down cleanly/completely when you cycled
it?

 -- Tom

Thomas A. La Porte
DreamWorks Feature Animation
tlaporte AT anim.dreamworks DOT com

On Thu, 2 Dec 1999, Nick Cassimatis wrote:

>Help!
>
>I had to cycle my ADSM Server, and on startup, I'm getting an ANR8208W.  I
>have to start the server in the foreground to see this, since it means I
>can't start sessions on TCPIP Port 1500.  Here's the help text:
>
>adsm> h anr8208
>-------------------------------------------------------------------------------
>
>ANR8208W  TCP/IP DRIVER UNABLE TO INITIALIZE DUE TO ERROR IN BINDING TO
>PORT
>port, REASON CODE reason code.
>
>EXPLANATION:  While initializing TCP/IP communications, ADSM fails to
>connect
>to a master socket on which to listen for clients.  The reason code is the
>return code from the TCP/IP bind API.
>
>SYSTEM ACTION:  Server operation continues, but the server cannot accept
>sessions from clients using the TCP/IP protocol.
>
>USER RESPONSE:  Ensure that no other application is using the port number
>specified in the server options file with the PORT option by issuing the
>TCP/IP
> netstat command. If HTTP is also in use for ADSM client sessions, ensure
>that
>the same port number is not specified for both TCP/IP and HTTP
>communications.
>If the server was brought down and client sessions were active, it may be
>necessary to terminate the client sessions on the client systems before the
>port can be freed.
>
>I did all of this, but netstat is still showing a bunch of sessions on port
> 1500.  How do I clear sessions off of the ports?
>
>Nick Cassimatis
>nickpc AT us.ibm DOT com
>
>If you don't have the time to do it right the first time, where will you
>find the time to do it again?
>