
NetWare 4 FAQ (Frequently Asked Questions)
==========================================


Version : 20 December 1996


This FAQ, or list of Frequently Asked Questions, has been compiled from
questions seen by Sysops (System Operators) and Assistant Sysops of the
Compuserve NetWire NETW4X forum and from questions in the following Usenet
newsgroups :

bit.listserv.novell
comp.os.netware.misc
comp.os.netware.connectivity
comp.os.netware.security
comp.os.netware.announce
de.comp.sys.novell
fido.novell

The intention of this FAQ is to help anyone who is seeking answers to some
of the most commonly asked questions on NetWare 4 asked by beginners and
experienced users alike. If you have further questions and answers you
would like added to this list please contact the FAQ creator at the
e-mail address shown at the end of this document. The FAQ is divided
into three main sections :

1 - NetWare 4 - Technical
Dealing with technical questions and answers relating to installation and
ongoing use of NetWare 4.

2 - NetWare for Macintosh - Technical
Dealing with technical questions and answers relating to installation and
ongoing use of NetWare for Macintosh.

3 - Administrational
Relating to non-technical issues

All references to Novell forum libraries on Compuserve may also be
interpreted as referring to the equivalent directories on the Novell FTP
servers at ftp://ftp.novell.com and ftp://ftp.novell.de as well as the
libraries which can be found on the support section of the Novell Web
server at http://support.novell.com/


Sections
========

1.0 NetWare 4 - Technical
  1.1 Patches and Updates
  1.2 Installation and Upgrade
  1.3 LOGIN
  1.4 CDROM Support
  1.5 Client Components
  1.6 NDS
  1.7 Time Synchronisation
  1.8 Disk Compression

2.0 NetWare for Macintosh - Technical

3.0 Administrational


1.0 NetWare 4 - Technical
=========================

1.1 Patches and Updates
-----------------------

* Q. Where are the update files for NetWare 4.x?
  A. Library 02 of the NWOSFILES forum or at http://support.novell.com/
     (mw)


* Q. Where can I find the latest operating system patches for NetWare 4.1?
  A. 410PT?.EXE in the NWOSFILES forum, library 02 or at
     http://support.novell.com/
     (mw)


* Q. Where can I find the latest operating system patches for NetWare 4.11
     and IntranetWare?
  A. 411SP??.EXE in the NWOSFILES forum, library 02 or at
     http://support.novell.com/
     (mw)


* Q. What patches should I apply to my new NetWare 4.1 server?
  A. See the file PATLST.TXT. This is regularly updated and available
     on both Compuserve NWOSFILES forum and http://support.novell.com/
     (mw)


* Q. I am seeing 100% utilisation on my NetWare 4 server
  A. Make sure you have :
     a) Latest LAN driver versions
     b) Latest ETHERTSM.NLM or TOKENTSM.NLM versions from LANDR?.EXE in
        the NWOSFILES forum library.
     c) Latest disk driver versions
     d) The patches for 100% utilisation from the file 410PT?.EXE in the
        NWOSFILES forum library.

     Also, ensure that MAXIMUM SERVICE PROCESSES and MAXIMUM PACKET
     RECEIVE BUFFERS values are not being reached.
     (mw)


* Q. I am seeing 100% utilisation on my NetWare 4 server using
     Compaq hardware.
  A. Download the latest NetWare Programs from Compaq (NPFC) Service Pak
     from the Compaq CPQFORUM forum or http://www.compaq.com/
     (mw)


* Q. When loading AIOCOMX.NLM I see a message indicating that public
     symbol "AIORegisterDriverA" cannot be found.
  A. Recopy AIO.NLM and AIOCOMX.NLM from the NetWare 4 CDROM. This message
     indicates that you have overwritten the files which shipped with
     NetWare 4.
     (mw)


* Q. I am seeing volume dismounts and/or mirroring errors when using
     Adaptec controllers.
  A. Please download the file NW4X.EXE from the ADAPTEC forum on
     Compuserve or from http://www.adaptec.com/ and use the latest
     driver versions.
     (mw)


* Q. I am seeing Page Fault errors on my NetWare 4.1/4.11 server
  A. Make sure you put the following in the server AUTOEXEC.NCF :

     SET Read Fault Notification = On
     SET Read Fault Emulation = On
     SET Write Fault Notification = On
     SET Write Fault Emulation = On

     and that you have :

     a) Latest LAN driver versions
     b) Latest disk driver versions

     If you continue to see page fault errors (without Abend) please
     contact the manufacturer of your NIC and disk controller to obtain
     the latest available driver versions.

     For a detailed explanation of what the SET parameters mean, please
     see the Novell Application Note :

     "Abend Recovery Techniques for NetWare 3 and 4 Servers", June 1995
     (mw)


* Q. Where can I find NLICLEAR.NLM for NetWare 4?
  A. NLICLEAR.NLM is not required for NetWare 4 - Unlicensed connections
     do not count against your license count.
     (mw)


* Q. I do not see all servers listed in RCONSOLE with NetWare 4.1
  A. Obtain the latest ETHERTSM.NLM module from the file LANDR?.EXE in
     the NWOSFILES forum on Compuserve or at http://support.novell.com/
     (mw)


* Q. Does NetWare correctly support the year 2000?
  A. IntranetWare / NetWare 4.11 are fully year 2000 compatible
     For NetWare 4.1 see 410PT?.EXE
     For NetWare 3.12 see 312PT?.EXE
     (mw)


* Q. What is the message "This module is using n outdated APIs"?
  A. The Outdated API message is merely informative and means that the
     NLM is using internal APIs introduced in previous versions of
     NetWare which Novell has since replaced or updated but continues to
     support for backwards compatibility.
     (sm)


1.2 Installation and Upgrade
----------------------------

* Q. How do I calculate how much memory my server should have?
  A. See SMEM.EXE in the NOVUSER forum library or at :
     http://ourworld.compuserve.com/homepages/marcus_williamson/
     (mw)


* Q. How do I calculate the correct command line for the
     REGISTER MEMORY command?
  A. See REGMEM.EXE in the NOVUSER forum library or at :
     http://ourworld.compuserve.com/homepages/marcus_williamson/
     (mw)


* Q. I'm seeing an error during the install process when copying the
     CDROM NLM. What can I do?
  A. Change the name of the CDROM device in the CONFIG.SYS and AUTOEXEC.BAT
     of the server. The device name "CDROM" should not be used.
     (mw)


* Q. How should my CONFIG.SYS be if I am booting directly to NetWare?
  A. NetWare performs its own memory management. EMM386, HIMEM and
     similar memory drivers should be removed from the CONFIG.SYS of
     the server prior to running NetWare.
     (sm)


* Q. How do I add or remove a server license?
  A. LOAD INSTALL and select License Options. Then see the list of
     function keys described at the bottom of the screen.

     For more information see the Novell Application Note
     "Licensing and Serialisation in NetWare 4.1", July 1996
     (mw)


* Q. How do I change a server name?
  A.

  1. Make sure that NDS is synchronised correctly (SET DSTRACE=ON)
  2. Change the file server name in AUTOEXEC.NCF of the server
  3. Down the server
  4. On another server, do a RESET ROUTER
  5. Wait 5 minutes then reboot the server which has been renamed
  6. Check DSTRACE again to make sure NDS is synchronised
  7. Go into NETADMIN/NWAdmin to rename volume objects associated with server.
     (sm)


* Q. How do I change/upgrade the SYS: volume on a NetWare 4.1 server?
  A. Download DSENH.EXE from the NWOSFILES library and use the DSMAINT.NLM
     which is documented within DSENH.EXE. The instructions are in
     README.TXT, section IV, Scenario 1.
     (sm)


* Q. How do I rename a tree in NetWare 4.1/4.11?
  A. LOAD DSMERGE and select the option to Rename a tree.
     (sm)


* Q. How do I remove NDS from a server where there are NDS errors which
     will not allow removal any other way?
  A. LOAD INSTALL -DSREMOVE then select the option to remove Directory
     Services
     (mw)


* Q. How do I enable NLSP?
  A. NLSP comes with Netware 4.1 and NetWare 4.11

      Load INetcfg
        Protocols
          IPX
            Advanced IPX - Enabled
              Routing Protocol - NLSP
      (sm)


* Q. How do I upgrade from NetWare 3.x to NetWare 4.1?
  A. Migration procedure from NetWare 3.x to NetWare 4.1 :

     The two main procedures are 'In Place Upgrade' and 'Across the
     Wire'.

     'In Place Upgrade' involves updating of the operating system on the
     same server. The INSTALL program is used for this process - this
     performs the upgrade and carries out the migration of Bindery
     information into NDS.

     'Across the Wire' involves taking data and bindery information
     from one server to another via a workstation on the LAN. The
     MIGRATE program is used for this process and is run after the new
     NetWare 4.1 server has been installed.

     Another method, 'Across the Wire same server', which is seldom
     used, involves using a workstation to hold data temporarily during
     the upgrade process.

     Advantages and disadvantages of each approach are :

     In Place
     --------

     Pro : Preserves passwords during the upgrade
           No physical data is transferred

     Con : Does not allow changing of volume block size
           Difficult to recover in the event of power failure
          (Requires restore from backup)

     Across The Wire
     ---------------

     Pro : Allows upgrade to new server hardware
           Allows changes in volume block size

     Con : Passwords not preserved during the upgrade


     Prior to using either of these methods, it is recommended that you
     consider upgrading client workstations to the VLM components or
     Client 32 at the earliest opportunity. This will allow elimination
     of any issues with the workstation environment and/or applications.
     If testing with VLMs or Client 32has already been carried out, then
     this test stage may not be required.

     Please see the NetWare 4.1 documentation or the file MIGRAT.EXE
     (Compuserve and FTP sites) for further information on this
     migration process.
     (mw)


* Q. What files do I need on my local drive to run NPRINTER before I log
     in?
  A. NPRINTER.EXE can be run from a local drive without logging into the
     network as long as the network drivers have been loaded (LSL, mlid,
     IPXODI, VLM) and the workstation is attached to the server.

     Typing NPRINTER /VER from the DOS prompt displays the files
     necessary to run NPRINTER from a local drive.

     \PUBLIC\NPRINTER.EXE Version:   4.10 (c) Copyright 1983 - 1994
     Novell, Inc.  All rights reserved

     Files required for this utility:
     NPRINTER.MSG (4.10)
     NPRINTER.HEP (4.10) - only required for context sensitive help
     SCHEMA.XLT   (4.11)
     NWDSBRWS.MSG (4.13)
     TEXTUTIL.MSG (4.05)
     TEXTUTIL.HEP (4.02)
     TEXTUTIL.IDX
     ???_RUN.OVL  (eg. IBM_RUN.OVL )

     Unicode files needed for country 1 and code page 437:
     UNI_437.001
     437_UNI.001
     UNI_MON.001
     UNI_COL.001

     The above files are located on the NetWare server and should be
     copied to a directory on the local drive:
     SYS:PUBLIC
     SYS:PUBLIC\NLS
     SYS:PUBLIC\NLS\ENGLISH or other language directory

     Associated error messages:
     NPRINTER-DOS-4.10-973 is displayed if the unicode files cannot be
     located.

     The following error is displayed if the workstation is not attached
     to the server with access to the print server.
     TEXTUTIL-NPRINTER-4.10-384:  You are not logged in to server
     servername>.  You must be logged in to use this utility.  The
     program cannot continue. Also NPRINTER-DOS-4.10-63:  Print server
     <printserver> is unknown at this time.

     Use:  NPRINTER <PRINTSERVER> <PRINTER#>
     (sm)


* Q. Why should I use 802.2 vs. 802.3?
  A. Novell's ETHERNET_802.3 complies with IEEE 802.3 in that it defines
     a 1514 max size packet where the first six bytes is the destination
     address, the next six bytes is the source address, and the next two
     bytes are a length field. What's missing is an 802.2 header which
     could tell you what protocol is being run. Implementors "cheat"
     today by counting on the fact that ETHERNET_802.3 follows with a
     "-1" checksum field (0xFFFF).  Since most popular protocols don't
     use a DSAP or SSAP field of 0xFF, you can hack in code to
     distinguish IPX running on ETHERNET_802.3 frame from something
     else.
     (sm)

* Q. Should I set my maximum physical receive packet size to 1514 if I am
     running Ethernet?
  A. The MAXIMUM PHYSICAL RECEIVE PACKET SIZE setting impacts both the
     size of the largest receive buffer that can be passed up to the
     protocol stacks -AND- the largest physically contiguous receive
     buffer that can be allocated by the driver.  It's this second point
     that impacts Bus Master DMA adapters and drivers the most.

     "Physically contiguous" means that if the physical address is
     0x2000, and the size of the receive buffer is 0x200, then that
     means that the adapter can read or write to 0x2000-0x21FF
     to get or set the packet information.  Bus Master DMA adapters rely
     on physical, not virtual, addresses.  That means that virtually (to
     the driver, OS, protocol stacks, apps, etc) the buffer can be
     contiguous, but actually broken up into several smaller fragments,
     physically. For a better explanation, pick up a good book on
     computer organization.

     If you set the MAXIMUM PHYSICAL RECEIVE PACKET SIZE to 1514, then
     that allows the driver to allocate at most a 1514 byte physically
     contiguous buffer to DMA into, then pass up.  But what if the
     driver needs more?  For example, many hardware architectures need
     buffers that are mod 4 in length.  That means that the adapter
     needs a size that's even divisible by 4.  Many hardware
     architectures DMA the 4 byte checksum (FCS), so while the driver
     would only indicate up at most 1514 bytes, the adapter needs to DMA
     1518 bytes!  Still other hardware implementations add extra bytes
     before or after the packet to provide receive packet status
     information (was the packet good, was it too big, did it have a
     good checksum, etc).

     What all of this boils down to is that while 1514 bytes IS the
     largest Ethernet-sized frame from destination address to end of
     data, inclusive, but NOT counting the 4 byte checksum...1514 may
     NOT provide a receive buffer large enough for the adapter hardware.

     Since most versions of NetWare server defaults to 4202, Bus Master
     Ethernet drivers usually don't have any problems getting receive
     buffers that are large enough.  As users lower the 4202 default to
     optimize memory, the problem may become evident.  So, my advice is
     to always check with the vendor and use no less than their
     recommended setting...OR...worse case, add 12 to 20 bytes to the
     max packet size just to be safe.
     (sm)


1.3 Login
---------

* Q. How do I login as the Administrator user for the first time after
     installation?
  A. Ensure that you are using VLMs with NDS.VLM loaded, or Client 32,
     then :

     LOGIN .admin.orgname
     (mw)


* Q. I get Unknown error 8848 when trying to login as an NDS object.
  A. Please ensure that you are using the VLMs and that the NDS.VLM is
     loading. You can check this using :

     VLM /D

     If it is not loading then check your NET.CFG to make sure that you do
     not have an EXCLUDE statement for this VLM.

     Once you have checked/rectified the problem then reboot the workstation
     and login as :

     LOGIN .admin.orgname
     (mw)


* Q. How do I stop the red banner from appearing at login?
  A. Use LOGIN /NB
     (mw)


* Q. When trying to change the user's password I see the error :
     "Login-4.12-710: The password could not be changed. Error ff6a."
  A. Two possible solutions :

     1. Make sure that timesync is operating correctly. Type TIME at the
        server console to check this.
     2. If you are using Intel LANDesk LOGIN.COM, please contact Intel
        for an update to this file.
     (sm)


* Q. I see users connecting to servers where they should not have a
     connection.
  A. Check the value of the user's "Default Server" property in NWADMIN
     or NETADMIN
     (mw)


* Q. The wrong user name is displayed by LOGIN or WHOAMI
  A. Make sure you have the NetWare 4 version of LOGIN.EXE, WHOAMI.EXE
     and all other relevant utilities in the SYS:LOGIN and SYS:PUBLIC
     directories of all servers - The NetWare 3 utilities do not support
     more than 250 user connections.
     (mw)


* Q. Group names which differ by only one character, for example
     GROUP1 and GROUP2, are not being handled correctly in the login
     script in IF MEMBER OF statements, in NetWare 4.1.
  A. Download LOG412.EXE from library 02 of the NWOSFILES forum library
     and update the LOGIN.EXE in SYS:LOGIN and SYS:PUBLIC of all servers.
     (mw)


* Q. I have updated LOGIN.EXE and group names are still not being processed
     correctly.
  A. Make sure you specify the full group name, as, for example :

     IF MEMBER OF ".groupname.ouname.orgname"
     (mw)


* Q. I am getting drive mappings created twice or to the root directory.
     Why?
  A. This is probably because the 'default' login script is running.
     To avoid this, put the line :

     NO_DEFAULT

     into the container login script.
     (mw)


* Q. Where do I find a list of login script identifiers for NetWare 4?
  A. See LOG401.DOC/LOG402.DOC/LOG410.DOC in the NOVUSER forum library
     (mw)


* Q. How do I set up NetWare 4 to allow login anywhere within the network
     for mobile/nomadic/peripatetic users?
  A. See the Novell Application Note :
     "Configuring NetWare 4 for the Mobile User", July 1994
     (mw)


1.4 CDROM Support
-----------------

* Q. Can I use an IDE CDROM with NetWare 4.1?
  A. Yes - Please see the file CDUP?.EXE in the NWOSFILES forum, library 02
     or at http://support.novell.com/
     (mw)


* Q. Where can I find the latest CDROM.NLM for NetWare 3.12 and NetWare 4?
  A. CDUP?.EXE in the NWOSFILES forum, library 02 or at
     http://support.novell.com/
     (mw)


* Q. Why do I get "Loader cannot find public symbol" when loading
     CDROM.NLM?
  A. LOAD NWPA.NLM before loading CDROM.NLM
     (mw)


* Q. My CD ROM Volumes don't appear in NWADMIN or NWUSER.  Why?
  A. CD ROM volumes are transient from the perspective of the NetWare
     operating system. Therefore, they do not get installed into NDS
     automatically.  You can access them with a map command from DOS.

     If you want the CD volumes in NDS, make sure the volumes are mounted.
     Then LOAD INSTALL and select :

     Directory Services
     Upgrade mounted volumes into the directory.
     (sm)


1.5 Client Components
---------------------

* Q. Where can I find assistance with Client-related issues?
  A. On Compuserve GO NOVCLIENT or see http://support.novell.com/
     (mw)


* Q. Where can I find the latest workstation components, such as the
     most recent VLMs?
  A. Compuserve NWOSFILES library or http://support.novell.com/
     (mw)


* Q. Where can I find a full list of NET.CFG parameters?
  A. NETCFG.TXT in VLM*.EXE in the NWOSFILES forum
     or the manual for the 'DOS/Windows Client Kit'
     (mw)


* Q. Where can I find Client 32 for Windows 95?
  A. GO NWOSFILES or see http://support.novell.com/
     (mw)


* Q. How can I use long filenames for Windows 95 or NT Workstation with
     NetWare 4.1?
  A. At the server console :

     VOLUMES
     Load OS2.NAM
     ADD NAME SPACE OS2 TO VOLUME volumename
     VOLUMES

     Make sure you are using the Client 32 software, which supports long
     filenames.
     (mw)


* Q. How can I use long filenames for Windows 95 or NT Workstation with
     NetWare 4.11?
  A. At the server console :

     VOLUMES
     Load LONG.NAM
     ADD NAME SPACE LONG TO VOLUME volumename
     VOLUMES

     Make sure you are using the Client 32 software, which supports long
     filenames.
     (mw)


* Q. Can I use NETX.EXE instead of VLM at the client?
  A. Yes, but you will only be able to login as a Bindery user and will
     not be able to administer the network using NETADMIN or NWADMIN.
     The Admin user and any user requiring NDS access must use the VLM
     components.
     Ensure the BINDERY CONTEXT is set correctly at the server console.

     When operating in Bindery mode the following information applies :

     The system login script is NET$LOG.DAT in SYS:PUBLIC

     The user login script (and rights to the SYS:MAIL\userid directory) are
     created automatically when the user logs in as a user in Bindery mode :

     LOGIN username / B

     If you wish to manipulate individual user login scripts, create
     directories underneath the SYS:MAIL directory. The directory name
     underneath the SYS:MAIL directory is the user ID. The user ID can be
     shown by the following line (placed in the system login script).

     WRITE "User ID : %USER_ID"

     Then create the login script as an ASCII file called LOGIN in this
     directory. Alternatively (after you've created the directory) use
     SYSCON to manage the user login script.

     SYSCON is a NetWare 3.x utility, the latest version of which can be
     download as the file SYS???.EXE in the NWOSFILES forum library.
     (mw)


1.6 NDS
-------

* Q. Where do I find a list of NDS error codes?
  A. DSTIPS.EXE in library 02 of the NWOSFILES forum or at
     http://support.novell.com/
     (mw)


* Q. How do I set up Bindery Emulation on the server?
  A. Use the SET BINDERY CONTEXT command on the console to set the
     context(s) where Bindery Emulation should occur.
     (mw)


* Q. What is error -631 when trying to SET BINDERY CONTEXT on server?
  A. Ensure that a partition replica containing the context to be bindery
     emulated exists on this server.
     (mw)


* Q. I have lost my Admin user password. What can I do?
  A. Call Novell Tech Support. See below (Administrational section) for
     details.
     (mw)


* Q. How do I set up a user so they can only change passwords
     without giving them full administrative authority?
  A. This feature is currently not available.
     In order for a user to change another user's password, that
     user must have write privileges to the managed user's Object
     ACL property. The problem with this is that if the user has
     write privileges to the managed user's Object ACL, the user
     can grant himself supervisory rights to the entire object and
     go on from there. If you would like to request this feature as
     an enhancement, please E-mail Novell. See below ("How do I
     request an enhancement?") for the address.
     (bi)


* Q. Is there a way to limit the amount of disk space a given user can
     access on a volume?
  A. In NWADMIN, click on the volume object, From the menu:  Object,
     Details, See User Space Limits  _or_ click on the directory under
     the volume. Object, Details, Facts, Restrict size
     (sm)


* Q. How do I manage file rights on a NetWare 3.x server running
     Netsync?
  A. Assigning File Rights With NetSync

     Administration of NetSync should be done using the NetWare 4.10
     utilities Filer or NWAdmin and not the Syscon utility.  Changes
     made in Syscon will not be updated in the binderies on other NetWare
     3.x servers.  To use NWAdmin to administer file rights for the NetWare
     3.x servers you must proceed as follows:

     * Create a server object for the 3.x server using NWAdmin.
       Do NOT delete the server bindery object that was created when
       NetSync was installed.
     * Create volume objects for each volume that resides on the 3.x server.
       You can now double-click on the volume object to display the file
       structure of the volume.
     * Highlight the directory to which you want to modify rights and enter
       the "Details" menu.  Rights can now be modified in the "Trustees
       of this Directory" menu.
     * Rights for NetSync cannot be modified from the user object.
     (bi)


* Q. I get a message on the server console that my NetWare 4.x server
     can't communicate with my NetWare 3.x server. Why?
  A. The NetWare 4.x server is trying to communicate with the NetWare
     3.x server using NetWare 4.x protocols. The NetWare 3.x server
     does not respond, so they cannot communicate. Ignore this error
     message.
     (sm)


* Q. How can I minimise network traffic across WAN links?
  A. In a NetWare 4 environment, WAN traffic can be seen from the
     following sources :

     a. Time synchronisation
     b. NDS
     c. SAP/RIP

     Traffic from each of these sources may be reduced in the
     following ways.

     a. Time Synchronisation

     Time synchronisation traffic may be kept at a minimum using the
     configuration as outlined above. In addition, the following two
     SET parameters may be adjusted to change the frequency (number)
     and polling interval (seconds) for time synchronisation
     polling :

     TIMESYNC Polling Count = number (default 3)
     (Decrease this figure)
     TIMESYNC Polling Interval = seconds (default 600)
     (Increase this figure)

     b. NDS

     NDS traffic may be reduced by using the DS Filter program,
     which allows setting of the periods during which
     synchronisation may take place. Using this program, NDS
     synchronisation will only occur at certain times of the day. DS
     Filter NLMs are available as part of the Novell Multi Protocol
     Router (MPR) 3.0 product, or on the Novell Consulting Toolkit.

     Additionally, it is possible to change the SET parameter :

     NDS inactivity synchronization interval = minutes (default 30)

     to increase the time between periods when a synchronisation
     attempt takes place, if no other activity has been seen during
     this time. This is of particular interest on ISDN (and other
     switched) connections where frequent activation of the line
     might be undesirable.

     c. SAP/RIP

     SAP (Service Advertising Protocol) and RIP (Routing Information
     Protocol) traffic may be reduced by the use of a filtering
     program included with NetWare 4.0x and 4.1. This program can be
     used on servers which are acting as routers within the network.

     If servers are not acting as routers, it is suggested that the
     filtering facilities as provided by the third-party router are
     used instead.

     For more information about Burst Mode, which can considerably
     improve file and print performance across the WAN, please see
     BURST2.TXT in the NOVUSER forum library.

     For more information on this topic see the Novell Application Note

     "Managing Novell Directory Services Traffic Across a WAN: Part 1",
     June 1996

     (mw)


* Q. Where can I find filter NLMs for NDS in the WAN?
  A. See DSFLT?.EXE in the Compuserve NWOSFILES forum library or at
     http://support.novell.com/
     (mw)


* Q. Where can I obtain the book "NDS Troubleshooting"?
  A. "NDS Troubleshooting"
     ISBN: 1-56205-443-0
     Peter Kuo & Jim Henderson
     Published by : New Riders Publishing
     Available in English and German
     (mw)


* Q. What is the equivalent in NetWare 4.x of SECURITY.EXE in
     NetWare 3.x?
  A. You need a third party utility, such as AuditWare/NDS
     from Preferred Systems or BindView/NDS from BindView Development
     Corp.
     (sm)


* Q. I need to have "admins" who can only change the user's password.
  A. Check out n4pa12.exe from forum novuser.  There are also a number
     of other 'password helpers' there too.
     (sm)


* Q. Are there any workstation based products that will back up NDS?
  A. Both EmSave v4.1 and Xpress Librarian v3.0e from NCE Storage
     Solutions are workstation backup solutions that will backup and
     restore the NDS.  However, you must have Bindery Emulation set on
     the server for this to work properly. GO EMERALD for more info on
     these products.
     (sm)


1.7 Time Synchronisation
------------------------

* Q. How do I change the time on a NetWare 4.1 server?
  A. LOAD SERVMAN
     Server parameters
     Time
     Timesync time adjustment - Change it here
     (sm)


* Q. What is the message "Synthetic time is being issued on partition..."?
  A. In NetWare 4.1 synthetic time will be issued at a server with the error
     "DS- 4.63-12" if the server time is set backwards. The synthetic time
     will be cycled every 2 minutes until the server time is after the last
     modified timestamp.

     To fix it run DSREPAIR, select Advanced Options, Replica and
     Partition Operations, Select the partition you want to update and then
     select Repair Time stamps and declare a new epoch.
     (mw)


* Q. Users are being logged out at wrong times and/or time restrictions
     are being shown wrongly and/or LASTLOGIN showing incorrect time.
  A. Ensure that workstation TZ variable is set :

     SET TZ = timezone
     (in AUTOEXEC.BAT)

     or

     DOS SET TZ="timezone"
     (in login script)
     (mw)


* Q. Where do I find a solution for external time synchronisation?
  A. See TIMESG.TXT in the NOVUSER forum library - TIMESG.TXT and
     TIMESG.HTM (an HTML version) also appear at :
     http://ourworld.compuserve.com/homepages/marcus_williamson/
     (mw)


* Q. Where do I find a solution for scheduling of server tasks?
  A. See TIMESG.TXT in the NOVUSER forum library - TIMESG.TXT and
     TIMESG.HTM (an HTML version) also appear at :
     http://ourworld.compuserve.com/homepages/marcus_williamson/
     (mw)


* Q. Where can I find out more about time and time synchronisation?
  A. See the Novell Application Notes :
     "Time Synchronization in NetWare 4.x", November 1993
     and
     "Time in the NetWare Environment", January 1994
     (mw)


1.8 Disk Compression
--------------------

* Q. I have compression turned on and some files are compressing,
     but some files have the CAN'T COMPRESS indicator on. The files
     are not flagged CI (compress inhibit).
  A. This indicates that not enough space would be saved by
     compressing the file. The SET parameter :

     Minimum Compression Percentage Gain =

     specifies how much space must be saved before a file is
     compressed.
     (sm)


* Q. I am getting the message :
     "Compressed files are not being committed decompressed on
     Volume SYS  due to lack of disk space"
     What does it mean?
  A. This means a file was accessed and would normally be stored
     back in uncompressed form, but because free space was less than
     the minimum percentage for the volume, it stored the file
     compressed.
     No files should have been lost or damaged. Default is 10
     percent of volume space and can be changed via a set command
     through SERVMAN.
     (sm)



2.0 NetWare for Macintosh - Technical
=====================================
(Courtesy of Suzanne Miles)


* Q. What do I need for my Macintosh computers to connect to a Netware
     3.11 server?
  A. You need Netware for Mac 3.11 (which isn't being sold any longer).
     Your alternative solution is to buy Netware for Mac 3.12 200 user
     version. Netware 3.12 comes with a 5 user version of Netware for
     Mac.  Netware 4.1 comes with an unlimited user version of Netware
     for Mac.  Check to see if it would be cheaper to upgrade the
     operating system or buy Netware for Mac 3.12 200 user version.
     Your Macintosh computers will need an Ethernet card or a Friendly
     Net connector to connect the machines to the Ethernet.

* Q. What hardware do I need in my server to attach a LocalTalk network
     to an Ethertalk network?
  A. COPS bought the Dayna DL2000 card line.  (Cooperative Printing
     Solutions). Card goes in your server, attaches via DIN-8 to the
     Localtalk loop.  Be aware though, that the DL2000 Card may also work
     for you but it has not been certified on NetWare 4.1, so you may run
     into problems with it.

     You could use an EtherPrint box from Dayna for the printers, that
     will convert your Localtalk devices over to Ethernet. Or some other
     type of LocalTalk to Ethertalk box.

     Cooperative Printing Solutions, Inc.

     5950 Live Oak Parkway
     Suite 175
     Norcross, GA 30093
     USA
     Tel : +1 770 840 0810
     Fax : +1 770 448 7821


* Q. Tell me about printing on NetWare 3.12 and the Mac.
  A. First issue is you have to use a LaserWriter 7 driver with NW-MAC
     3.x. LaserWriter 8 drivers use Postscript level 2 which is NOT
     supported in NW-MAC 3.x.

     That should allow you at least to print simple print jobs to the
     printer.

     You may also encounter a Binary vs. ASCII Postscript print problem.


     ASCII PostScript vs. Binary Postscript

     There are two methods of sending Postscript data to a PostScript
     printer: ASCII PostScript and binary PostScript. Jobs formatted in
     ASCII PostScript can be safely sent through all communication
     channels although you may need to set serial ports to 8 bits.
     While an AppleTalk-connected printer can understand either ASCII
     or binary Postscript, serial, parallel and IPX communication
     channels do not support binary PostScript; they are not
     "binary-capable" communication channels. Users printing documents
     from a Macintosh client to a non-AppleTalk connected printer can
     experience erratic problems due to this incompatibility.


* Q. Will I still be able to print if I take Appletalk off my server if
     I am using the Netware Client for Mac OS?
  A. You only need the AppleTalk modules if you only have AppleTalk
     printers.  You can set up your printing with the IPX client through
     the supplied tools -- NetWare Directory Browser or NetWare Print
     Chooser. You can print to the same queues that the PC workstations
     print to.

* Q. How do I create a Queue for DOS users to print to a Mac printer?
  A. Option 1:  You can create a Queue for DOS users to print to a MAC
     printer by using the following in your ATPS.CFG file.

     -p "PrinterNameInChooser" -z "ZoneWherePrinterIsFoundInChooser"

     Then load ATPS. This will create a queue called
     NW_PrinterNameInChooser to which your DOS machines can print.
     ATPS will forward the job from the Queue to the printer.  Remember
     that you must print with a Postscript driver from DOS in order to
     print to the Printer.

     The line above will also create a spooler for the Mac's to print to
     called NW_PrinterNameInChooser.  If you do not want to see this or
     have it show up in spooler then use a -wf on the line above.  (-wf
     means without front-end)

     Option 2:  In PCONSOLE:

     Change Context to the appropriate context
     Select PRINT SERVERS
     Select existing Print Server or create new one
     Select PRINTERS
     <ins><ins> and enter new printer name
     Select that newly created printer name to add to list of printers
     serviced by Print Server Select the new printer to get to options
     Change Printer Type from Parallel to Appletalk
     Selection CONFIGURATION option
     Set Appletalk Name to exactly match the printer name as advertised
     on Appletalk (case, spaces, etc.) Select Appletalk Type as
     appropriate Enter correct Appletalk Zone of printer
     <esc> to previous Printer screen
     Select Print Queues Assigned
     <ins><ins> and enter new print queue name
     <ins> at Print Queue Volume to see list of existing queue volumes
     and select as appropriate <esc><esc>
     answer Yes to Save Changes? and <esc> several times out to system
     prompt.


* Q. I get an error message Appletalk Interface Failed
  A. FYI: "AppleTalk Interface Failed" Error An ATPS queue can only be
     advertised in an internal zone such as a zone that is defined on
     the LOAD APPLETLK statement in the AUTOEXEC.NCF. In the ATPS.CFG
     file, a queue was defined to advertise itself in a zone that was
     only listed on the BIND APPLETLK statement in the AUTOEXEC.NCF.

     The zone was not included in the LOAD APPLETLK statement. There are
     two options to correct this problem.

     1. Change the ATPS.CFG file to advertise the queue in one of the
     internal zones.

     Example: One of the zones already defined in the LOAD APPLETLK
     statement.

     2. Change the LOAD APPLETLK statement in AUTOEXEC.NCF to
     include the zone in which you want to advertise the queue.

     Example: If you want the queue to be advertised in the Marketing
     zone:
     old LOAD APPLETLK net=55000 zone={"Admin"}
     new LOAD APPLETLK net=55000 zone={"Admin","Marketing"}
     Please note that the feature of using multiple zones for the
     internal network is only available in NetWare for Macintosh v3.01
     or later, and is not available in NetWare for Macintosh v3.0.


* Q. How do I configure ATPS?
  A. Configuring ATPS

     Macintosh Printing Using ATPS.NLM

     Note: the # symbol is used to remark out a line in the atps.cfg
     file. #For printers connected over Appletalk (LocalTalk, EtherTalk,
     tokentalk) -p "LaserWriter II NTX" -z "MacZone" -o "LaserQueue"

     #For printers connected over parallel, serial, rprinter, or
     nprinter -o DOSQUEUE -wb -L -f hplaser

     Troubleshooting Macintosh Printing Using ATPS

     At the server console prompt, type:
     LOAD ATPS -V
     Then switch screens to the screen with ATPS at the top left.When
     working correctly, you will see:

     Using directory SYS:SYSTEM\ATPS
     initializing existing queue LaserQueue
     getting an initial spooler font list from printer
     <LaserWriter IINTX>
     attaching printer <LaserWriter II NTX> to queue
     LaserQueue NBP registering spooler <LaserQueue:LaserWriter@*>

     You may see error messages, such as;
     ATPS: can't find printer <LaserJet 4MV:LaserWriter@zonename>,
     retrying.

     This suggests a communication problem.  Use ATCON.NLM (see
     Troubleshooting Using ATCON section of the Installing NetWare for
     Macintosh guide.)

     Options for Loading ATPS

     Load ATPS -D VOL1:QUEUES
     Allows you to specify a volume other than the default sys:system
     for the queues to be located in.

     LOAD ATPS -V
     brings up the verbose screen. Useful for troubleshooting, but it
     creates very large system error logs, unload and load without this
     when finished troubleshooting.

     ATPS.CFG Options

     -y
     Notification, this turns OFF notification of print jobs that
     printed successfully.

     -p
     printer name.  This name can be up to 31 characters in length.  If
     you do not specify a queue name, ATPS.NLM will create a default
     queue name with NW Printername.

     -z zone name.  This is the AppleTalk zone in
     which the printer resides.  If you do not specify this, ATPS
     assumes the default zone, or the zone used in the Load Appletalk
     line of autoexec.ncf

     -e Turns off error banner pages generated by Postscript errors.

     -wb without back end, meaning atps.nlm will give the job to another
     print server, such as pserver.nlm.

     -L Laserwriter prep, this means that each time a Macintosh prints
     to the queue the Laserwriter prep will be downloaded to the printer
     to set it up for Macintosh postscript

     -f font file, and the font file name here is Hplaser.  There are
     several font files, but they are almost all exactly the same. -h
     Hides AppleTalk printer by changing its NBP type to Lasershared.

     -wb Turns off the back end of the atps.nlm, so that this queue will
     be services by another print server.

     -n# -n20 where 20 is the number of concurrent print jobs allowed in
     the queue.  This number must be between 1 and 50.

     -t Type of printer, the default is LaserWriter.  The default works
     for almost all postscript printers.  See document, Printer Types
     for a list of these.

     -s Use this if the type of printer is not the default type
     LaserWriter, but it is still Postscript printer.  This is used with
     non-Appletalk printers.

     -r Sends fonts in 512k blocks, which is faster than the default.


* Q. How do I set up ATPS In order to print to a non-AppleTalk printer
     from the Macs?
  A. In order to print to a non-AppleTalk printer from the Macs do the
     following:

     1. Setup the printing on the pc side and verify that you can print
     to the printer from a pc workstation.
     2. Enter the following line in
     atps.cfg using the above queue name

     -o "queue name" -wb -l -f hplaser

     The -l if to for a laser prep file needed for laser printers.
     The -f specifies the font file.
     hplaser is the most common but your other options are in the
     nw-mac\fonts directory. The spooler will show up in the Mac chooser
     with the same name as the queue.  If you want those names to be
     different then use

     -o "spooler name" -q "queue name" -wb -l -f hplaser


* Q. How do I configure MacIPX Gateway on a NetWare 4.1 file server so
     that a Macintosh using Apple Remote Access and running the NetWare
     Client for Mac OS v5.1 can login to the DS tree and mount a
     volume?
  A. The following steps will help you configure this scenario.

     1. LOADING THE IPX GATEWAY MODULE

     After installing the IPX gateway LAN driver, execute the following
     LOAD command at the server or router prompt to launch the IPX
     gateway software:

     LOAD MACIPXGW

     To specify a distinctive name for the IPX gateway when you load it,
     you can execute a command like this:

     LOAD MACIPXGW GATEWAY_NAME="AppleTalk-IPX Gateway"

     Macintosh users will see this name when they configure MacIPX at
     their workstations

     2. BINDING THE IPX GATEWAY TO THE IPX NETWORK

     After loading the gateway, you should bind the IPX gateway to the
     IPX network, using this command:

     BIND IPX TO MACIPXGW NET=<net_number>

     The <net_number> in this command must be a unique network number;
     think of this as the "MacIPX network number."

     This command effectively binds IPX to the gateway itself. The
     command can be executed at the server or router prompt or can be
     included in the server's or router's AUTOEXEC.NCF file, after the
     LOAD MACIPXGW command.

     3. From the remote Macintosh, establish your Apple Remote Access
     (ARA) session. This will establish an AppleTalk connection to your
     local network.  In order to use IPX on the Macintosh and mount
     devices through Directory Services (DS), you will need to establish
     an IPX connection as described below.

     4. From the remote Macintosh, open the MacIPX control panel and
     double click on the AppleTalk icon.

     5. You will then be warned that current services will be
     disconnected, and then you will be presented with a window that
     allows you to select a zone and an IPX Gateway device in a
     particular zone.

     6. If you only have one file server running the IPX Gateway NLM,
     the gateway will already be selected and show up as "greyed out".
     This is because the default setting is to "Always Auto-select an
     IPX Gateway". If you uncheck the check box next to this option, the
     gateway that was "grayed out" will then appear black and can be
     selected.  If you have more than one gateway device available
     select the desired one. Once you've selected the gateway device,
     close the MacIPX control panel.

     7. Locate and launch the NetWare Directory Browser on the
     Macintosh. You will be prompted to login to DS, if not already
     logged in.  The Browser will then display the DS objects available
     in the context being browsed.

     8. Locate the desired DS object in the Browser and double click to
     mount a volume, or choose a print queue, etc.


* Q. I installed System 7.5.3, and now I get the message that the MacTCP
     control panel was no longer found in the Control Panels folder..
  A. Run the installer and do a custom install of the MacTCP software.
     If the Mac was running Open Transport prior to updating, the MacTCP
     and NetWork control panels will be replaced with TCP/IP and
     AppleTalk respectively.


* Q.  I installed System 7.5.3, and now I get an error message about
     the Netware UAM only working with certain versions of Appleshare.
  A. The NetWare UAM files that ship with the 3.x and 4.1 clients for
     the Macintosh aren't compatible with the version of AppleShare that
     is installed by System 7.5.3 (AppleShare v3.6.1RevB).  The NetWare
     UAM v5.0 that ships with the NetWare Client for Mac OS 5.1 does
     work with this newer version of AppleShare.  But the NetWare Client
     control panel must also be installed on the Macintosh.

     When the System 7.5 Update 2 (v7.5.3) is installed on a Macintosh,
     the version of AppleShare that gets installed is v3.6.1.  This
     version of AppleShare causes problems for the earlier versions of
     the NetWare UAM (v3.0 and v4.0).  The NetWare UAM v5.0 that ships
     with the new NetWare Client for Mac OS v5.1 is compatible with the
     newer version of AppleShare v3.6.1.  With this newer UAM, the
     NetWare Client control panel must also be installed on the
     Macintosh to avoid errors described in the above.

     Depending on the version of NetWare being used on the file server,
     users should upgrade the client files as follows when upgrading to
     the Macintosh System 7.5.3:

     NetWare 4.1
     Download and use the NetWare Client for Mac OS v5.1 client kit
     (CL4MAC.EXE or CL4MAC.BIN) available on Novell's Macintosh Support
     web location at :

     http://netwire.novell.com/home/client/mac/patch51.htm)

     On Compuserve GO NWGENFILES - Library 7

     NetWare 3.x
     Download and use the NetWare for Macintosh Cleint kit (3XCLNT.EXE
     or 3XCLNT.BIN) available on Novell's Macintosh Support web location
     at :

     http://netwire.novell.com/home/client/mac/patch312.htm

     On Compuserve GO NWGENFILES - Library 7.


* Q. I am having a problem with Quark Express via Netware Client for
     Mac and getting the error Auto-saving a failed:file not found (-43)
     - Quark .  This problem does not occur if the user is logged in to
     the file server via AppleTalk.
  A. This problem has been submitted to engineering.  There are two
     possible workarounds.  First, login to the file server via
     AppleTalk, rather than the NetWare Client for Mac OS 5.1.  Second,
     if the user needs to use the NWClient for Mac OS 5.1, do not use
     the Auto Save feature in Quark Express.


* Q. I am having a Problem getting logged into the DS tree using the new
     NetWare Client for Mac OS v5.1.  After entering the user password
     in the login dialog box, the following error would be displayed on
     the Macintosh:

     "No NetWare Servers can be found on the network at this time.
     Please check your physical network connection or contact your
     network administrator."
  A. Change the SET parameter "set reply to get nearest server" to ON.


* Q. How do I configure Dynatext to be able to see the online  docs
     from the new client for MAC?
  A. Read the DynaText Book - Installing and Using Novell Online
     Documentation, in Chapter 4.  The directions are there for adding a
     new collection. Also read the dynatext.ini file in the dtapppwin
     directory.

     Also, the manuals are available via the Novell Web site
     at http://www.novell.com/

     You can find the Installing and Using Novell Online Documentation
     manual at http://occam.sjf.novell.com:8080/nw410.english


* Q. I installed MACFILE.NLM on my server and it instantly abended.
     What should I do?
  A. After installing the MACFILE.NLM from the NetWare Client for
     Mac OS 5.1 and rebooting the file server, the file server abends
     after MACFILE.NLM initiates the automatic desktop rebuild process.
     The following abend message is displayed on the console screen:

     Abend: Page Fault Processor Exception
     Running Process: MACFILE Rebuilder Process

     This abend is caused because the MACFILE Rebuilder Process
     encounters Macintosh application files on the file server that have
     damaged or invalid resource fork information.  The rebuilder
     process looks at each Macintosh application to retrieve information
     from the bundle resource, such as icons, TYPE and CREATOR flags,
     etc., to build up the desktop database on the file server.  There
     are some application files, that for some reason, the bundle
     resource information is invalid or damaged.  The cause of this
     damage is not known, and not all Macintosh applications have this
     problem.

     This problem has been fixed in a new release of MACFILE.  This file
     is located in the NWGENFILES forum library on Compuserve and is
     called MACFIL.EXE.


* Q. Where do I get the latest Mac client?
  A. Download NetWare Client for Mac OS 5.1

     Novell's NetWare Client for Mac OS is the first client for Mac OS
     (including Macintosh) that uses the IPX protocol to significantly
     ease the burden of administrators and greatly improve network
     access and security for users in a NetWare 4.1 environment.

     The latest MacIPX client can be found on the NWGENFILES forum or on
     http://support.novell.com/ in CLT511.EXE.

     Administrator Benefits
     -  Single protocol for all users-IPX
     -  Increases server performance by unloading the NetWare for
     Macintosh NLMs -  Easy, flexible installation with four different
     options
     -  Ability to send NDS object icons to users to make changing
    printers and servers as easy as double-clicking
     -  Automatically senses the correct frame type to use, whether
    it is Ethernet II, Ethernet 802.2, Ethernet 802.3, or Ethernet
    SNAP
     -  Supports Ethernet, Token-ring and LocalTalk cabling
     -  Remote console application
     -  Ability to see the mac user's ethernet address

     You can get more information about the new IPX client from the
     Novell Mac web page via : http://support.novell.com/


* Q. How come when I do a DIR on a PC some of my Mac files are
     only zero-bytes?
  A. Macintosh files are really made up of two "forks"....a data fork
     and a resource fork -they're sort of like separate files.  Data
     files (like your documents) are usually all data fork, with a
     zero-byte resource fork, though some may have a small resource fork
     as well. Program files, and some data files like fonts, are all
     resource fork, with a zero-byte data fork.

     Additionally, You can do a NDIR *.* /mac /long to see the actual
     file sizes.

     When you do a DIR on a PC, you only see the data fork.


* Q. How can I get a Macintosh to see the netware server and print to
     a local printer at the same time?
  A. You can only access either Localtalk or EtherTalk at any given
     time.

     The easiest way to do what you want is to get the LaserWriter
     bridge from Apple.   It will bridge over the LaserWriter so you do
     not have to switch back and forth to print.

     A patch for the LaserWriter bridge to work with Open Transport (and
     7.5.3) can be found in the GO APPLE forum, Mac Planet, Library 14
     LWBRDGE.SIT. The LaserWriter bridge software on the Internet at:

     http://infotech.kumc.edu/docs/macusers/lbridge.htm
     (LaserWriter Bridge Software)


* Q. How do I auto-mount volumes on the Mac in NW 4.1?
  A. You can do one of two things :

     To get an AppleTalk connection to the server:

     Login through chooser, selecting the NetWare Encrypted Method.
     Then make an alias of the server volume and place that alias in
     your startup items folder in your system folder.

     To get an IPX connection to the server:

     Install the NetWare Client for Mac OS on your workstations.

     Then go into the Directory Browser and Find the volumes you want to
     Mount on startup and drag the volume objects to your desktop.
     Place the volume objects you dragged out of the Directory Browser
     in your startup items folder.  It will prompt you for a password
     once and mount the volumes on your desktop.

     The objects that you drag out of the Directory Browser can be
     emailed to other users and they can place them in their startup
     items folder as well.  You do have to have the NetWare Client for
     Mac OS installed on the workstations though.


* Q. The Macintosh System does not show the correct available space and
     used space.
  A. System 7.5 can access volumes to 4GB,  System 7.1 can access
     volumes to 2GB. When you access volumes larger than these with
     NW-MAC 3.0x, the finder does a calculation on the space available
     and returns a negative number.  Thus there is no space available on
     the volume. This problem has been seen with volume sizes 1.2 and
     greater with System 7.1.

     NetWare workaround for Finder Limitation with NetWare for
     Macintosh:

     AFP 3.12 and 4.x lies back to the finder with volumes over 1GB.

     When the finder (7.1 or 7.5) queries the AFP about the volume size
     and space available on a volume with over 1GB of space available,
     AFP reports back 999MB available to the finder.  If there is less
     than 1GB of space available on the volume then it reports back the
     correct amount of space available.

     Note: The 999MB of space available is on a per login basis.  So
     when you mount the volume, you can save 999MB of information over
     to the server during that session.  If you try to copy more than
     999MB then you will run out of space.  In order to enable yourself
     to copy more information to the volume you must trash the volume
     and re-login to the server and mount the volume again.  At which
     time the 999MB counter will be reset and you can copy 999MB of
     information over to the server again during that login session.
     The reason for the 999MB per login basis, is due to the fact that
     the finder keeps the space available for the volume in the
     Macintosh memory and does not query AFP again while the volume is
     mounted. Finder just continues to decrement the space available in
     memory until it runs out, and remounting the volume refreshes the
     space available on the volume in the Macintosh memory.

     With system 7.5.2 (for PCI base PowerMacs) the Finder limitation is
     2TB. However, Appleshare is limited to accessing only 4GB volumes.
     So for accessing a server's volume the 4GB limitation move from the
     Finder to AppleShare.

     Known Issues with AFP 3.12a.  With volume sizes over 4GB, AFP will
     sometimes report back something less than 999MB to the finder.
     This was resolved with an update to AFP (3.12f available in
     AFP11.EXE)

     NetWare workaround for Finder Limitation with NetWare Client for
     Mac OS and NetWare 4.1.

     The NetWare Client for Mac OS uses IPX instead of AppleTalk to
     access the volume, providing you mount the volume with the
     Directory Browser and not through the Chooser and AppleShare.
     Therefore the NetWare Client does not use AFP to determine the
     volume size so the workaround had to be built into the client.  The
     client determines the Operating System running on the Macintosh and
     lies back to the finder that a maximum of 2GB is available per
     login session an a Macintosh running System 7.0, and a maximum of
     4GB of space available on a Macintosh running System 7.5.

     So with an IPX session and the NetWare Client for Mac OS, it
     reports back 2GB or 4GB instead of 999MB.

     With System 7.5.2 (PCI based PowerMacs) has a Finder limitation of
     2TB.  Seeing how the NetWare Client for Mac OS v5.1 does not use
     AppleShare (which has a 4GB lmitation) the finder should report
     back the volume sizes for volumes larger than 4GB correctly, and it
     does not. It reports back 4GB. This is a known issue and a Novell
     is working on a resolution.


* Q. I'm attempting to log in to my NetWare 4.1 network from an
     AppleTalk workstation I'm installing and I receive the message
     "unrecognizable login sequence".
  A. Make sure LOAD AFPCON, DETAILED CONFIGURATION, USER ACCESS...,
     Allow clear text password logins = YES is set and check to see if
     you do have the Bindery Context Set correctly.


* Q. How do I rebuild the desktop on a Netware server?
  A. Option 1:  RBUILD.EXE from GO NWGENFILES.  This is a Dayna desktop
     rebuilder application. (Only from a Netware 3.x server)

     Option 2:

     Unload AFP
     Load AFP CDT
     Unload AFP
     Load AFP

     Option 3:

     Unload AFP LOGIN to the server with a DOS machine as
     supervisor.  Map a drive to the root of the problem volume (SYS or
     Other) FLAG DESKTOP.AFP\*.* n
     Del DESKTOP.AFP\*.*
     FLAGDIR DESKTOP.AFP h
     RD DESKTOP.AFP
     Load AFP

     Option 4:

     (from a NW4.x server)
     Load AFPCON
     Maintenance and Status
     Desktop Rebuild


* Q. How can I get the Mac's to receive warning about password
     expirations?
  A. Install Netware Notify on the Mac's.  NetWare Notify is actually
     part of the NW-MAC client.  You should have a Mac Client diskette
     with your NW-Mac product.

     If you can't find it get NTFUAM.HQX from GO NOVLIB library 08.
     You will also need BinHex to extract it.  You can get that from
     BINHX5.EXE from GO NSD (download the file by name)

     Install the client on the workstations or at least install it on
     one workstation and get NetWare Notify from the Extensions folder
     and copy it to the other Mac's.


* Q. How do I unstuff an HQX file?
  A. You can use either BinHex or Stuffit.

     Files with the extension HQX are BinHex files, and require BinHex
     4.0 to destuff.  GO NSD and download BINHX5.EXE -- extract this
     file to any disk. It results in...

     BINHEX5  EXE        42,847 01-10-95  12:54p
     BINHX5   TXT         1,788 02-28-95  11:51a

     As the text file will tell you, copy BINHEX5.EXE to a NetWare
     volume with Mac name space installed, then run it.  This results
     in:

     BINHEX5  0               0 04-24-85  11:04p
     BINHEX5  EXE        42,847 01-10-95  12:54p
     BINHX5   TXT         1,788 02-28-95  11:51a

     The new BINHEX5.0 file with 0 bytes is a Mac application -- don't
     delete it! Instead go to a Mac, double-click on it, then use it to
     convert (Download --> Application from the File menu) the file to
     Mac format (probably an SEA file).  Then double-click on the
     converted file and you're on your way!

     Also, Stuffit Deluxe will destuff them. I believe the freeware
     Stuffit Expander will also deal with BinHex files.

     Apple divides all files into up to two "forks" or byte streams, one
     of which, the "resource fork" holds specially formatted data,
     including all of the code segments for a program.  They also have
     different directory attributes, including longer file names and
     attributes called the "type code" and "creator code" which tell the
     operating system what application to launch and what icon to
     display. There are three competing standards (and some proprietary
     solutions) for representing this information on a non-Macintosh
     computer; the most common of which is MacBinary II, which
     originated on Compuserve's MacDev forum.

     Another common work-around is to compress the files using any of
     the standard compression packages; the result is a plain, data fork
     only, file.  You then have to hope that your decompression software
     is smart enough to ignore the missing type and creator codes.

     As somebody already wrote in, the =easy= solution is for you to
     =somehow= obtain a copy of StuffIt Expander 3.5.2.  You can buy
     StuffIt Deluxe at any software shop; that way you get both StuffIt
     Expander and DropStuff. You can pick up StuffIt Expander and the
     annoyanceware version of DropStuff for $2 or so at any Mac user
     group meeting.  Or you can download it from just about any bulletin
     board or online service to your Mac.

     If you're determined to =only= use the modem on your PC, you can
     get baroque and then use a null-modem cable to connect your PC to
     your Mac, and use =terminal software= on both ends to transfer the
     file; the Mac will recognize an incoming MacBinary file and decode
     it. But by the time you rearrange the cables, you might as well
     move the modem this once.

     Once you get StuffIt Expander installed on your Mac, if you have
     System 7.x you can drag and drop just about anything, or even whole
     folders of anything, onto StuffIt Expander's icon and it will
     figure out what archive format was used on each file and unpack it
     all for you.


* Q. I can't get my Macintosh to use the Netware for Mac OS and be able
     to use Soft PC to connect to the server. The Ethernet connection
     will crash whenever I switched between the Mac & PC environment.
  A. Change to a different frame type (802.3 SNAP) on the Mac side


* Q. Where can I find a product for the mac that will run the login
     script?
  A. Wholly Mac Software.
     PO Box 34046
     Las Vegas, Nevada
     USA
     Tel : +1 702 878 3316
     http://www.whollymac.com


3.0 Administrational
====================

* Q. How do I call Novell Technical Support?
  A. Call 1 800 NETWARE (US only) or +1 801 429 7000 (US and Worldwide)
     or +49 211 56320 (Europe)
     (mw)


* Q. Where can I obtain Novell Application Notes?
  A. Back issues of Novell Application Notes and Research Reports are
     available for $15 each (add $5 for shipment outside the U.S.). A
     discount is available for bulk reprint orders of 10 or more copies.

     Contact the Novell Application Notes Order Desk for more information.
     All orders must be prepaid.

     Novell Application Notes Order Desk:

     Voice (toll-free)  : 800-377-4136 (US only)
     Voice              : +1 303-297-2725
     Fax                : +1 303-294-0930

     See the file APPNOT.EXE in the NWGENFILES forum library for a full
     list of Application Notes.
     (mw)


* Q. How do I request an enhancement?
  A. Novell is always interested in hearing suggestions from the user
     community.  If you are interested in submitting an enhancement request,
     you can send E-Mail to one of the addresses noted below.

     Novell Enhancement Requests E-Mail Addresses

     enhclient@novell.com      Client products
     enhserver@novell.com      Server products
     enhprint@novell.com       Printing and utilities
     enhnds@novell.com         Directory services/Timesync
     (sm)


* Q. How do I get an upgrade from NetWare 4.0x to NetWare 4.1?
  A. Call +1 801 429 7000 and ask for After Market Products
     (mw)


* Q. How do I obtain registered IPX addresses?
  A. Send a request via e-mail to registry@novell.com
     (mw)


* Q. Where do I find a list of SAP types and socket numbers?
  A. See LISTNG.EXE in the NWGENFILES forum library or at
     http://support.novell.com/
     (mw)


* Q. Where do I find information about Novell certified hardware and
     software products?
  A. GO NOVLABS or see http://labs.novell.com/
     (mw)


* Q. Where can I find Novell Technical Information Documents (TIDs)
  A. GO NTID or see http://support.novell.com/
     (mw)


* Q. Where can I get information on the Internet about NetWare 4.1/4.11?
  A. http://netware.novell.com/
     (mw)


* Q. Where do I find NetWare 4.1 manuals on the Internet?
  A. http://occam.sjf.novell.com:8080/nw410.english
     (sm)


* Q. Where is the main Novell World Wide Web Server?
  A. http://www.novell.com/
     (mw)


* Q. Where can I find out information regarding NetWare 4.1 and
     competitive products?
  A. For information please see :
     'NetWare and Windows NT Server : A Comparative Analysis'

     For further info please see this document as well as the Novell
     documents :

     'NetWare 4 Reducing Cost of Ownership'
     'When you purchase your network, make sure you get ALL the pieces'
     'Evaluating NetWare 4.1'
     'Novell Strategic Direction'

     These are available from Novell on 801 429 7000 (800-NETWARE)
     or via your local Novell office.

     You might also like to see Novell Application Notes :

     'Building and Auditing a Trusted Network Environment with
     NetWare 4', April 1994
     and
     'An Introduction to Novell's Open Security Architecture', Aug 1994

     These are available from Novell Research on 303 297 2725
     (800-377 4136)

     Info is also available from Novell via the World Wide Web at
     http://netware.novell.com/

     Networking industry analysts who have recently done comparisons
     of Novell and MS networking strategies and products are :

     Forrester
     IDC Research
     Gartner
     The Burton Group

     Please contact these companies to obtain information about their
     reports.
     (mw)


* Q. Where are the main NetWare-related file libraries within NetWire on
     Compuserve?
  A. Please see :

     NWOSFILES - NetWare Operating System Files
     NWGENFILE - NetWare related files
     NOVUSER   - Third-party upload files
     (mw)


* Q. What are the names and functions of all Novell-related forums on
     Compuserve?
  A. See below

     Novell NetWire forum listing
     ============================

     Forums with Message Sections
     ----------------------------

     Novell Client Forum                  - NOVCLIENT
     Novell Connectivity Forum            - NCONNECT
     Novell Desktop Forum                 - NOVDESKTOP
     Novell Developer Product Information - NDEVINFO
     Novell Developer Relations Forum     - NDEVREL
     Novell Developer Support             - NDEVSUPP
     Novell GroupWise Forum               - GROUPWISE
     Novell Information Forum             - NGENERAL
     Novell NetWare 3.X Forum             - NETW3X
     Novell NetWare 4.x Forum             - NETW4X
     Novell Network Management            - NOVMAN
     Novell OS/2 Forum                    - NOVOS2
     Novell User Forum                    - NOVUSER

     Libraries
     ---------

     Novell Operating System Files        - NWOSFILES
     Novell Connectivity Files            - NWGENFILES
     Novell GroupWare files               - NGWFILES
     Novell User's Library                - NOVUSER
     Novell Vendors A Library             - NVENA
     Novell Vendors B Library             - NVENB

     Databases
     ---------

     Novell Buyer's Guide                 - NOVBG
     Novell Labs                          - NOVLABS
     Novell Technical Bulletins           - NTB
     Novell Technical Solutions Database  - NTID
     Novell Technical Solutions Database  - NTID
     (mw)


Original         : 17 May 1995 (NETW4X.FAQ)
Latest Revision  : 20 Dec 1996 (111 Q/As NETW4FAQ.TXT)

(Updated for release of NetWare 4.11/IntranetWare)

With thanks to Suzanne Miles for many additional FAQs.


NETW4FAQ.TXT

Marcus Williamson
http://ourworld.compuserve.com/homepages/Marcus_Williamson/

E-Mail(CIS) : 71333,1665
E-Mail      : 71333.1665@Compuserve.com
