Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!zaphod.mps.ohio-state.edu!wuarchive!mailrus!usenet.ins.cwru.edu!eagle!news
From: xxseub@osprey (Steven Eubanks)
Newsgroups: comp.protocols.nfs
Subject: PC-NFS/NDIS Netbind error?
Keywords: PC-NFS, NDIS, Netbind, Ungermann-Bass
Message-ID: <1990Aug7.202022.10064@eagle.lerc.nasa.gov>
Date: 7 Aug 90 20:20:22 GMT
Reply-To: xxseub@osprey (Steven Eubanks)
Organization: NASA/Lewis Research Center, Cleveland
Lines: 88


	I'm just beginning to test PC-NFS against U-B's NDIS driver and am
experiencing problems.  While starting up PC-NFS, I get an error when
NETBIND executes:

	Sun Microsystems PC-NFS Network File System
	Version 3.0.1
	Serial # ---------
	Copyright (c) ------------
	Copyright (c) ------------

	MS DOS LAN Manager Protocol Manager v1.1

	Sun Microsystems PC-NFS(R) NDIS Interface Driver Version 0.2
	Copyright (c) 1989, 1990 Sun Microsystems, Inc.

	UBNEI$: Initialization started.

	UBNEI$: Initialization succeeded.

	MS DOS LAN Manager Netbind v1.1
--->	PRO0025E Failed to bind

	C> NET START RDR ws-name *

	NFS908F Configuration error - LANMAN NETBIND must be run before NFSRUN

Has anyone else seen this and/or are aware of the cause?  I'm currently
using v0.2 of the PC-NFS NDIS Interface Driver (June 26 1990), and to
the best of my knowledge have tried to follow both the instructions that
came with the compatibility kit as well as those that came from U-B. I am
running NFSRUN directly after NETBIND.  And my CONFIG.SYS and PROTOCOL.INI
files look as follows:

--------------------
	FILES=30
	BUFFERS=40
	FCBS=16,8
	LASTDRIVE=V
	BREAK=ON
	SHELL=\COMMAND.COM /E:500 /P
	DEVICE=\DOS\ANSI.SYS
	DEVICE=D:\NFS\PCNFS.SYS
	DEVICE=D:\NFS\SOCKDRV.SYS
	DEVICE=\LANMAN\PROTMAN.SYS
	DEVICE=\LANMAN\NFS-NDIS.SYS 
	DEVICE=\LANMAN\UBNEI.DOS

----------------------

;		Test PROTOCOL.INI for UBNEI and PC-NFS
;
;		S W Eubanks, 3 Aug 1990
;
; A strange melding of U-B and Sun example .INI files
;

[protocol manager]
    drivername = PROTMAN$

[UBNEI]
;	Note that many of these parameters have default values (which are
; given below under "Comments about UBNEI parameters"). A parameter need not
; be specified in your PROTOCOL.INI if its default value is satisfactory.
    DriverName = UBNEI$
    AdapterType = Personal NIU
    MemoryWindow = 0xD0000
    IO_Port = 0x360
    IRQ_Level = 2
    MaxRequests = 6
    MaxTransmits = 6
    ReceiveBufSize = 600
    MaxMulticast = 16
    ReceiveMethod = ReceiveLookahead
    ReceiveBuffers = 64

[NFS-NDIS]
    drivername = NFSLINK1
    bindings = UBNEI

-----------------------
Any suggestions?  Thanks in advance.

--
======================================================================
Steven W. Eubanks,  EDS/LIMS			NASA Lewis Research Center
Internet:xxseub@osprey.lerc.nasa.gov		21000 Brookpark Rd. 
(216)433-8498					Cleveland, OH  44135