Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!wuarchive!rex!ames!excelan!bdelvecc
From: bdelvecc@kinetics.com (Brian Del Vecchio)
Newsgroups: comp.sys.novell
Subject: Re: File Service Packets...
Summary: NCP, packet structure unpublished
Message-ID: <2516@excelan.COM>
Date: 26 Dec 90 20:55:55 GMT
References: <2437.275e0b97@waikato.ac.nz>
Sender: news@excelan.COM
Organization: Novell, Walnut Creek CA.
Lines: 18

In article <2437.275e0b97@waikato.ac.nz>, hamish@waikato.ac.nz writes:
> Can anyone tell me what file service request packets, and their response look
> like (ie fields, values etc). 
> 
I believe that the packet structure is not published by Novell.  Instead,
the API is documented at the software interrupt level, and a C library
interface to the API is provided for DOS and OS/2 clients.  There is also
a Mac client API available, but I know less about it.

If you have a top-of-the-line LAN protocol analyzer like the Novell LANalyzer
or the Network General Sniffer, you can use this to decode NCP packets.
I think that with the combination of the API reference and the packet decodes
there is very little you can't figure out.
[----------------------------------------------------------------------------]
  brian del vecchio; software engineer; novell, inc.; walnut creek, ca, usa;
	"But for what purpose was the earth formed?" asked Candide.
	"To drive us mad," replied Martin.	  - Voltaire, _Candide_
[---the opinions expressed are mine...the official Big Red Word may differ---]