MacNDS 4 v4.10 Beta
(C) Copyright 1994 Novell, Inc. All rights reserved worldwide.


NetWare UAM v4.00

1. Usage Requirements

The NetWare UAM is required under any of these conditions:

	a.) The "~NetWare Aliases" system extension is used.
	b.) NetWare Directory Services access and authentication is desired.
	c.) The user name is longer than eight (8) characters.
	d.) The password is longer than eight (8) characters.
	e.) The NetWare server does not allow unencrypted passwords.
	f.) The NetWare server enforces a restriction on the station address
      from which a user may log in.

2. Known Problems

PROBLEM #1:  On a multiple script system, a long user name that requires more than one line for display in the login dialog can line-break at blanks.

SOLUTION:  None, but be aware that a blank in a user name could be "hidden" by a line break.

PROBLEM #2:  If a log in attempt fails, perhaps due to an incorrect password or username, the error alert displayed does not respond to the Return or Enter keys.

SOLUTION:  Use the mouse to click the OK button to dismiss the alert.



MacNCP v1.0

1.  Known Problems

PROBLEM #1:  In Systems before 7.1, MacNCP does not work correctly with Virtual Memory turned on or with System Extensions that add Virtual Memory (such as RamDoubler).  In this case, MacNCP will not load and a message will be displayed at startup.

SOLUTION:  Either turn off VM or upgrade the Macintosh to System 7.1.

PROBLEM #2:  If MacIPX autoconfigures an incorrect frame type, MacNCP will be unable to see any IPX services on the network.

SOLUTION:  Manually configure MacIPX to use the correct frame type.

PROBLEM #3:  Configuring Network Address Restrictions for Macintosh Clients.

SOLUTION:  Only an IPX address needs to be entered if the user will always log in using Directory Services. If the user will also log in using bindery emulation, then an AppleTalk address must also be entered.


~NetWare Aliases 1.0

1.  Known Problems

PROBLEM #1:  If an alias created by ~NetWare Aliases is used when ~NetWare Aliases is not installed, the alias may be "updated" to a standard System 7 alias. An alias so updated may not work if the server to which it points requires the NetWare UAM, whether or not ~NetWare Aliases has been reinstalled.

SOLUTION:  Delete the alias and recreate it with ~NetWare Aliases installed.


MacIPX  v1.2

1.  Known Problems

PROBLEM #1:  MacIPX may display an error message containing the error code -94 when trying to use the Ethernet 802.3 frame type with some Ethernet adapters. 

SOLUTION: Install AppleTalk version 58 or later on your Macintosh. Contact your Ethernet adapter vendor to get AppleTalk version 58 or later, or get AppleTalk from Apple's Network Software Installer, version 1.3 or later.

PROBLEM #2: Some third-party applications use their own IPX protocol stacks, and do not use MacIPX.  MacIPX may not function properly in their environments, depending on how MacIPX is configured.

SOLUTION: Contact your application vendor to check the availability of a version of their application that works with MacIPX.  If none is available, you can configure MacIPX to use a network interface setup different from the network interface setup the other IPX protocol stack is using.  For example, if the application's IPX protocol stack is using the Ethernet 802.3 frame type, you can configure MacIPX to use a different frame type, say 802.2.  If this solution is unworkable in your situation, you can configure MacIPX to use the LocalTalk network interface, rather than the interface in use by the other IPX stack (Ethernet, for example).  This solution, however, requires you to install and configure a MacIPX gateway somewhere on your network.  Instructions for MacIPX gateway installation and configuration are located in the NetWare Operating System documentation.