ADSM-L

Re: strange TCP/IP err on Novell

1998-03-09 10:04:14
Subject: Re: strange TCP/IP err on Novell
From: Mike Castillo <mcastill AT UTEP DOT EDU>
Date: Mon, 9 Mar 1998 08:04:14 -0700
   Hey Matthew,
     I had the same scenario occur with adsm,even though I am running it
on VM. After speaking with IBMLINK,They said to increase the Commitimeout
and the idletimeout.I have commtimeout=600 and idletimeout=90.Hope this
helps...








Michael A.Castillo
Information and Technology Services
University of Texas at El Paso
Systems Software Specialist
Phone:(915)747-6303
Fax:(915)747-5067
E-Mail:mcastill AT utep DOT edu

On Mon, 9 Mar 1998, Matthew Warren wrote:

> Hello all,
>
>         I am new to using the ADSM client on Novell platforms, 3.1x and
> have a strange problem.
>         The Novell server can ping the ADSM box, & the ADSM box can ping
> the Novell server but whenever DSMC tries to connect with the ADSM box
> it returns the TCP/IP connection failure below:
>
> TcpOpen: TCP/IP error connecting to server.
> sessOpen: Failure in communications open call. rc: -50
>
>         I have checked dsm.opt etc.. and I was wondering if anyone had
> seen anything similar or if there are any peculiarities of setting up &
> using the DSMC client on Novell 3.1x that could explain it.
>
> Thanks,
>
> Matthew Warren,
> ADSM(FAB) & Unix support.
>         HOIST : Head Office Infrastructure Support Team.
>         Marks & Spencer PLC
>         Michael House
>         Baker Street
>         London.
>
>
>         Tel: 01712681522
>         Mail: matthew.warren AT marks-and-spencer DOT com
>
<Prev in Thread] Current Thread [Next in Thread>