I am not a Netware 4.x guru by any means, but the thing I noticed from your
sample, based on my NetWare 3.x experience is that there is no gateway
specified on the bind statement (gate=<  >).  Perhaps you were just over eager
setting up the sample, but if it really isn't there, you would get failures
assuming that the ADSM server is on another segment of your IP network.......


Jerry Lawson
jlawson AT thehartford DOT com
________________________Forward Header________________________
Author: INTERNET.OWNERAD
Subject: Netware 4.02 TCP/IP Error
03-24-97 04:00 PM

To: OAS     --LMS1

FROM: Betsy Moir (TTCEDM) Ext 85020
      VM Tech Services
      email:  elizabeth.moir AT vm.ssw.abbott DOT com
Subject: Netware 4.02 TCP/IP Error

I have a Netware 4.02 customer who has just installed ADSM on his Netware
file server and each time he tries to initiate the schedule he gets that
always helpful error message; TCP/IP Connection failure.  We ADSM version
1 on VM for the server and he can ping VM.

The autoexec.ncf file contains the following:

LOAD CPQTOKEN SLOT=4 FRAME=TOKEN-RING_SNAP NAME=TOKENIP
LOAD TCPIP
BIND TOKENIP ADDRESS=<    > MASK=<      >
SEARCH ADD SYS:ADSM
LOAD DSMC SCHEDULE -PASSWORD=password

He is using the latest Netware TCP/IP.

Can anybody point us in a direction for an answer to this problem? Thanks
for your help as always.

Betsy