Article View: comp.os.netware.misc
Article #208Re: Btrieve v6.x Socket Connection Problems
From: raym
Date: Sat, 28 Sep 1996 00:00
Date: Sat, 28 Sep 1996 00:00
44 lines
1603 bytes
1603 bytes
On Thu, 26 Sep 1996 19:35:26 -0700, Jay Malone <malone@cts.com> wrote: >OK Gang..... > >Here's my Problem..... > >I've got clients who are running NetWare v4.1 and v3.12. > >They're using Btrieve NLM (mostly v6.15, some v6.10) and periodically >they ALL get a Btrieve Status 95 error (SPX connection lost). > >It appears that the SPX socket connection is being corrupted between the >NCP snd Btrieve's SPX manager. > >Anyone else having this problem? > >All are patched with 312PT7 or 312PT8 (current). > >It's not hardware (different vendors), nor is it traffic related >(segments are clean). > >So far, Btrieve hasn't had much info. > >Any help would be appreciated! > >-- >Jay Malone > >jmalone@esicorp.com > >Magician..........Photographer.......Network GOD........ >Certified Expert at Work Avoidance (though SOME may say certifiable) > > >"I may do nothing........BUT I do it extremely WELL" I had the same problem with a client. The problem turned out to be in the wiring. ------ Ray Markarian raym@ix.netcom.com
Technical Details
Message-ID:
<324c8370.9879922@nntp.ix.netcom.com>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<324B3D6E.37B2@cts.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fe659,93e8e491c57700f4 X-Google-Attributes: gidfe659,public X-Google-Thread: f8bf7,93e8e491c57700f4 X-Google-Attributes: gidf8bf7,public From: raym@ix.netcom.com Subject: Re: Btrieve v6.x Socket Connection Problems Date: 1996/09/28 Message-ID: <324c8370.9879922@nntp.ix.netcom.com> X-Deja-AN: 185779756 references: <324B3D6E.37B2@cts.com> organization: Netcom x-netcom-date: Fri Sep 27 8:49:44 PM CDT 1996 newsgroups: comp.os.netware.misc,bit.listserv.novell