The Scheduler is running on the PC.
There is only the one session.
And.. it happens on my machine as well as others! I have tried different
things but I have found that
if I kill the session that is trying to connect and start a new one it
will connect and backup.
 Hmmmm?

CR
__________________________
Cris Robinson
Sr. Telecommunications Analyst
Liberty Mutual Insurance
cris.robinson AT libertymutual DOT com
(603) 431-8400 Ext. 54837


> -----Original Message-----
> From: Dennis Riley [SMTP:riley AT TIMKEN DOT COM]
> Sent: Tuesday, October 07, 1997 12:24 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Cannot Connect to Win95 client
>
> Is the Scheduler client running on the PC at the time? Or is there
> already
> a Backup client session active?
>
> Dennis Riley               riley AT timken DOT com
> Technical Principal        330-471-3515
> The Timken Company         Canton, OH
>
> On Tue, 7 Oct 1997, Robinson, Cris wrote:
>
> > Actually that is in there as:
> >
> >  TCPServeraddress LMIG-ADSM-02
> >
> >
> > Any other Ideas?
> >
> > CR
> >
> > > -----Original Message-----
> > > From: Moir,Elizabeth [SMTP:Betsy.Moir AT ABBOTT DOT COM]
> > > Sent: Tuesday, October 07, 1997 10:32 AM
> > > To:   ADSM-L AT VM.MARIST DOT EDU
> > > Subject:      Cannot Connect to Win95 client
> > >
> > > To: OAS     --LMS1
> > >
> > > FROM: Betsy Moir (TTCEDM) Ext 85020
> > >       VM Tech Services
> > >       email:  betsy.moir AT abbott DOT com
> > > Subject: Cannot Connect to Win95 client
> > >
> > > It appears you're missing the TCPServerAddress.  This is what our
> > > standard
> > > options file looks like.  Hope this helps.
> > >
> > >  COMMmethod                 TCPIP
> > >       TCPServeraddress      vm
> > >       TCPPort              1501
> > >       NODEname             default
> > >
> > > Betsy
> > > *** Forwarding note from OWNERAD1--INTERNET 97/10/07 09:16 ***
> > >
> > >
> > >
> > >
> > >
> > > TO:         NOREPLY  INTERNET  ADSM-L AT VM.MARIST DOT EDU
> > > FROM:       OWNERAD1 INTERNET  owner-adsm-l AT VM.MARIST DOT EDU
> > > DATE:       10/07/97 09:16
> > > SUBJECT:    Cannot Connect to Win95 client
> > > OK - here's one to kick around.  We get this message in the server
> > > activity log in the morning. Apparently ADSM attempts to connect
> to
> > > the
> > > machine but is unable to connect to the client. ( This is just a
> > > snipit
> > > of the log. We actually get quite a few of these. )
> > > Every Win 95 client has the same options file, with the exception
> of
> > > the
> > > nodename of course.
> > >
> > > Here are the DSM.OPT parameters:
> > >
> > >
> > >
> > >         ******* COMMUNICATION SETTINGS *******
> > >
> > >         COMMmethod TCPIP
> > >         TCPPort 1500
> > >         TCPBUFFSIZE 32
> > >         TCPWINDOWSIZE 64
> > >         SLOWINCR NO
> > >
> > >         SCHEDMODE PROMPTED
> > >
> > >
> > > Here is the activity log:
> > >
> > >
> > > Actitvity Log
> > > -------------
> > > Date and Time        Message
> > >
> > >
> ----------------------------------------------------------------------
> > > --
> > > ------------------------------------------------------------
> > > 10/06/1997 22:01:50  ANR8213W Session open with 136.184.149.182
> timed
> > > out.
> > > 10/06/1997 22:01:50  ANR2716E Schedule prompter was not able to
> > > contact
> > > client C07837784-0055 using type 1 (136.184.149.182 1501).
> > > __________________________
> > > Cris Robinson
> > > Sr. Telecommunications Analyst
> > > Liberty Mutual Insurance
> > > cris.robinson AT libertymutual DOT com
> > > (603) 431-8400 Ext. 54837
> >