Joseph,
        It sounds as though the TCPIP port (usually 1500) ADSM uses was not
defined in the TCPIP profile dataset... Besides defining this in the
ADSM option file, this also needs to be defined to TCPIP so it knows
what port to listen on for ADSM stuff.  This file is usually a text file
that can be edited... TCPIP will probably need to be recycled for the
change to take effect.

Tim Pittson
tpittson AT himail.hcc DOT com

>----------
>From:  Michael & Judi Bryant[SMTP:bryants AT PRIMENET DOT COM]
>Sent:  Monday, May 27, 1996 1:31 PM
>To:    Multiple recipients of list ADSM-L
>Subject:       Re: ADSM setup
>
>Joseph,
>Can't help you on the TCP/IP error, I am not at work and don't have my
>manuals. The second error normally is when you have not defined the
>client
>node to the administrator (server).  When you configured the client you
>should have given it a NODE name.  This NODE name must also be defined
>on
>the server if you have set registration to closed.
>
>Hope this helps,
>Michael Bryant
>Sherlocks Inc.
>Minnetonka, MN
>
>
>At 10:13 PM 5/27/96 +0800, T.JOSEPH TAN wrote:
>>Good day,
>>
>>I am setting up an ADSM server & client server.  I am using TCP/IP as the
>>communication device.  I have two problem and could like to hear your
>>advise:-
>>
>>1). At the startup of ADSM server, at the line of TCP/IP.. the error
>>message:
>>    "Error opening TCP/IP socket, error code 10022"
>>2). At the client icon, after clicking to open up the icon.. the error
>>message:
>>    "ANS4353E Session rejected
>>     Unknown ID entered"
>>
>>I hope you could assist me in those problem, thanks!!
>>
>>_____________________________
>>Joseph Tan
>>
>>
>