The legacy AppleTalk* protocol stack is not supported as a transport protocol in this version of Novell Native File Access Protocols for Macintosh. AppleTalk migration is targeted for a subsequent release.
Older Mac applications that have unique dependencies upon AppleTalk as a transport protocol must be updated to a version that is known to work over TCP/IP. The AppleTalk stack protocols (TLAP, ELAP, LLAP, DDP, RTMP, AEP, ATP, NBP, ADSP, ZIP, ASP, and PAP) are not supported over TCP/IP by Apple*.
Therefore, Novell does not support those legacy protocols either. Both Novell and Apple have embraced TCP/IP as the Internet standard transport protocol.
IMPORTANT: Older NetWare for Macintosh and Prosoft versions of AFP.NLM and APPLETLK.NLM are not supported. Do not attempt to mix old Mac support NLM programs with the new AFPTCP.NLM.
The MONITOR.NLM on the server does not register Mac connections. Also, the active connections' Network Address list indicates "no address available." This is a known problem for connections other than NCPTM sessions.
Mac users receiving the following error message should check the AppleShare folder in the Extensions folder and try again:
The UserAuthentication Method required by this server can't be found
This error occurs because the new AFPTCP.NLM cannot coexist with prior versions of the AFP.NLM.
To fix this error, do the following:
Unload the old AFP.NLM and remove it from the AUTOEXEC.NCF file.
Unload and delete the old AFPCON.NLM and do not use it again.
Delete the old AFPCON configuration file in SYS:\SYSTEM\GLOBDATA.AFP if it exists.
Make sure that the user's context is in the context search file CTXS.CFG.
Mac OS 8.x will not mount volumes checked to mount at startup. To resolve this, add the server volume's alias to the StartUp Items folder inside the System Folder on the Mac's local startup disk.
When you drag a NetWare folder to the trash, an error occurs because it is unable to leave the item in the trash and it will delete it immediately.
This happens on Mac OS 8.1 with NSS volumes. Also, Mac OS X running with network volumes does not support the functionality associated with the Trash icon.
Certain extensions and control panels (such as MacAdministrator) use filenames beginning with 0x01 to ensure that they load first. These filenames will not work correctly on an NSS volume.
The Winsock component used by the Macintosh Native File Access NLM does not always clean up all open sockets. If you unload AFPTCP.NLM and then explicitly unload WSPDSI.NLM, it might give you the following warning in flashing red text:
WARNING!!!1 active Winsock 2 DSI socket session(s)Unloading WSPDSI.NLM with active session(s) will abend the server.Unload all Winsock 2 apps with active SSL socket session(s).Unload module anyway?Do not unload the module or the server will abend.
The warning is correct. WSPDSI thinks there are still active AFP sessions and it will abend the server if you unload it. The last line of the warning should read "Unload AFPTCP.NLM" but, because AFPTCP is already unloaded, unloading AFPTCP will have no effect.
There is no need to unload WSPDSI manually. AFPTCP.NLM loads it automatically on startup and AFPSTOP.NCF does not unload it. It remains loaded. Under normal use, you should not see this warning.
You might get pervasive errors in a clustered AFP environment when the volume ID is set to higher than 32. To eliminate these errors, use ConsoleOne to edit the cluster AFP/TCP volume resource and change the volume ID to 32 or lower. Remember to make the value you choose unique from other volume IDs.