HDTenEightyP/NetNews huggingface dataset:
From: dhoward@novell.com (Dirk W. Howard)
Subject: Re: How is nearest server determined when two are on the same cable?
Organization: Novell, Inc.
Date: Wed, 26 Aug 1992 17:35:49 GMT

In article <1992Aug25.170307.161@indyvax.iupui.edu> imhw400@indyvax.iupui.edu writes:
>From: imhw400@indyvax.iupui.edu
>Subject: How is nearest server determined when two are on the same cable?
>Date: 25 Aug 92 17:03:07 -0500
>What is the algorithm that NetWare 386 uses to break ties when deciding who is
>the nearest server (in response to the GetNearestServer request)?  I'm trying
>to figure out why the "wrong" server *always* wins in one particular setup we
>have.
>-- 
>Mark H. Wood, Lead Analyst/Programmer    +1 317 274 0749   [@disclaimer@]
>Internet:  IMHW400@INDYVAX.IUPUI.EDU     BITNET:  IMHW400@INDYVAX
>Celebrate freedom:  read a banned newsgroup.


The "nearest" server is determined by which server can respond first to the
GetNearestServer packet.  That is it.  There is no fancy algorithm to it at 
all!  There are no ties.  If there was a tie on a CSMA/CD system then you 
would have a colision.  Hence, no tie.  If you need to connect to a 
particular server then use the preferred server option of the shell.

---------------------------------------------------------------------------
Dirk W. Howard              These are my personal opinions.  No one else 
Novell Technical Support    in their right would claim them.
dhoward@novell.com
                     "I'm sorry Ralph... not even the Networking
                      Fairy can pull this one out of the fire."
---------------------------------------------------------------------------
From: bataller@dogie.macc.wisc.edu (Erik Bataller)
Newsgroups: comp.sys.novell
Subject: Brgen: SFT 215 "Error = 9"
Date: 26 Aug 92 23:55:09 GMT
Distribution: comp.os.novell
Organization: University of Wisconsin Academic Computing Center

Hello,
	I am trying to get a Bridge running using the Netware 2.15 SFT 
bridge generator to "route"/"bridge" PCnet to Ethernet_II.  When I go to
Link it conks out and gives me the error message:
	"An error occurred linking brgen:bridge error = 9"

Would anyone have any ideas?  I am also interested in finding the latest 
SFT 2.15 OBJs and LANs for PCNet II and Western Digitals.

Thanks.
Erik

Internet:  Bataller@macc.wisc.edu
Bitnet:  Bataller@wiscmacc.bitnet
Newsgroups: comp.sys.novell
From: cmenser@nyx.cs.du.edu (Charles Menser)
Subject: Re: IPX Burstmode
X-Disclaimer: Nyx is a public access Unix system run by the University
	of Denver for the Denver community.  The University has neither
	control over nor responsibility for the opinions of users.
Organization: Nyx, Public Access Unix at U. of Denver Math/CS dept.
Date: Tue, 1 Sep 92 01:17:34 GMT

In article <1992Aug31.155041.29694@novell.com> mcollins@db.novell.com (Marty Collins) writes:
>mesdagt@gov.on.ca (Terry Mesdag) writes:
>: Does anyone know which versions of Novell's operating systems that
>: supports IPX BURSTMODE. Is it 3.11 and up?
>
>Only Netware 3.11 servers and their respective DOS clients.
>
>: 
>: My understanding is that IPX BURST MODE is primarily intended to enhance
>: WAN traffic performance between Novell LANs by allowing multiple IPX
>: request/responses in one burst of traffic, instead of having one
>: response/request in a 512 byte packet. Are there any other benefits to
>: IPX BURSTMODE ?
>
>Burst mode is exactly as you have specified.  The ability to send multiple
>IPX packets without immediate acknowledgement. This only takes affect when
>there is a read/write request of more than 512 bytes.
>

Is burst mode used by default (when sending more than 512 bytes)?

>: 
>: Many thanks in advance to any replies.
>: 
>: -- 
>: 
>: ---------------------------------------------------------------------------
>: Terry Mesdag                                Mail:  mesdagt@govonca.gov.on.ca
>: Computer and Telecommunication Services     Voice: (416) 327-3139
>
>--
>		Why is it that we can put a man on the MOON,
>		but we can't put metal in a MICROWAVE.
>
>            |--------------------------------------------------|
>            |  Marty Collins              Product Support      |
>            |  Novell, INC.	          San Jose, CA.        |
>            |  1-800-NETWARE              mcollins @novell.com |
>	    |--------------------------------------------------|


--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Charles D. Menser               !  "... and even if you choose not to decide,
cmenser@vyonous.kennesaw.edu    !           you still have made a choice."
From: donp@novell.com (don provan)
Newsgroups: comp.sys.novell
Subject: Re: SNMP & SNMPLOG
Date: 1 Sep 92 23:51:57 GMT
Organization: Novell, Inc., San Jose, California

In article <4478.79.uupcb@cccbbs.UUCP> david.santos@cccbbs.UUCP (David Santos) writes:
>Could someone please explain what the SNMP.NLM & SNMPLOG.NLM files in
>the system directory of a NW311 server are for?  No where in the
>"red books" are they explained?

You must have missed chapter six of "NetWare v3.11 TCP/IP Transport
Supervisor's Guide", where they are explained.  SNMP.Nlm is an SNMP
agent.  SNMPLog.Nlm logs SNMP traps.  In v3.11, neither are very
interesting unless you're using TCP/IP or, perhaps, AppleTalk.

						don provan
						donp@novell.com
Newsgroups: comp.sys.novell
From: scholl@gaul.csd.uwo.ca (Cam Scholl)
Subject: Need method to determine current user's Full Name and ID\
Organization: Computer Science Dept., Univ. of Western Ontario, London, Canada
Date: Sat, 29 Aug 1992 05:04:13 GMT

I need a simple routine to determine the current user's ID, and Full Name.

I would also like one to determine the current server.

If possible, I'd like them to run both on Novell SFT Advanced 2.11, and 3.11.
They can be in any language, I really don't care, but I'll be porting the
routines to Turbo Pascal 6.

Thanks,
Cam Scholl.
Internet: scholl@gaul.csd.uwo.ca
From: steved@vaxc.cc.monash.edu.au
Newsgroups: comp.sys.novell
Subject: Re: Problem installing 2.2
Date: 27 Aug 92 09:46:46 +1000
Organization: Computer Centre, Monash University, Australia

In article <1992Aug26.204200.6423@cs.uwp.edu>, datta@cs.uwp.edu (David Datta) writes:
> Some history: We have a Gateway 386 that was used as a server running
> 2.2. It had 2-200MB [Maxtor LXT213A] hard drives being mirrored and
> they both failed at the same time. (1 controller and 1 motor.) We got a
> new drive [Maxtor 7213AT]. We are now trying to re-install netware. The
> machine boots and works fine with the new drive. When trying to install
> 2.2, we get the following error.
>
> ABEND: Improper ROM Parameter table for DISK Controller.
                  ^^^^^^^^^^^^^^^^^^^
The disk you are using is not in the ROM table. I'd bet you have selected
the user defined drive in the CMOS config. I had this problem too.
>
> I have checked and the parameters and they are correctly set to:
>
> C:683 H:16 S:38 WP:1698 LZ:1698
>
> Any suggestions?

My "work-a-round" for this was to put my disks parameters in the ROM.
This required a new BIOS ROM to be burned, with appropriate checksum.

There must be a better way.

The other "work-a-round" is to choose a drive config in the table that
gets the most from your drive.

SteveD.
Newsgroups: comp.sys.novell
From: wnkretz@ikesg1.energietechnik.uni-stuttgart.de (Oliver Kretzschmar)
Subject: Problem to change second server disk in NetWare V2.15
Organization: IKE
Date: Fri, 4 Sep 1992 04:55:15 GMT



    Hey,

    we want to change the second disk of our NOVELL Server (we use
    NOVELL V2.15 with ESDI-controller) and want to build in a bigger
    one to increase size, but I don't know, what I must consider.
    Can I only change the disk or what is important to know ?
    Could somebody tell me, what steps I must do for this change ?
    Please mail me your informations !


    Thanks for your efforts

      Oliver

-- 
 Name : Oliver Kretzschmar   Inst.IKE / Uni.Stuttgart    /   @@ \   /   @@ \
 email: wnkretz@ikesg1.energietechnik.uni-stuttgart.de   \______// \\______/
 Phone: +49 711 685 2130        Pfaffenwaldring 31              |   |
 Fax  : +49 711 685 2010        7000 Stuttgart 80               \___/
Newsgroups: comp.sys.novell
From: dbuckley@cix.compulink.co.uk (David Buckley)
Subject: Re: How is nearest server determined whe
Cc: dbuckley@cix.compulink.co.uk
Reply-To: dbuckley@cix.compulink.co.uk
Date: Thu, 27 Aug 1992 19:50:00 +0000

>The "nearest" server is determined by which server can respond first to the
>GetNearestServer packet.  That is it.  There is no fancy algorithm to it at
>all!  There are no ties.  If there was a tie on a CSMA/CD system then you
>would have a colision.  Hence, no tie.  If you need to connect to a
>particular server then use the preferred server option of the shell.

That is true as far as it goes, but does not explain when you have 50
identically configured servers scattered over a LAN the same one *always*
responds first to the call, irrespective of server loading, or other obvious
variables...
From: stef@mais.hydro.qc.ca (Stephane Lecuyer)
Newsgroups: comp.sys.novell
Subject: Problems to shut DOWN novell 2.2 ?
Summary: Problems to shut DOWN the fileserver 2.2 ?
Keywords: novell,netware,fileserver
Date: 4 Sep 92 02:22:48 GMT
Organization: Hydro-Quebec, Montreal, Canada

If I try to DOWN the server and there's no connection ACTIVE, it can take up
to 5 minutes before it actually goes DOWN.  The problems seems intermittent, sometimes it will down fast (30 sec.) .
From: billb@ppc-a.isc-br.com (BILL BALLINGER)
Newsgroups: comp.sys.novell
Subject: Re: NWLite Lockup
Date: 2 Sep 92 21:13:48 GMT
Organization: ISC-Bunker Ramo Corporation, Spokane, WA.

In article <wbaker.5@sd-wbaker.jsc.nasa.gov> wbaker@sd-wbaker.jsc.nasa.gov (Bill Baker) writes:
>From: wbaker@sd-wbaker.jsc.nasa.gov (Bill Baker)
>Subject: NWLite Lockup
>Date: 1 Sep 92 18:19:24 GMT
>I've installed 14 stations using NWLite  1.0  and in the past few weeks I've 
>been experiencing constant lockup problems. This is the server configuration.
>	386DX40, 8MB RAM, 80MB IDE MAXTOR HD, 1.2, 1.44,
>	90MB BERNOULLI, HP LASERII, HP PLOTTER,
>I've got the laser on LPT1, the bernoulli on LPT2, and the plotter is set on 
>LPT3, actually is hardwire to com2 but rerouted the com port to LPT3.
>The lockup normally seem to happen when a print job is in queue, or when 
>first booting up, I have already try to change the printer buffer size, 
>client task, receive buffers, # of read buffers, read buffer size.
>What can I do next.

I'm not sure of your situation but it took me only one day to pull the 
plug on my NW Lite 1.0 installation.  I could make the server lockup
during multiple xcopy's.

I have sinced participated in the 1.1 beta test and have not experienced
any problems.  Novell tells me that 1.1 updates are being mailed Sept.
8th to all registered 1.0 buyers.  I hope this fixes your problem(s).

BTW - I called to verify my registration to confirm that I would 
automatically receive my official upgrade but they had no record!
Sean at Novell is fixing this for me and can confirm for you.
His number is 800-453-1267 ext. 5813.


Bill Ballinger                  Internet:  billb@mail.isc-br.com
ISC - Bunker Ramo               UUCP:      oliveb!isc-br!billb
22425 East Appleway             Phone:     509 927 5624
Liberty Lake WA 99019-9534 USA  Fax:       509 927 5195
From: debbied@NREL.ColoState.EDU (Debbie Devore)
Newsgroups: comp.sys.novell
Subject: Printing Banner Page in Windows 3.1
Date: 26 Aug 92 15:12:56 GMT
Distribution: usa
Organization: College of Natural Resources, Colo. State Univ.

I am tyring to eliminate the banner page and form feed options when printing
to a Paintjet XL300.  I am strictly using the Windows printer drivers, 
therefore, when connecting my port to the paintjet queue in Print Manager, the
form feed and banner page are always selected.  I always have to deselect those options before printing.

I have been trying to figure out how to make the default so that those options
are always de-selected.  I can log in and out and go in and out of windows
and the options will stay de-selected.  It is when I re-boot my machine that
the options go back to form feed and banner page selected.

I have made sure that the default in printcon is set up not to print the banner
page or form feed.  The windows option seems to override that.

If anyone has suggestions, or if you have experienced this problem, please
e-mail me.  I would appreciate any responses.

Debbie Devore
Colorado State University

E-mail:  debbied@zirkel.cfnr.colostate.edu 
Newsgroups: comp.sys.novell
From: dhoward@novell.com (Dirk W. Howard)
Subject: Re: NCP Packet size
Organization: Novell, Inc.
Distribution: na
Date: Mon, 31 Aug 1992 14:34:13 GMT

In article <1992Aug29.211512.19124@sj.nec.com> abbie@tdd.sj.nec.com (Abbie Matthews  x2959) writes:
>From: abbie@tdd.sj.nec.com (Abbie Matthews  x2959)
>Subject: NCP Packet size
>Date: 29 Aug 92 21:15:12 GMT
>Hi,
>
>When a Novell client conects to a Novell file server over ethernet
>the packet size that is negotiated is 1500 bytes. However when
>the client connects thru a non-Novell router the packet size
>that is negotiated is around 512 bytes.  The router is being
>written by me.
>
>Does any one know
>	1) why this happens (ie. am I doing something wrong)
>	2) is there any way for the router to influence
>	   what the packet size is (ie. increase the packet
>	   size back to the 1500 size)?
>
>-- Abbie.


1) This is a function of the routing alorithm of NetWare.  When ever NetWare 
IPX encounters a router the hop count is incremented.  If this happens while 
the client and server are negotiating the packet size it will automaticly 
default to 512 bytes.  NetWare takes the approach of supporting the lowest 
common demoninator in packet size in the routing.

2) No, there is nothing that the router can do specificly.  However, there 
is the LIPX.NLM that is available in the Multi Protocol Router (MPR).  MPR 
has a list price of $995.00 and gives you a site license for the LIPX.NLM.

This is from the AppNotes paper on LIPX.NLM

LIPX.NLM (previously known as BIGPACK.NLM) provides a way to help alleviate 
this packet size limitation. LIPX is a NetWare v3.11 NLM that, once loaded, 
causes the server to ignore the router check during packet size negotiation. 
This allows data packets larger than 512 bytes to be exchanged, as long as 
the intermediate routers are configured to allow data packets larger than 
512 bytes.

---------------------------------------------------------------------------
Dirk W. Howard              These are my personal opinions.  No one else 
Novell Technical Support    in their right would claim them.
dhoward@novell.com
                     "I'm sorry Ralph... not even the Networking
                      Fairy can pull this one out of the fire."
---------------------------------------------------------------------------
Newsgroups: comp.sys.novell
From: kca@engin.umich.edu (Jonathan Van Oast)
Subject: more (questions) on get_user_FULL_name ??
Date: Mon, 31 Aug 92 12:46:16 EDT
Organization: University of Michigan Engineering, Ann Arbor

in a previous post, some asked about netware calls to determine a users
full name as well as login name.  to help out, i sent info on the user_name,
and then looked into full_name.  i am not a netware expert, but (using
lan times' "programmers guide to netware" -- a useful tool) have managed
to write code doing everthing from the aforementioned getting a users
login name to mapping drives.  anwyay.. in this book i found only ONE
reference (i could have missed some...) to a users full name.  this was
in the get_station_logged_information (E3h 05h).  this also seems to be
the only place to extract home_directory (if you need this).  the big deal
is, i THINK (maybe i just coded wrong), it does not work.  NOTE that the
book notes: "this call is supported in ... NetWare386 [what i use].  It has
been replaced by higher-level calls such as Get Connection Information but
is shown here for completeness."

i am wondering if maybe it really ISNT supported in netware 386, (either that
or i coded wrong -- has anyone else made this work?), AND what is the
"higher-level call" which replaced the part about full_name (which is not
in Get Connection Information)?

any help along these lines would greatly be appreciated.  i am guessing it
IS possible to get the full_name since there is a variable to access it for
login scripts (and it would be silly(?) not to be able to access it).

thanks,   -jon   pc&ns  kca@caen.engin.umich.edu
From: clem@log.moron.vware.mn.org (Clem)
Newsgroups: comp.sys.novell
Subject: NE2100 Bus Mastering Card
Date: Wed, 26 Aug 92 11:05:57 CDT
Organization: Clem's Cafe, Minneapolis, MN

I have an NE2100 Bus Mastering Card that I am going to install into a Compaq
Eisa Server.  The Compaq will also have a NE3200 Eisa Bus Mastering Card in 
it.  In the documentation for the 2100 it says not to install that card in a
machine with any other Bus Mastering Cards in it.  I understand this to be
the case for ISA machines, but does it apply to EISA machines?  Will the 
configuration I have proposed not work?

thanks,
clement
From: keith@novell.COM (Keith Brown)
Newsgroups: comp.sys.novell
Subject: Re: Modem on Novell server.
Date: 4 Sep 92 00:15:54 GMT
Organization: Novell San Jose Development Center

In article <920803.150122.kjetilo@test2> kjetilo@bilbo.uio.no (Kjetil Otter Olsen) writes:
>
>Is it possible for the clients to share a modem on a Novell server ?
>

Now it is yes. The Novell crew down the road just turned the NetWare
Asynchronous Communications Server (NACS) into NLMs. The NACS was, and
probably still is available as, software for a dedicated 286 PC that
you load up with intelligent async cards and modems. Now you can
load up your NetWare 3.11 server with intelligent async cards and modems
instead. I read that they even support the standard PC serial ports
that may be adorning your server, but at limited speeds (PC serial
ports have a little "one character in, one yank on the interrupt line"
problem, plus a "you had better take this damn character away from
me fast because another one is coming and if you don't haul ass I won't
be keeping it here for you" problem).

>Answers in E-mail please.

Oops!

Keith
-
Keith Brown                                           Phone: 408-473-8308
Novell San Jose Development Center                      Fax: 408-473-8990
2180 Fortune Drive, San Jose, CA 95131                  Net: keith@novell.COM
From: heinrich@yvax.byu.edu (Ed Heinrich  - The LOKI Group, Inc.)
Newsgroups: comp.sys.novell
Subject: Re: How is nearest server determined whe
Date: 30 Aug 92 12:53:33 -0700
Organization: Brigham Young University

In article <memo.597357@cix.compulink.co.uk>, dbuckley@cix.compulink.co.uk (David Buckley) writes:
>>The "nearest" server is determined by which server can respond first to the
>>GetNearestServer packet.  That is it.  There is no fancy algorithm to it at
>>all!  There are no ties.  If there was a tie on a CSMA/CD system then you
>>would have a colision.  Hence, no tie.  If you need to connect to a
>>particular server then use the preferred server option of the shell.
> 
> That is true as far as it goes, but does not explain when you have 50
> identically configured servers scattered over a LAN the same one *always*
> responds first to the call, irrespective of server loading, or other obvious
> variables...

As a former Novell engineer, (one who wrote code for Novell products as
opposed to a CNE), I can tell you that Get Nearest Server does NOT have
any algorithms in it to maintain a "closest" node address.  It simply
broadcasts a message and the first node to respond is deemed to be the
"nearest".  Why does the same one always respond?  I don't know.  When I
was at Novell, which has a VERY large internal network,  I often saw the 
same node respond to this call.  Network toplogy, location of other ethernet 
devices, i.e., bridges/routers, etc., type of ethernet card used in a 
particular server, etc. can all add variables to the pie.  Being a software 
engineer, not a hardware  type, I really don't know all the factors that 
cause this.  

*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*
Ed Heinrich
The LOKI Group, Inc.
HEINRICH@yvax.byu.EDU
*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*

Newsgroups: comp.sys.novell
From: beecher@watsun.cc.columbia.edu (Ben Beecher)
Subject: vrepair finds hundreds of directory errors
Keywords: vrepair nw4mac nfs
Reply-To: beecher@watsun.cc.columbia.edu (Ben Beecher)
Organization: Columbia University
Date: Thu, 3 Sep 1992 02:12:08 GMT

I'm running NetWare 3.11 with NW4MAC 3.01 and NetWare NFS 1.1 and
every time I run vrepair I get lots of directory errors.  Last night I
ran vrepair for the first time in 2 months and fixed hundreds of
directory errors on each of four volumes.  I ran vrepair a second time
and fixed several hundred more directory errors.  A few months ago
when I started getting these errors I moved the MAC volume to a new
disk with a separate controller, but I still get hundreds of directory
errors every time I run vrepair.

On the MAC volume, which has MAC and NFS name spaces, vrepair fixed
540 directory entries the first time I ran it.  The second time it
repaired 1064 directory entries, and the third time it repaired 1584
FAT entries.  The fourth time it found no errors.

On the APPLIC volume, which has the NFS name space, vrepair fixed 86
directories the first time and 86 directories the second time.  It
came up clean the third time.

On the USERS volume, which has the NFS name space, vrepair fixed 445
directories the first time and 445 directories the second time.  It
came up clean the third time.

When I tried to repair the SYS volume, which has MAC and NFS name
spaces, vrepair was unable to load V_MAC.NFS.  I tried to load V_MAC
from the C: drive but it refused to start.  The first error message
scrolled off the screen before I could read it, and it was followed by
many messages of the form: "Loader cannot find public symbol:
<symbolname>", and then "Load file referenced undefined public
variable".  Then I told vrepair to remove the MAC name space and it
came back with 10329 directory errors.  The second time I ran vrepair
on the SYS volume it fixed 2632 directory entries, and the third time
it found no errors.

I downed the file server and brought it up normally, and as usual NFS
complained that:

	Problems have been detected for the following volumes:
	You are encouraged to dismount the volume, run vrepair
	to repair it

	1. /mac

I get this message every time I start the file server, but this time I
also got two messages I hadn't seen before:

	Can't modify directory entry for
	Can't modify directory entry for

Does anyone know what's going on here?  Is this a problem with NFS?
With NW4MAC?  With NetWare?  I'm sure it's not a hardware problem
because I moved the MAC volume to a new disk with a new controller and
I'm still getting these messages.

Ben Beecher		beecher@columbia.edu
Columbia University	Network Planning Group
From: troch@gandalf.Rutgers.EDU (Rod Troch)
Newsgroups: comp.sys.novell
Subject: Disk Usage Statistics
Date: 31 Aug 92 20:17:52 GMT
Organization: Right Coast HQ For Stupid Pub Tricks


Howdy.

Does anyone know of some software that will display how
much disk usage a user or multiple users are using?

If you would be so kind as to email me the site and name of
that utility I would be grateful.

thanks.
Rod
--
-----------
If you yell try : Rod Troch                  | Zeta Beta Tau
internet        : troch@gandalf.rutgers.edu  | 
                : troch@pilot.njin.net       | happyHappy joyJoy
Rutgers Univesity - Department of History - Network Administrator