From: buhr@umanitoba.ca (Kevin Andrew Buhr)
Subject: Re: NetWare Requester 2.0 error....
Organization: University of Manitoba, Canada
Date: Thu, 17 Dec 1992 00:24:54 GMT

In article <Bz48nI.6u@constellation.ecn.uoknor.edu>
callison@uokmax.ecn.uoknor.edu (James P. Callison) writes:

|  I'm having trouble getting my OS/2 2.0 machine to work with my NetWare 3.11
|  network. On startup, everything seems to load normally, until a few
|  seconds after the desktop loads, when I get a blank screen with a 
|  red box at the top with the message :
|
|	   NWD0115: Error getting connection ID (0x880F).
|		   Press <Esc> to continue
|
|  After I press <Esc>, I get the desktop back, with this most unhelpful
|  message:
|
|	   SYS0059: An unexpected network error occurred
|
|  Doing a help on this message gets me another un-helpful message about
|  seeing my system administrator. Well, I'm the system administrator,
|  and I don't have a clue as to what this error is...

I got this message when I forget to tell the "NE2000.OS2" MLID that
"Frame Ethernet_802.3" was the first frame supported (and therefore
the frame that "IPX.SYS" should bind to.  "IPX.SYS" was binding to the
"Ethernet_II" frame on the same physical board, and the Requestor
exhibited exactly the behaviour you describe (right down to the
"0x880f").

DOS MLID's and Protocol drivers seem to make up their own rules, so a
"NET.CFG" that works for a DOS session doesn't always work under OS/2.
Moreover, all Netware's OS/2 drivers are incredibly buggy: sometimes
an (incorrect) "NET.CFG" will successfully boot, but some totally
unrelated change (like changing the "Slot" parameter, for example ;) )
will cause it to fail afterwards.

In short, try this (and I'm doing this from memory, so take it with a
grain of salt):

If your CONFIG.SYS looks like this...

	DEVICE=C:\NETWARE\LSL.SYS
	DEVICE=C:\NETWARE\3C503.OS2 (or whatever)
	DEVICE=C:\NETWARE\IPX.SYS
		.
		.
		.

then make sure your C:\NET.CFG looks like this...

	Link Driver 3c503 (or whichever board you use under OS/2)
		Slot ???  (if your MLID is going to have trouble
                           deciding which board is which)
		Frame Ethernet_802.3 (assuming your IPX is framed thusly)
		Frame Ethernet_II	(or whatever)
		Protocol IPX 0 Ethernet_802.3 (just to make it explicit)

	Link Driver 3c509
		Slot ???
		Frame Ethernet_802.3 (or whatever)
		Protocol IPX 0 Ethernet_802.3

|  I have two ethernet adapters; a 3Com 3c509 (for DOS) and a 3c503 (8-bit)
|  for OS/2 and Linux. I use the NET.CFG to separate them, and, when I
|  had this same copy of OS/2 installed on my 386 (without the ServPak),
|  I had no problems.

Hopefully, the OS/2 "IPX.SYS" will bind to the first virtual board it
sees (the Ethernet_802.3 frame of the "3c503" MLID).  In a DOS
session, provided you load the "3c509" MLID only, the DOS "IPXODI.COM"
will bind to the first virtual board of the first available MLID, i.e.
the Ethernet_802.3 frame of the "3c509" MLID.  If this is the desired
behaviour, then you're in luck.

If you find you simply can't reconcile the DOS and OS/2 "NET.CFG"'s,
I've found that Netware DOS ODI drivers seem to look for the "NET.CFG"
file in the current directory, so if you run them from "C:\DOSNW",
they'll find a DOS-only "NET.CFG" in that directory.

Anyway...  Good luck!

Kevin <buhr@ccu.UManitoba.CA>
Newsgroups: comp.os.os2.networking