Click for MacWindows home

Access Your Computer From Anywhere
Control a PC from a Mac over the Internet


MacWindows Special Report:

NetWare and Macintosh Issues

Last updated on June 11, 2003

Novell and Prosoft Product Announcements

Prosoft releases NetWare Client for OS X 1.1.2. January 8, 2003 -- Prosoft Engineering has just released NetWare Client for Mac OS X 1.1.2, an update to its client for NetWare servers. The new version allows users to make aliases of NetWare volumes and improves browsing of networks.

Prosoft releases NetWare Client for OS X v1.1. November 22, 2002 -- Yesterday, Prosoft released NetWare Client for Mac OS X - IP Edition version 1.1 (US $149; free upgrade for version 1.0 owners), an update to the Mac OS X native version of the client for NetWare 5 and 6 servers. (See also this press release.) Among the improvements in this version:

Prosoft releases NetWare Client for Mac OS X. July 30 , 2002 -- Prosoft Engineering is now selling NetWare Client for Mac OS X - IP Edition (US $149), a new client that can authenticate to NetWare 5 and 6 servers over IP and participate in native NCP file sharing and NetWare Directory Services (NDS) browsing, without having a NetWare Loadable Module (NLM) running on the server. The new client also supports RSA secure login using NDS. Prosoft says the users can interact with the graphics users interface and a command line.

Novell releases X-platform server NLM. September 25, 2001 -- Last week, Novell released Native File Access Pack (US $299 per server, free upgrade for owners of NetWare maintenance or upgrade protection ), a server add-on that enables Windows, Mac OS, Linux, and UNIX clients to access file storage on Novell NetWare 5.1 servers without special client software. Native File Access Pack provides the the following:

All clients are managed through Managed through Novell eDirectory. Novell also said that Native File Access Pack will be included free with NetWare 6 when it ships.

Novell posts Public Beta of Native File Services. April 18, 2001 -- Novell is has posted a public beta version of the upcoming Novell Native File Access, a set of server-based software that allows Macintosh, Windows, and Unix systems to connect to NetWare servers without adding software to the client. Native File Access for Macintosh allows Mac uses the Apple Filing Protocol (AFP) file sharing client that comes with Mac OS. The readme from Novell Native File Access for Macintosh Beta describes it this way:

Novell Native File Access for Macintosh allows Macintosh users to access storage on a NetWare server using TCP/IP without installing client software on Macintosh workstations and to manage user access to the data using the power of Novell Directory Services (NDS)....

The legacy AppleTalk protocol stack is not supported as a transport protocol in the first release of Novell Native File Access for Macintosh. AppleTalk migration is targeted for a subsequent release...

Native File Access for Windows uses the SMB/CIFS file sharing client (the Client for Microsoft Networks) that comes with Windows. The readme file for the Windows version states "There is no additional Windows workstation configuration required if the Client for Microsoft Networks is installed." Windows clients also get access to NDS.

Unix clients (including Mac OS X, we would assume) use NFS.

Novell Native File Access requires NetWare 5.1 Server with Support Pack 2a. (Thanks to all the readers who alerted us to this release.)

Novell to directly support Macs in NetWare again. March 2, 2000 -- Novell announced that it would take over development of Mac client support from Prosoft Engineering and produce its own product called NetWare 5 File and Print Services for Macintosh. The new product, to ship later this year will provide file and printer access for Mac clients over TCP/IP, the default protocol for NetWare 5. Prosoft's current Client for Macintosh is IPX-based, and Prosoft's NetWare 5 Services for AppleShare installs AppleTalk on the NetWare server. Novell said that Prosoft could continue to sell the current products.

The Novell announcement gave few details about the File and Print Services product. Novell did not indicate whether the new product will be a completely server-based solution or whether it would have client components. Novell also did not mention whether the new product would give Macs access to NDS (NetWare Directory Services).

A MacWeek story questions the impact of the announcement on cross-platform networks.

Reader Reports

Thi oldest reports are directly below. The newer reports are at the bottom.

Prosoft NetWare Client for Macintosh--an early look


We asked Bill Reynolds, a beta tester of the Prosoft NetWare Client 5.12 for Mac OS, if the beta client was an improvement over last Novell version. He replied with this report:

Yes, it's an improvement. You get:
  • A more Mac-like login (I'm not at home right now, but it's basically: go to the Chooser, select the Netware chooser extension [instead of AppleShare], then proceed as with AppleShare or NT servers); and
  • The faster MacIPX connectivity, without any special configuration headaches. (Again, you need to go to the MacIPX control panel on each Mac, command-click on Ethernet, uncheck Autosense and select the appropriate packet type...otherwise, 802.2 or Ethernet II or Ethernet SNAP may be selected when you really want 802.3. You could probably copy the MacIPX prefs from one Mac to many...I don't think any unique address issues are involved, but I haven't checked that out.)

The Netware Chooser Extension defaults to Bindery mode; you have to select NDS every time. I saw a ticket re that already in their system.

Network Admins can consider not running AppleTalk, etc., on their servers, since connectivity is handled via MacIPX. (Mac Name Space is still required, however, so Mac file properties [names, resource forks] are supported.) But I haven't tested this option at all.

I need to fix and set up my LaserWriter so I can test the print queues (or maybe I need an HP4M or other PC-compatible printer?...again, I haven't been down that road before). If I get around to that, I'll send you an update (let me know if anyone else is printing via MacIPX).

I couldn't get the Remote Console software to work.

He also found a bug:

"I haven't had a chance to try MacIPX printing yet, but the Beta1 client is quite similar to the Alpha Preview client. However, one thing that broke between the alpha and beta versions (I opened a ticket) is aliases: If you mount two volumes from the same server, both aliases under Recent Servers point to the same volume (whichever one was mounted first). You have to go back to the Chooser to mount the missing volume (even if you log out completely and try again)."

NOTE: Novell has discontinued its Client for Macintosh. Prosoft Engineering now sells NetWare Client for Mac 5.12, which fixes all of the problems noted below, according to Prosoft.

TIP: NetWare and Mac OS 8.5 error.

Apple's Mac OS 8.5: Open Transport 2.0 Read Me - Part 2 has this note about using the Netware client on Mac OS 8.5:

"When using Netware Client version 5.11 configured for NetwareIP service, the first login may yield a Netware Configuration error message. To avoid this error, open the NetwareIP control panel and change the value under Domain SAP Server (DSS) Retry Attempts from 1 to 2. You can also change Open Transport TCP/IP control panel to always load TCP/IP into memory (open the TCP/IP control panel, click the Options button, and click the "Load only when needed" box to remove the X)."

TIP: Update to Novell NetWare Client for Mac OS 5.11: Fixes problems with Mac OS 8

This note from Novell (download 5.11 Updates).

FIX 1: NetWare UAM. System 8 users could not log in via the Chooser using the NetWare Encryption. (Clear passwords turned off at the server.)

FIX 2: MacIPX Ethernet. Customers using NuBus LAN cards and Open Transport (OT) were not able to use the Novell Client. A work around was to turn off the OT. This update is required for System 8 which only allows OT. For System 7.x users, the OT must be turned back on. (Via the Network Software Selector.)

FIX 3:When a user selects the Collect for Output in QuarkExpress v3.32, the following error is received: "File is locked [-54]"

The Collect for Output attempts to gather all of the linked graphics and prompts the user for a location to store all the files. If they choose the Mac hard drive or the network drive the above error occurs when any of the files are stored on the file server. The Macintosh workstation is logged in to the server via IPX through the NetWare Client for Mac OS 5.11 client.

FIX 4: MacIPX Ethernet always uses OT calls if the Mac is a PCI-based Mac.

Known Issues:

1. Occasionally, MacIPX doesn't find a network and sets the network address to 0. In this case you can go to the MacIPX control panel and select AppleTalk, and then select Ethernet again. Or you can reboot.

2. When 2 cards are installed, it seems to work ok on startup, but in the MacIPX control panel when switching to the other card, sometimes the system will crash.

TIP: Fix for G3 Macs and Netware, and Netware Mac Client 5.11 bug with OT, PCI adapters.

Novell's document explains this.

NetWare Client for Mac OS 5.11 does not support PCI Ethernet and token ring adapters on Power Macs using Mac OS's Open Transport networking software. Novell recommends that you use the Macintosh Client updates MCLUPD3.BIN or later - MCLUPDx.BIN (see the Novell document PCI Net adapters with IW Client Mac 5.1x ). These updates will support PCI & ComSlot II Bus Based Macs for EtherTalk. However, TokenTalk is still not supported. This software is part of the Mac Client update 3.

However, Ken Emery has used this file to fix his problem with Power Mac G3's and Netware (see news item from 2/2/98). He reports:

"Apple seems to have used a different low-level Mentat driver for the G3 and it looks like Novell's older MacIPX was too specific to the older driver.

"The required MacIPX extension comes with CLT511.bin and CLT511.exe (different release dates) but the one that worked is part of mclupdt.exe which you would not guess by looking up "MacIPX" on Novell's search engines. (By the way, it looks like there are several date-stampings on the same version# .., and only one works.) I finally tracked down the one that worked. [mclupd3.bin]."

Emery also points out that a message on Apple's Tech Exchange forum had a message (posted 2/2/98) reporting a PowerBook 3400 problem with Netware. It said the new PB 3400 uses a "3400/G3 Ethernet" system extension.

Further info: Apple has posted a TIL article on the MCLUPD3.BIN file and Netware Client 5.11.

In addition to updating MacIPX with Novell's patch, Bill Reynolds recommends the following:

"Users on an ethernet network should open the MacIPX control panel, COMMAND-Click (not option-click) on the Ethernet driver, turn OFF auto-sensing, and choose the frame type appropriate to their network (802.3 for us).

"Administrators might want to do this for ALL their mac users. I had to make these changes for my 7300/180 when I upgraded to OS 8. But when I added two G3/266 desktop macs, OTHER users began to be affected! I'm slowly making the rounds and resetting MacIPX on all the Macs. Even then, I suspect I need to patch (upgrade) MacIPX on all the Macs, whether they're running OS 8.x or 7.5.5. (Similar to running different flavors of AppleShare client...a definite no-no.)

"BTW, the Netware client install requires (and installs) the older version of AppleShare (AppleShare Workstation ZM 3.6.1)." (See next tip below for more info on AppleShare client versions.)

TIP: Intranetware 4.11 & Mac client 5.11, Mac OS 8.1 -- copying files from server

This tip thanks to Bill Reynolds. On Mac OS 8.1 running Mac client 5.11 (version 4 or 5), Reynolds got read errors whenever he tried to copy files from the server to any other destination. There was no problem with copying files to the servers, or between local disks. A work-around that did succeed was to open a file on the server with an application on the client and use Save As to save the file on the client.

Reynolds tried different combinations of AppleShare -- the Netware client installs the older AppleShare Workstation-ZM 3.6.1 -- and found two solutions:

"1) If you use AppleShare Workstation-ZM 3.6.1 with OS 8.1, do NOT mount Netware 4.1x volumes via the Chooser: BYPASS ASWS 3.6.1 by logging into NDS via MacIPX (the little tree), then use Netware Directory Browser (in the Netware Client Utilities folder installed by the Mac Client installer) to mount any volumes (otherwise, you'll get READ ERRORS during Finder copying from the servers; I've duplicated this at home on my 7300/G3/250 and IW411 on a 486/33 PC!).

"2) You can safely keep OS 8.1's AppleShare 3.7.4 instead of ASWS-ZM 3.6.1 and use EITHER login method: Chooser/AppleShare OR MacIPX/Directory Browser, with these caveats:

"The MacIPX solution is faster in each case above. Also, with AS 3.6.1 and MacIPX (and OS 8.1), logging out from the tree automatically unmounts all Netware volumes, as it did with OS 7.5.5. With AS 3.7.4, OS 8.1 and either login solution, you must trash the volumes manually (or select them and type command-Y) because the volumes appear to be in use, then logout from the tree. (This is true with OS 8.0, also, but the READ ERRORS are not an issue.) You probably do not want different versions of AppleShare in use on different Macs in the same network, so pick the one that works best for you. (If we didn't need AppleShare to access the lo-res and hi-res volumes of our SGI/Indy Colorbus RIP to download oversized FPO art scanned on one of the Canon CLC700S copiers, I'd consider removing it completely.)"

Mac OS 9 won't mount mulitple Netware volumes

First is a description of the problem. Below are several suggestions for fixes as well as descriptions of the cause.

April 17, 2000
Bryan Forrest

I have seen others with this problem, and so far, Apple has refused to acknowledge the problem or claim responsibility. I have done all the basic troubleshooting from eliminating 3rd party extensions to tossing various prefs files to clean installs of the OS to trying this on a brand new virgin G4. Same results every time.

We are having a problem with OS 9 accessing multiple volumes on Novell servers. When multiple volumes from one server are selected to mount at startup, one or more of the volumes may fail to mount. When the settings are checked again in the chooser, the checkbox for Mount At Startup is unchecked. If the user checks the box again and mounts the server, MacOS sends an error message stating that "The name <servername> is already taken. Please use a different name." I have tried experiments with NT servers and with shared folders on another Mac. Neither showed the same results. However, I have read reports from Apple's Tech Exchange of similar results in mounting volumes from Apple File Sharing.

When a server is selected to mount at startup, OS 9 will place a shortcut to that server in a folder called Servers in the System Folder. At startup, AppleShare will check that folder and attempt to mount any servers it finds shortcuts for. Not all volumes are mounting. For example, in SERVER1, VOL01 and VOL03 will both mount with no problem, but VOL02 will not. Likewise, I selected all seven volumes of SERVER2 to mount at startup, and all but Vol2 and Vol4 mounted. Similar results with SERVER3.

Apple suggested mounting the server and creating a shortcut from the server volume, drop the shortcut into the servers folder and see if that worked. Same results.

In testing SERVER1, I renamed VOL02 in the Servers folder so that it would load before VOL01. VOL02 mounted, but suppressed VOL01 from mounting.

The only work-around I know of for this is to place shortcuts for these servers either on the desktop or in an easily accessible folder and have the user double click the server to mount it. This is a little more convenient than having to go through the chooser to mount it, but in the long run this is still not a solution.

TIP: Fixes for NetWare multiple mounting problem.

April 19, 2000 -- We've had a number of responses to the above report about a problem with NetWare that prevents Macs from mounting multiple volumes from one server. First, most readers say that the problem is not specific to Mac OS 9, but occurs with all Mac OS versions. We've also recieved several solutions. Several readers said this was a known problem with aliases and creation dates and suggest solutions. They suggest a utility from JRB Software called setvdate. John DeMillion suggests using the freeware KeyChain AutoUnlock. Here are their reports:

Rick Zeman

Mac OS has a fairly known (or so I thought) problem regarding NetWare servers. The Mac Alias Manager gets confused when server volumes have the same creation date and time. Netware, when volumes are created during install, gives the volumes the same time/date stamp. Ergo, the problem when mounting via aliases.

John Baird, of JRB Utilities fame (must-have tools for Netware geeks), created a tool that will change the creation time of Netware volumes to obviate this problem.

Michael Menne

I don't believe this to be a problem specific to OS 9. The problem relates to how the Mac OS resolves volume aliases. There is a known issue between NetWare and Mac OS. The problem relates to aliases of volumes with identical creation dates and times.

VOL1 Created Mar 19. 1999 1:40:02 am
VOL2 Created Mar 19, 1999 1:40:02 am

If you create aliases of both volumes, the Mac OS gets confused. It will only mount the first volume since they have the identical creation date and time. This doesn't show up on previous Mac OS versions because they don't use Aliases to mount volumes at startup. Since Mac OS 9 does, the problem appears more frequently. The only solution I know of is to change the creation date on the volume. This can be done one of two ways, both of which are simple, but one takes more time than the other.

1)Backup any volume with a duplicate creation date.
Delete those volumes
Recreate the volumes one at a time, backing out of the process after each volume is created.
Restore each volume.

2) Use a utility from called setvdate. This will allow an administrator to change the date of the Netware volume. This is a utility that must be purchased from jrbsoftware.

This should eliminate the problem if the volume creation dates are identical (which is very possible and common.)

John DeMillion

We've been using the freeware KeyChain AutoUnlock to bypass various problems with automounting network volumes under Mac OS 9. It will probably work with multiple Netware volumes, although I haven't tested it.

The utility requires you to create a folder called "Startup Servers" in the System Folder (versus the Mac OS's "Servers" folder). When KeyChain AutoUnlock is run (usually at startup), it will unlock the KeyChain and mount all the servers with aliases in the "Startup Servers" folder. It works great for us with multiple NT volumes and a single Netware volume.

One user, J. Garland Tillery, reports that he does not have this problem using the Netware Client for Mac OS v5.13 with Mac OS 9.0.4. He calls this version "a very stable client for Macs on Novell."

Mac Client for NetWare 5.13 and Office 98 conflict

This is a confirmed bug. A reader below offers a simple fix. However, Version 5.14, released in late March 2001, fixes the bug.

August 21, 2000 --
Francis Barr

It seems there is a bug in the Prosoft NetWare [Mac] client that conflicts with Microsoft Word and Excel (Office 98 versions). If Word is running and you click the application switcher menu the Mac will lock up about 50 percent of the time. Also, after a while the menus in Word fail to operate properly and will again lock up if clicked. This is real pain if you are just going to save a document, and the machine crashes. So far as I can tell there is no fix for this, and no mention of it on the Prosoft web site. The only option for technical support appears to be very expensive, and there is no obvious way to report bugs in a shipping product and get an answer.

I have now checked this out on Macs running systems from 8.6 through 9.04, with G3 and G4 processors - all behave in exactly the same way.

Confirmation from Prosoft

August 22, 2000 --
Rick Zeman

Prosoft knows about this because they said the following on their mailing list on 12 July 2000:
This is a known issue and has been reported to engineering. The same thing will happen if you click on the clock before you click on a menu item. This is not being addressed. If there is a future release of the IPX client then it may be addressed at that point, but there is no plan to update the IPX client. When a contract is finalized with Novell our networking resources will be devoted to the IP client. Since this is a known issue it is something that the engineers will be considering with the IP client.

For now, this is going to have to be something the users don't do.

David Neil
Support Escalation Engineer
Prosoft Engineering, Inc

We Mac Netware users are caught in limbo. I think it's total BS that usersare caught so helplessly in the middle of Novell's outsourcing charade. Iwould imagine that this could easily be fixed and the existing base of 5.13clients patched via an updater. If it's a "known issue," it's unconscionable that "[this] is not being addressed."

Not even Microsoft would treat their paying customers this shabbily....It's not as if this is a subtle bug only affecting a few customers.

August 22, 2000 --
Johann Dijkstra speculates that the order of installation of updates to Office, Outlook for Exchange Server or other Microsoft products may have be playing a roll with this conflict:

I think that the person having this problem is also using Outlook for Exchange server or other Microsoft products. The long wait problem is mentioned before and I think it is only related to the Microsoft products. There are several updates available for Office, Outlook, and Outlook Express and then there are IE 4.5 and 5.

I've seen something like this also but the problem went away after reinstalling one of the updates. I guess the order of the updates is critical also and maybe after installing IE 4.5 or 5 some updates have to be installed again.

Given the fact that the Service Packs for NT have to be reinstalled after a driver installation I think it's a Microsoft way of life.

Just a suggestion

August 24, 2000 --
Shane Palmer reports that after extensive troubleshooting of the conflict, he can add two points to our discussion:

Palmer also has been active on the Prosoft NetWare Client mailing list. We've posted some of these comments as follows:

I have found a serious and 100 percent repeatable bug that involves the following combination of software:
  1. 1. Mac OS 8.5 or greater
  2. 2. Microsoft Office 98 (specifically Word, PowerPoint, Excel, Clip Gallery, Graph, and Organization Chart) & Outlook
  3. 3. NetWare Client 5.13 (also happens with NetWare Client 5.11)

    Here is the scenario. Make sure you have 1 and 3 installed and active. Open any one of the Microsoft products listed in 2, then click on the widget to resize the Finder/Application menu, then click anywhere in the menubar

    and your Mac will freeze. I have tried this on numerous Macs from G4's & G3's to PowerBook 3400's to PowerMac 7300's and every time it freezes. There is also a side affect that even if you don't click the Finder Menu Resize Widget (for lack of a better term) you might freeze just by randomly clicking in the menubar. Every time I try this it will eventually freeze by rapidly clicking at random in the menubar. It takes anywhere from 50 to 100 clicks. I have tested every application on my hard drive for this problem, over 100 of them, and the Microsoft products above are the only ones that have exhibited this behavior. This is not to say Microsoft is at fault however, because Internet Explorer 5.0 does NOT have this problem.

    I support a few hundred Macs at Iowa State University and I have several people that are noticing the problem mostly by clicking anywhere in the menubar. They generally freeze 5 to 10 times a day, which is totally unacceptable. They have been experiencing this problem for about 8 to 12 months (about the time we migrated them to Mac OS 8.5) and at first I did not have a clue as to what was happening. I only recently found out what was causing it completely by accident, because I never use the Finder Menu Resize Widget, and one day while in Word 98 I accidentally clicked the widget, then clicked another menu and it froze. Many others may be having the problem, but are not telling me because they don't realize the pattern.

    I know that a simple solution is just don't click on the Finder Menu Resize Widget, and admittedly most people don't even know about this feature unless they accidentally click on it, but there is still the other half of the problem which is randomly clicking in the menubar.

    I have found that I can get rid of the both of the freezing problems by doing any ONE of the following:

  4. A. Downgrade to Mac OS 8.1 or earlier (i.e. these versions don't have the Finder Menu Resize Widget)
  5. B. Remove the NetWare Client
  6. C. Don't use the affected Microsoft Applications.

    In Option B I even tested with the most minimal System Folder you could have and still run Microsoft Office. As soon as I specifically remove NetWare Client extension (the other extensions for the NetWare client don't pose a problem) the problem goes away. I have even moved the Microsoft shared libraries into the Microsoft Office 98:Office folder so the only thing I have in the Extensions folder is the NetWare Client extension, i.e. ONE extension, and nothing in the Control Panels folder, i.e. ZERO control panels. So I have pretty much eliminated any possibility of extension conflicts.

    I have also found that if I am in Word, for example, and I click on the Finder Menu Resize Widget I can prevent the freeze by switching to the Finder and clicking in the menubar then switching back to Word. At this point I can click in the menubar without freezing.

    Another workaround

August 25, 2000
Paul St. Amand sent us another workaround for the conflict between the Prosoft NetWare Mac client and Microsoft Office. He keeps Office 98 running by uninstalling the Prosoft NetWare client and turning on FTP on the NetWare server:

I too have been searching for the reason that my Mac would freeze upon choosing menu items when in Word or Excel. You have already told users that uninstalling the Prosoft NetWare client will fix the crashing, but that seems to prevent you from getting files from a NetWare server. But not so! If you can get your administrator to turn on ftp capability to your directory, you can use Interarchy (or any ftp program) to get your files. (Note: ftp may only be possible with the latest NetWare 5.1, but I am not sure.)

Make a bookmark in Interarchy and put it in your Apple Menu Items folder and you're all set. When you use Interarchy, the NetWare server directory opens like any folder and you can drag and drop files just as easy as using the Prosoft client. File transfers appear to be just as fast or even faster. This does nothing for printing services, but if like me, you only use the file services on NetWare, then you can toss out the buggy client with it's 6 or so extensions and be done with the crashing! Works great for me.

More on the future of the Mac NetWare Client from Prosoft

October 18, 2000

We asked Prosoft's David Neil about the NetWare Client for Mac and Office bug. He replied:

There is no development happening on this client. The contract expired. Any new contract with Novell will be for an IP client. We have been unable to secure the intellectual property required to develop that client. Novell has been very busy this summer with layoffs an such, so I don't know if that is the reason we haven't been able to finalize a contract or not. We are no longer pursuing it. We are open to Novell, if they decide to bring us a contract, we'll talk.

This issue would certainly be addressed in any future client, but we have yet to identify if it is something we can fix or if Microsoft has to fix it. Recently I spoke with Microsoft about another issue with Office 2001 and they are looking into duplicating that issue to address it. It is possible the two issues are related since the symptoms are similar. There is a possibility that we my find some resolution, but we do not have engineers working on this client.

David Neil
Support Escalation Engineer
Prosoft Engineering, Inc.

Conflict continues with Office 2001, OS 9.1.

January 22, 2001 --
Damien Barrett reports that the conflict with Mac Client for NetWare 5.13 and MS Office also occurs with Office 2001 and Mac OS 9.1:

Reading MacWindows readers comments about the Novell clients and conflicts with Office 98 prompted me to test these conflicts against Mac OS 9.1 and Office 2001. The freeze still occurs with both Mac OS 9.1 and Office 2001.

I haven't had time to test with clean-installs of the OS, but updating to 9.1 and fresh-installing Office 2001 both resulted in the same freeze that's been documented by others [with Office 98].

Now I have to call Prosoft and get my client's money back. They sold me a product that just doesn't work. Ugh.

Simple workaround for NetWare Client and Office 98/2001.

January 23, 2001
Rick Zeman reports having discovered a simple and painless fix for the Office conflict:

I discovered a few months ago that the conflict is avoided by going into the Date and Time control panel and turning off the menu bar clock. Since I did that, I've not had one crash in Word 98, nor in 2001 after I upgraded. Others who have tried this report the same success.

NetWare client 5.14 fixes conflict with MS Office; IP client to come.

March 30, 2001 --Rick Zeman reports that Prosoft Engineering has released NetWare Client for Macintosh 5.14, which fixes the bug that causes the Mac to crash when Microsoft Office is launched, which we first reported last August. Zeman sent us this:

From Prosoft's David Neil on the Prosoft Netware4Mac list:
I have two announcements that will be of interest to this list.

First: The Office bug that causes hangs...remember that one? It's been fixed. Anyone who needs it can contact This is called version 5.14. I want anyone who needs it to have it as soon as possible.

Second: The development contract with Novell that will permit us to develop an IP client has been signed by us and is on it's way back to Novell now.

I contacted Prosoft support and received the updated client nearly immediately.

This new version is a change from Prosoft's previous position, which was "there is no plan to update the IPX client." The new contract with Novell is probably the cause of Prosoft's change of heart.

NetWare-FireWire conflict and workaround

August 22, 2000 --
Paul Rinkes reports of a conflict between Prosoft's NetWare Client 5.13 for Mac and a FireWire hard drive, as well as a workaround:

I've been able to reproduce it faithfully for the past few weeks ...

I've got a Fantom 30GB FireWire external HD with drivers made by Radialogic. I've got a G4 running NetWare Client 5.13, made by Prosoft -- which also makes (or actually IS) Radialogic. so when I have the FireWire extensions enabled on the G4 running OS 9.0.4, I cannot get the MacIPX driver to load at startup. I can't even get it to load when I open the control panel and option-click on "Ethernet."

The only solution I have found: turn off all Radialogic drivers except the FireWire driver, then open the MacIPX control panel and option-click on the Ethernet option. then you can log on to the tree and mount the Novell volume(s) successfully.

Future of Macs in NetWare: native AFP/IP server support

August 24, 2000 -- Mike Maday said he found the answers to how Novell will support Macs in the future by going to and opening novell.macintosh forum. He says:

There's good info on what's on tap for Mac's in a Novell environment. In fact, Dan Lawyer and Tim Meyer are two guys in charge of the Apple product protocol suite, due out in beta in a few months. You can talk to them directly!

In a nutshell:

MacIPX prevents PowerBook with AirPort from waking from sleep

February 16, 2001
Kim David Hawksworth

We have three Apple firewire laptops (2 iBook SEs, 1 PowerBook) running OS 9.1. All three have Airport cards and connect to our Novell 4.11 LAN using the 5.11 client. 

When the MacIPX control panel is set to Ethernet (2) (ethernet built-in), the portable won't wake from sleep when put to sleep by closing the lid or selecting "Sleep" from the "Special" menu. The screen remains black when the lid is opened and/or a key is pressed. You can hear the hard drive spin up, but there's no screen display. Pressing the Command-CTRL-Power keys is the only option for bringing the computer back to life. What's interesting is that this problem does not occur when the MacIPX CP is set to Ethernet (1) (the Airport card). Nor does it happen with the built-in ethernet on a 400 mhz iMac SE running the same version of the OS and Netware client.

We have tried a number of work arounds including disabling the Airport extensions without any success.

Reader attributes problem to Mac OS 9.1

February 20, 2001
Thomas Koons

I am having this same problem but with a PowerBook Wallstreet and just the built in Ethernet. I had no issues at all putting it to sleep with OS 9.0.4 but as soon as I tried OS 9.1, it crashes on wake every single time! I get a gray screen but no mouse and the HD does spin up. I have to do the key combo reboot to rescue it.

I thought it may have been do to my use of the Multiple user control panel but now I think its a more OS 9.1 issue with PowerBooks.

Another issue I found was that I could not keep selected the "turn off power to inactive PC cards" in the Energy Saver control panel installed by OS 9.1. Once selected and then I close the window and reopen the window, it would be unselected again. reverting to the older 9.0.4 version of the control panel worked fine. This brings up another point.

The new ES control panel does not have the selection for reconnect to servers on wake up like the older version does. The older version, when I select this feature locks up the PowerBook. The new version might have this feature active all the time which means you cannot turn it off and it will always lock me up.

So I have 2 issues that could be causing my PowerBook to lock and both due to OS 9.1 install.

Koons told us he was not using MacIPX:

No, I am just using plain old Apple TCP/IP control panel and ethernet built in. I am connected to an ASIP 6.3.2 server via a Linksys Cable/DSL router which also supplies my internet via Motorola Cybersurfer Cable modem with COX @Home service.

Sleep/AirPort problem occurs with iBook, 9.0.4 and 9.1

I can add to the mix that I have experienced the same problem, but can add different circumstances to the list. I'm am experiencing this problem with:

iBook (no FireWire), OS 9.0.4 and 9.1). It doesn't seem to be a 9.1 only problem. MacIPX from Novell Client 5.13, Airport Ethernet connection.

It probably occurs close to 75 percent of the time when connected to a Novell server via the airport card. Frequency decreases if there are no active server connections. Also, it occurs with 1) closing the lid, 2) choosing "sleep" and 3) auto sleep through the Energy Saver control panel. I don't think it has occurred with built-in Ethernet, but I very rarely allow it to go to sleep when it is using built-in Ethernet.

The only "fixes" I have are making sure to log out before putting it to sleep and preventing it from going to sleep when possible.

NetWare Client for Mac can't get into folders

Paul Rinkes
April 16, 2001

[A user has a] G4 w/OS 9.0.4 and the NetWare Client for Mac v. 5.13. When she's in an application that uses apple's built-in API to open a file (word 2001, for instance), she can open the top level of her mounted Novell volume, but any attempt to go below the top level automatically returns her to the "desktop," where she can choose to go into the Novell volume again -- only to be booted back again. Apps that don't use this API (quark is my example) don't have this problem.

I've not seen anyone report on this, so maybe it's the Novell server config.

If you've seen this problem, please let us know.

April 18, 2001
Greg Cox

It can't be fixed on the server as far as I know. I have seen this reported to Novell technicians, and the team working on the new AFP/IP Native File Access pack is aware of the problem. Hopefully we will see a fix in the upcoming releases from Novell and Prosoft.

April 18, 2001
Geoff Strickler

Try disabling Apple's Navigation Services. I haven't personally dealt with this, but numerous people on the Novell Services for Mac support forum report that the Prosoft Client 5.13 is incompatible with Apple's Navigation Services.

November 27, 2001
Byron Duvall

We have the same problem. We just installed new NetWare 5.1 servers and started migrating users to them. On the Macs with Prosoft's client version 5.13 installed, whenever we use an application that uses the newer style "Navigation Services" dialogs, drilling down to a folder causes us to be booted back to the "Desktop" menu.

We have narrowed it down to NSS volumes only. The SYS volume (which is traditional) on the same server works correctly under the same circumstances. We are running dual-NICs on the new servers using Cisco Fast EtherChannel. We disabled this, and even forced the NIC into 10 Half with no luck. We have also tried running MACFILE.NLM on the server, but had no luck there either. We installed the latest NSS update for NetWare 5.1. We are running the latest service pack as well.

Our next thought was to try Native File Access Pack (NFAP), but now that it's out of beta, it can't be downloaded from their website. I just noticed today that there is a version 5.14 available from Prosoft via e-mail, but I'm not holding my breath that it will fix this problem.

NetWare/Copy Agent showing 1.9 GB available space problem

April 30, 2001
Scott Kirchner discovered his Novell server was telling his Mac that there was on 1.9 GB of free space left, a problem that occurs with Windows NT Server. He describes the problem and how to fix it:

I have a G4 running Mac OS 9.0.4 using Prosoft client for Novell, the most current. I am using Copy Agent by Connectix to copy files over to a shared volume on the Novel side. The problem is, The Novell volume is reporting that there is only 1.9 gigs of space available, but I know that there has been something like 20-30 gigs allocated by the Novell Admin.

I have found out that if you are using Novel 4.2 that in some versions under (less than) service kit 9, are missing the AFP Con. This is the "utility"?? that a Novell admin would use to set the permission that allows a user to see volumes larger than 2 GB. This permission should allow a user to see up to 8 TB on the remote side.

I am passing this info on from people who are admins of Novell systems. I am not. Also, A good article explaining this on the Novel web site is number 2957945.

May 1, 2001
Rick Zeman

System 9.04 should report the full size available; I wonder if Copy Agent is masking the true size.

If he's using the Prosoft Client, he's talking IPX, not AppleTalk, to the server. Afpcon is only for managing a Netware server running the Netware AppleShare (AFP) server. The reason it was "missing" is because the Macintosh server wasn't installed; if it was installed, he'd have afpcon. Yes, afpcon has a setting for what he says, but it's totally irrelevant to anyone not running the AFP server.

NetWare 5.1.3 client for Mac printing problem (actually a Suitcase problem)

July 6, 2001
Chris Brown

On a PowerBook G3 OS 9.1, installed NetWare 5.1.3 as per instructions, NetWare works fine. Printing is not happening. Having setup the desktop printer with NetWare Queues, printing from Stickies (avoiding any Office issues) the instant response is the message "no desktop printer exists for this spool file. the file has been moved to the trash". The desktop printer icon created, is there on the desktop. If one goes to printing>change setup from the main menu, and clicks autosetup, the Mac crashes, and a forced restart is required.

No one seems to have a solution at the moment.

If you've seen this problem, please let us know.

July 11, 2001
Al Kalis

I have had just the opposite experience. I have 6 Macs (out of around 15) running MacOS 9.1 with NetWare Client 5.1.3 installed. The other Macs are running 8.1 or 8.6. The Macs range from an all in one G3 to a 5400/180. All are connected via Ethernet to my school's dozen or so printers, ranging from Lexmarks to old Apple Laserwriter IIs. All print to any of them, there is no problem. We have a Window server, I think running Windows 98 with the NetWare software.

Possible Explanation and workaround:

July 12, 2001 -- Damien Barrett suspects that this problem is actually a problem with Extensis Suitcase, and not with the NetWare client. The Extensis Suitcase 9 FAQ page describes the problem and a workaround:

I'm running Suitcase 9 in OS 9.1 and I cannot print without deactivating either ATM Lite or MenuFonts. Is there a fix for this?

Yes. Browse into your System Folder: Control Panels folder on your hard drive and locate ~Suitcase 9 MenuFonts™. Rename the file by adding a space right after the ~ so it is ~ Suitcase 9 MenuFonts™. Reboot your machine, and you should be able to print again.

Also, be sure that you are running at least version 4.6.1 of ATM Light, which can be downloaded from Adobe.

Barrett describes his experience:

I ran into very similar errors after I had updated some of my computers to OS 9.1 and discovered the workaround described in the URL above. I haven't been able to reproduce the printing problem at my client that uses ProSoft 5.1.3 client.

July 16, 2001
Mike Potter

Our G4 Tower (running OS 9.1) did not have a NetWare client installed but had a strange problem printing. We could select a printer in the Chooser, create a desktop printer, and try to print from any application. The print dialog box would disappear after clicking "OK" but document never spooled.

Sometimes, we'd also receive a message that there was no printer selected in the Chooser, upon which we'd open the Chooser, select a printer, and try to print again to see that same error message.

This had us completely baffled. A hardware problem with a network-connected printer led us further astray.

We can confirm, however, that the suggested solution on MacWindows to rename the Suitcase Menu Font control panel to "~ Suitcase 9 Menu Font," allowing ATM to load last, fixed our problem.

Macs locked out of Internet by Novell Bordermanager

July 23, 2001
Lyle Rogalla can't access the Internet from his Mac on a NetWare network, and his network people are telling him the problem is Novell Bordermanager:

My IT Manager tell me until there is a Novell Bordermanager and client trust for the Mac I am prevented from access the Internet...Bordermanager Error #403 with Mac Netware Client 5.13 and IE5 or Netscape 4.77: I am using Prosoft's Netware Client 5.13 and my company's Novell network is version 5. I am the only Mac and I have no trouble accessing any of the public services, folders or printers Netware works great. My problem is this, even though Netware 5.13 says I am logged in and authenticated, when ever I attempt to access the Internet with IE5, Netscape 4.77 Bordermanager returns the error #403 you are not logged in. What do I tell my IT department to correct this problem.

If you've seen this problem, please let us know.

July 24, 2001
Michael Prewitt has a suggestion:

I'm in the same situation with BorderManger running on a Novell network at work. I can access the Internet through VPC with the client trust app installed, but cannot access the Internet on the Mac alone. The solution our IT department came up with was to give me the IP address of a machine running Microsoft Proxy Server, thus bypassing BorderManager. This has worked just fine for me. Hopefully Lyle's IT department will give him the same option.

August 16, 2001
Dennis Chang

We too have this problem. All of our several Macs, running Mac OS 8.x to 9.1 and using Apple TCP/IP, must bypass Bordermanager with direct connections out to the Internet. We do not have any Netware-provided clients for Mac OS or the Prosoft-provided client. Our Mac's Internet Explorer browsers simply fail to connect when trying to go through Bordermanager as a proxy server. Funny thing is, our LINUX boxes have no problems going straight through, proving that you don't need a NetWare client to make use of Bordermanager. So, our solution has been to put the Macs on a subnet that is routed out directly through our T1 to the Net.

October 26, 2001
Kyle Skrinak

There are some things to consider:

1) Internet Explorer (Mac 4.x - 5.x) handles certificates differently than Netscape on the Mac. Therefore, a Mac client behind a BorderManager firewall would do well to first connect using Netscape -- enter the required account information and then one may proceed to browse with either client. It seems that once your Mac has established a certificate at a fixed address that that IP then has free reign -- until the certificate expires. In our case, every seven days. Note too that DHCP is unstable in a Novell environment and the Macs must use static (manually-assigned) IP addresses. Probably another rub for the IT crew.

2) My problem is that if I use the same firewall proxy settings for my OS X environment, my OS X apps won't pass data to and from the BM firewall -- BUT -- my Classic apps, even from within OS X -- work fine! Likewise for my emulated Linux environment (Virtual PC/Mandrake) booted from either OS X or Classic, either VPC 4.0.2 (Classic) or 4.0.6 (OS X public beta) I haven't bothered to perform packet analysis to see what is different about the data coming from either environment. So, I'm browsing in my Classic environment within OS X -- which is -- relatively stable -- but I am becoming accustomed to the better memory protection of OS X and would rather switch than fight.

I hope some one has an idea how to resolve this. Subnetting to bypass the firewall is not an option here.

A work around: log in with Virtual PC

January 27, 2003 --Bill Brothers found a workaround to the problem -- he uses Virtual PC to log into the Bordermanager. Then he can use Mac Internet software:

I can log in through the Novell Bordermanager using Virtual PC from Connectix VPC using Windows 2000 and Internet Explorer on the VPC and a shared IP address between my Mac and the VPC .

After logging in on the virtual machine I can use the Mac IE or Safari to surf the web, run Software Update, etc. and Apple's Mail, Sherlock or any app that needs the web. It's a little time consuming to boot the Mac, then the VPC, the VPC IE, get through Novell Bordermanager, and then start the Mac app like Safari to access the web.

If you don't need anything else with the VPC you can quit the Connectix app (save the VPC settings) and the Internet port will still be open. However, if there is a timeout on the Novell system and you don't access the web for awhile, you'll have to repeat the process by booting the VPC again. Unless having the VPC minimized causes you grief, leave it minimized. If a timeout occurs, going to any new web address using the VPC IE will force a new login through the Novell Bordermanager. Log in again, then just minimize it again and work with the Mac.

Slowdown of Mac OS 9.1 with NetWare 4 server, Prosoft client

October 2, 2001
Vince Vetere

I have encountered a problem with Mac OS 9.1 and up accessing a NetWare 4.1 server. Accessing the network volume slows to an unbearable crawl. I have tried both NetWare Client 5.11 from Novell and Client 5.13 from ProSoft Engineering. Several e-mails from ProSoft have been unable to fix the problem. All works fine with OS 9.0.4 and lower. The main slowdown is in the Finder updating window contents, but the machine is considerably slower all around. I have tried several computers and they all experience exactly the same problem.

The degree of the performance degradation is much worse for people who log in that have access to more directories than other users. For example, teachers who log in have access to student directories. When students log in, the problem is much better. Please also note that the slowdown occurs for teachers whether or not any directories are open on the server volume.

If you've seen this problem, please let us know.

A suggestion:

October 4, 2001
Steven Kline

I have also had problems with a slowdown of the Finder, normally when opening a folder with many directories (500-1000). I have had pretty good luck raising the files= line on the Novell server startup config file (I'm not the admin, but I think it's called startup.ncf). Increasing this files buffer seems to help the problem.

Moofing around with the Prosoft Netware Client

September 25, 2001 -- Dan Pusateri found a strange artifact when accessing a NetWare volume from AppleWorks using the Prosoft NetWare Client 5.13:

When navigating in the NetWare volume and you're deep in a folder and look at the path in the pull down menu to get to the Desktop for instance - instead of seeing the word "Desktop" and the volume name I will see "Moof" in those spots.

"Moof" is the signature slogan of Clarus the dogcow, the Apple developer mascot who appears in the Print Setup dialog of Mac OS 9 and earlier.

September 26, 2001 -- Half a dozen readers report also seeing the strange problem. Several of these people sent in screen shots. All show the same thing--the word Moof in place of the Desktop and the mounted volume name:

Sara Porter reported the "problem" like this:

I noticed this a couple of months ago using MacOS 8.6/9.x with Prosoft's 5.12 client and thought it was our Admin's idea of a joke (he's a former Mac user)...apparently not. The first layer Moof (the hand holding an Apple) take user to the Desktop while the last layer Moof (globe) takes the user to Network browsing.

The names change if you actually browse to them- so hand-holding Apple Moof becomes Desktop and World Moof becomes Network.

It also occurs with applications besides AppleWorks. James Commons reports:

Although we have not had the same exact problem, we do see the "Moof" when saving or opening from a NetWare server with CodeWarrior 5.0. We use Mac OS versions 9.0 and 9.1 with iMacs, and G3's.

Apparently, the issue is not limited to the NetWare client, either. Michael Sayer said he sees this with DAVE accessing a Windows NT server.

October 2, 2001 -- We have more readers reporting that Novell NetWare volumes appear as named "Moof" from the Mac. Marla Poirier said:

Under the aforesaid conditions, I see "moof, moof, moof" every time. Appears to be a glitch in some programs. Macintosh G4, running OS 9.04, with Prosoft 5.13 and NetWare 5.

Steve Huizinga said "I noticed this quite a while ago."

History of Clarus the Dogcow. October 4, 2001 -- In response to our recent reports of the word Moof appearing in the open dialogs when accessing network volumes with NetWare Client and DAVE, a number of readers have asked about Clarus the Dogcow and the "moof" sound it makes. We aim to please, and refer you to this history of Clarus the Dogcow article at the Apple web site. Originally part of the first Macs' Cairo font, Clarus seems to have completely disappeared from Mac OS X.

Prosoft client 5.13 file name problem

October 8, 2001
Chris Altemeier

What made me decide to ditch the NetWare Client 5.13 from ProSoft Engineering was when we burned CDR's (Mac OS 9.0.4). All or most of our file names, especially fonts, ended up being truncated. This caused major problems when our files were sent to the service bureau. Nothing linked properly in our page layout program.

If you've seen this problem, please let us know.

October 10, 2001
Steve Huizinga sent us a solution :

I am also using Prosoft client v5.13 and I found that after installing the Joliet volume access extension I was able to to copy CDs with the full file names with no problems. I don't recall ever having this problem when burning new disks from files located on my hard drive. I only found I had a problem when I tried to burn a copy of a PC/Joliet formatted disk. The filenames on the copy I would burn were truncated.

Had no problems after installing the extension. I don't really see how NetWare can be to blame for this problem. Are files being burned off of the network the only files that have problems?

Problem with aliases in Mac OS 8.x and Novell Native File Access: a known problem with a fix

November 9, 2001 -- John McGonigal finds that aliases to items on NetWare volumes don't work:

I run a NetWare network with Mac and Windows OS and have come across a bug concerning Mac OS 8.6 access NetWare 5.1 volumes and resources via aliases. The aliases just do not work. When an alias is used to access a network resource and error message appears that says the resource (file, volume, application) can not be found on the network. Yet on an OS 9.2 machine aliases work just fine.

I have reported this to Novell (just today) and have not heard back. As yet there doesn't seem to be any information out there on this problem.

November 15, 2001
Dave Pooser

I run a NetWare network with Mac and Windows OS and have come across a bug concerning Mac OS 8.6 access NetWare 5.1 volumes and resources via aliases. The aliases just do not work. When an alias is used to access a network resource and error message appears that says the resource (file, volume, application) can not be found on the network. Yet on an OS 9.2 machine aliases work just fine.

I saw a very similar problem using an AppleShare IP server running 6.3.3--as I recall, updating to a later version of the AppleShare client software fixed it.

The Solution:

November 15, 2001
Douglas Phillips of Novell says this is a known problem and that a fix is available:

Yes this is a known problem, (I think it was even in the read me). It only effects Mac OS 8.x, I think there is a patch file out on our support site and the fix will be in SP1.

November 15, 2001
John McGonigal elaborates on the fix, which he says does indeed work:

The latest update is that Novell has developed a new build on the AFPTCP.NLM that is the core of the Native file access that allows Macs to connect to NetWare 5.1 or later servers using Apple Talk Client. I received a test version today, installed it and it solved the problem(that is aliases would allow access to services). This patch is in the nonsupport patch phase right now. I suppose that Novell will be posting an update in the days to come.

Another interesting note is that my Mac OS 8.6 had an Apple Share Client 3.8.3 which would only let me mount one of the two volumes on the NetWare server. When I update to Apple Share Client 3.8.8 I could mount both volumes.

The before mentioned AFPTCP.NLM only took a couple minute to install and make operable. That is a cool thing about NetWare.

NetWare support for Mac OS X

November 14, 2001 -- Richard Heend reports that the Prosoft NetWare Client for Mac 5.13 does not work in Classic mode in Mac OS X 10.1

November 26, 2001 -- A source who wishes to remain anonymous passes this on about Mac OS X access to NetWare networks:

Prosoft has been hired to create an OS X client and their original time frame was IP client by end of Q4 2001 and IPX by end of Q1 2002. Unfortunately due to some problems they ran into, the time tables have been shifted back at least one quarter.

Also, If you are running Novell 5.1x or higher, it is possible to authenticate using Windows authentication (SMB). 5.1x you need a patch and 6.x is native.

As for 5.13 client not working in Classic, it won't work because Classic can not touch the physical layer (network card).

Migrating from NetWare to Windows Servers

February 18, 2002-- When moving Mac files from NetWare servers to Windows servers, the resource forks (as well as icons and type and creator codes) of the Mac files will be lost.

One way to retain the resource forks is move the files from a Macintosh: mount both servers and use the Finder to copy files. A way to automate is to use Retrospect from Dantz. An anonymous reader says:

We use retrospect to back up local machines. It has a duplicate function. So, what I do is mount both volumes. Use the duplicate function and chose source and destination and set it to copy corresponding files. It will keep up with what it could not copy (open files) plus if you need to copy again it will only copy what has changed.

Don Haldane reports:

We have just finished migrating Mac files from Novell to Windows 2000, (4 servers in all). Just use Retrospect and set up a script to to a duplicate. All docs must be closed on client machines, otherwise those open files will not copy.

Disconnects with NetWare 5.1, Native File Access Pack and Macs

February 26, 2002
Ron Bishop

We just installed Native File Access Pack on a Novell 5.1 server to connect via TCP/IP (We are migrating our Macs to OS X to take advantage of DTI's AdSpeed Systems.) However, we are getting random disconnecting during file transfers with the server. Then, we can't delete the files from the server because the server says they are in use. No disconnections occur if nothing is happening. This problem occurs in OS X, Os 9.x, and Os 8.x.

My boss says that several other companies are experiencing the same problem. No troubles on the PC side.

Suggestion: new version may fix

Mike Maday
March 1, 2002

Make sure the NetWare 5.1/6.0 servers are patched to the latest AFPTCP.NLM, version J as a separate download (Our random disconnect problem went away with this version). Also, there's a NFAP service pack that was released on February 26th. Search for NFAP1SP1.EXE or Document ID 2961627 at Novell's support site. Please note: With OS 9.x, there's an Ethernet update that you may need to apply to the Macs in question aside from any server patches.

John Endahl
March 1, 2002

Our school has had similar problems. Are they running the latest version of AFPTCP? I believe it is AFPj100, that has improved our connection success.

OS X athentication using NetWare LDAP

Here is some information on OS X login authentication to NetWare LDAP. (Our Mac OS X report page has information about using Mac OS X 10.1.3 with Microsoft authentication.)

April 16, 2002 -- Petri Asikainen of Finland has posted a web page describing how to integrate MacOS X with Novell's E-Directory (LDAP).

March 26, 2002
Adrian Cadden pointed us toward an article called How to Integrate MacOS X with E-directory, which provides some details. However, Scott Krajewski has read this article but has not been able to make it work:

While I can't say I've succeeded yet-- though not from lack of trying -- I've been following closely and an early success was just reported at [the How to Integrate article] I'm still baffled why all of the suggestions noted there haven't worked here. But I suppose it may be due to something in our LDAP setup or attributes.

March 26, 2002
An anonymous reader reports that Apple has demonstrated NetWare integration:

An Apple engineer named Dan Sinema (sp) in Provo Utah has successfully demonstrated this a couple of weeks ago at a tech conference in Salt Lake City. He connected directly to a users home directory on a Novell 6 server from the login screen on an OS X box. It was super to watch all the PC techs look at that one. He is writing an Apple tech article on how to do that.

March 26, 2002
John Endahl

Haven't done this myself yet, as I don't have an X server with Mac Manager installed, but have asked the question at a couple of Apple seminars...

An Apple engineer told me you can use the Mac Manager piece for logon and point it to a Novell LDAP server for authentication information, and even have the user's server-based folder mount during login.

March 26, 2002
David Morrison heard of a limitation with Mac OS X login authentication to NetWare:

Not doing it myself, but someone did tell me that the Novell LDAP server did not support MD5 encryption of the passwords. Ergo, passwords traverse the network in plain text...

If you can shed some light on this topic, please let us know.

Microsoft Services for NetWare SP1 lets you move Mac files from NetWare to Win servers.

June 19, 2002
Patrick Peccatte pointed us to Microsoft Knowledge Base article Q316094, which describes Service Pack 1 for NetWare for Mac:

According to "List of Problems That Are Fixed in Services for NetWare 5.0 Service Packs (Q316094)" Services for NetWare SP1 allows to migrate Macintosh files from NetWare volumes toward Windows 2000 SFM volumes (which avoid to connect a Macintosh on both NetWare and NT2K boxes to do the job).

(Peccatte credits Mike Maday for the tip.)

Prosoft NetWare client crashing when opening files

Several readers have reported problems with the Prosoft NetWare client crashing when opening files using the Open dialog box of Illustrator, Quark XPress, Photoshop, and other applications. A workaround is offeredbelow.

July 23, 2001
Jim Scharosch

I am having a problem opening and saving on a Novell Netware 4.11 server with folders containing a large number of Photoshop files with any application that will show Photoshop documents in the open dialog box using Navigation Services. The application will die with an "unexpected quit" error. I can consistently reproduce this same issue with Photoshop 6.0.1, Illustrator 9.0.2, GoLive 5.0, and ImageReady 3.0.1. All of these apps show Photoshop documents in the file list in the open dialog box. The new version of Toast and iMovie also use NavServices, but they do not show Photoshop documents in their open dialog box and thus do not have the problem. I suspect if there were non-Adobe apps that would list Photoshop files using NavServices they would exhibit the same behavior as the Adobe apps do. I have not tried to figure out how many documents must reside in the folder before this behavior starts to occur. If I copy this exact folder to an AppleShare IP server I do not have the problem.

We are not running the Prosoft client. I found a poster on Adobe's forums who is using the Prosoft client and is having the same issue. I have tested this on four Macs, all running OS 9.1 with current versions of Adobe products. 2 of the machines have had the OS and Photoshop reinstalled on a reformatted disk. Have done all the usual testing of running with minimal extensions. Old versions of Adobe products that do not use NavServices work fine.

If you've seen this problem, please let us know.

July 24, 2001
Hugh Justham

I have definitely experienced the same problem using Prosoft client 5.13 and 5.14. I had previously thought that issue was related to MacIPX and my client had considered using the AppleShare NLM on the NetWare 5 server to solve it so it is interesting that it occurs in this case as well.

My client's Mac users are now reluctant to use the new versions of Photoshop, Illustrator etc. The problem seems to occur after a period of use making me suspect a memory leak. We had previously found the problem in attaching/detaching files in Lotus Notes 5.x but by using Default Folder, Navigation Services can be disabled. However, Navigation Services cannot be turned off in the current Adobe apps.

This has been one of the (minor) issues leading to an agreed future move to Win 2000 for file and print. The others have been the lack of an IP client, unreliability of returning a valid network number and Novell general lack of interest in the Mac platform.

June 19, 2002 -- Jeff Lucia reports a problem with the Prosoft NetWare client crashing when opening files using the Open dialog box of Illustrator, Quark XPress, and Photoshop. Prosoft Client 5.14 fixed a problem with MS Office crashing, but Lucia says this version didn't help here:

I have a client who was using about 10 iMac 350's connected to a NetWare Server. The iMacs were running flawlessly and were using Prosoft Client 5.12. Since we upgraded them to G4 1 GHz DP's we have had nothing but trouble.

The problem we are seeing most is crashing when opening files (from within applications - Illustrator, Quark, Photoshop). Performance is also horrible from within applications - constant pausing or just really slow load times. I have since updated to Prosoft Client 5.14 which resolved nothing. My only workaround is to have the client drag the files from the server to their local hard disk and open from there. Everything works fine in that scenario, but it is unacceptable to the client (I don't blame them).

According to Prosoft, Apple has made some change the OS which is causing this problem. They claim that it is Apple's responsibility not theirs, but I see no updates (or tech notes) from Apple coming anytime soon. Since I am not a Novell guru, I am looking to the MacWindows community (like I have before) for some advice.

The new G4's are using MacOS 9.22. Since the iMac's were working perfectly before running on OS 9.1, I'm assuming the Prosoft tech was referring to "changes" made in OS 9.21 and above.

Possible cause: Prosoft says Apple's Navigation Services causes NetWare client crash

June 21, 2002 -- Jeff Lucia updated his June 19 report . He has word that Prosoft is aware of the problem:

My partner was in contact with Prosoft a couple of months ago and this was the email that was sent to him:
The bug they are experiencing is in Apple's Navigation Services code. The 5.15 update is an unofficial release and it helps some issues, but the hang problems are still part of Apple's bug. There isn't anything we can do other then what we've done, which is report the bug to Apple.

In the mean time I would recommend they move files locally to work on them and then drag and drop them back on the server when they've been modified. It's not a clean solution, but it's what can be done until Apple fixes Navigation Services.


David Neil
Product Manager
Prosoft Engineering, Inc.

June 25, 2002
Simon Triggs question's Prosoft's claim that the problem is Apple's fault:

Prosoft's response puzzles me a little. If there is a bug in Apple's Navigation Services code why don't we see this in AppleTalk, OT, SMB or any other protocol? Surely Prosoft can work around the bug if Apple has managed to do so and other third party protocol providers? This also doesn't fully explain the problem Navigation services isn't used by all applications, Quark Express 4.11 still uses the old standard file open dialog and still exhibits crashing problems from time to time.

June 25, 2002
Patrick Fergus

I've seen plenty of examples of the NetWare open/save crashing bug. I first saw it about a year ago, but couldn't put my finger on a cause. Since then I've seen it in other Novell/Mac installations.

The important parts to reproduce it seem to be a Navigation Services dialog, and opening/saving directly on the server. Standard file dialogs (QuarkXPress 4 especially) seem to not have a problem. The listing of Photoshop files (under the second heading above) could be a requirement, but since the Adobe apps are usually what the client is using it's not a valid test. The crash generally occurs right after the user has double-clicked on a folder/volume, and the Navigation Services dialog box is querying file information from the server.

In the last year I've worked with three clients who use Novell and Macs:

--One has ditched Novell entirely for the Macs and has gone to NT/2000 for serving the Macs. According to them, support calls for the Macs dropped dramatically.

--One is seriously looking at getting rid of Novell for the Macs, whether waiting for the next budget cycle, or using a spare NT server with a lot of disk space.

--One has nobody working directly off the servers, and instead has all users copy down the files they are working on.


June 25, 2002
Hugh Justham

You can mitigate or resolve this problem by using Default Folder [from St. Claire Software] to turn off Navigation services and so use the "Classic" file dialogs instead.

However, some apps - possibly those built with certain versions of PowerPlant - do not respond to Default Folder. Lotus Notes 5.0.10 will, but Photoshop 6.01 will not, respond to Default folder 3.13

Reader review: Novell's Native File Service

June 25, 2002
Andre Kuehnemund provided this report of Novell's Native File Services for Macs:

I've been responsible for integrating Macs with NetWare environments for years while working at a university, an advertising agency and now a wholesale distributor. I was a beta tester of Novell's Native File Services product and I have to say: It really works! And it works well!

No client software is required on the Mac. In OS 9, one simply connects through the Chooser, in OS X via the Go menu at the top of the screen. Connectivity is via TCP/IP and it's fast! Access can be (and should be) encrypted, but clear text passwords are a (not recommended) option. The initial release that came with NetWare 6 was not all that stable, but since SP1 and another update patch have been released, I have not have had any more problems with this product.

Since access to the NetWare server is via TCP/IP, I can access my NetWare server from home, a hotel room, a friend's computer etc. Passwords are encrypted and all I had to do was to open port 524 in the corporate firewall. Setup in NetWare 6 is super easy since it comes with NetWare 6 "out of the box". During the NetWare 6 install the person installing the OS is being asked whether he/she wants to install Native File Services for Mac, Windows and UNIX. Say "Yes" and the installer does the rest.

Neither Macs, Windows nor UNIX machines require any client software. The NetWare server simply looks to the client like any other AFP over TCP/IP, Windows SMB or UNIX NFS server, which is why no client software is required.

The product is available as an add-on ($299 per server) for NetWare 5.1, but is included for free in NetWare 6.

International Charactor problem with NetWare IP for Mac OS X client

August 6, 2002
Bernard Merindol reports a problem with international character with Prosoft's NetWare Client for Mac OS X:

I had purchased the beta version of NetWare Client for Mac OS X IP Edition. After I installed the final version, it no longer works with international characters, such as " é,à ,è ..".

I work in France and use characters with accent marks. I have notified Prosoft Engineering of the problem, but have not yet received an answer.

If you've seen this problem, please let us know.

NetWare IP for Mac OS X client: SLPDA.nlm incompatibility

August 8, 2002
Randall York

Caveat: In order for the IP client to work, the Novell servers can NOT be running SLPDA.nlm. I am able to log in, but cannot mount any drives. This is noted by ProSoft, but there is no work around. I am told by my NetWare Administrator that SLPDA is necessary and cannot be taken off.

August 9, 2002
Jason Froikin

In my previous job, part of my responsibilities was to take care of the NetWare Server, and because it got some heavy use, to pare the loaded NLM's down to the minimum.

I just thought I would mention that I never used SLPDA.NLM, and never needed it. The NetWare admin who claims to require it may not be knowledgeble enough to remove it.

August 9, 2002
Richard Jenkins

My netware admin didn't seem surprised by this: We run the SLPDA.nlm on our DS servers, but nobody mounts those drives. Users mount drives on the user servers, not the directory services and top-of-tree servers.

August 21, 2002
Mike Maday

On our testing with this new client, SLPDA.NLM cannot be used under any conditions to have hope for mounting Mac volumes. Unfortunately, it is crucial to a NetWare IP-only network, so removing it on servers that need this running is not an option in many cases. On small networks and on those where routers allow multicasts to pass through, SLPDA isn't needed---broadcasting will take care of things. This usually isn't the case on many networks, especially larger ones.

Hopefully they'll fix this sooner rather than later as it is a show-stopper for us.

Prosoft Mac OS X NetWare client problem with resource forks

August 22, 2002
Alex Kiresuk

I have recently purchased a copy of the Prosoft Engineering OS X client and I have some information which is important to pass on to others via After installation I was able to access the Novell network however all the icons were generic, as if I was viewing them from a PC. After further investigation it appears that none of the resource fork is accessible via the Prosoft client. I read all the documentation and the FAQ online and could not find any mention of problems with resource forks. This is a critical issue for us as we use DNA Strider which requires the resource fork to open its files- even after launching Strider and selecting the file manually. I knew that these files had resource fork as the OS 9 IPX client displays the correct icon and opens with the appropriate application. I further tested the ability to access the resource fork with the ditto terminal function with either an AppleTalk connection or a OS X Prosoft connection. This confirmed that the OS X client had no access to the resource fork. I sent an e-mail to them and have received a response which acknowledges the lack of 'Mac name space support' or resource forks. It is planned to be added in the time frame of 1-2 months. I was disappointed with the lack of 'name space support' as I believe a Mac client should have access to both parts of a Macintosh file system by default or list this limitation.

The response from Prosoft Engineering Support;


The resource fork thing (Mac Name Space support) is intended to be added. I'm not sure how long this will be, but it looks to me like about a month and a half to two months, but since we are listening to engineers, it could be slightly longer. When that work starts depends on where engineering places it in priorities. I think I have been successful in convincing the engineering lead to put this at the top.


David Neil
Support Manager

Prosoft Client for NetWare 1.1 (TCP/IP)

December 10, 2002
Mike Maday

I downloaded the most recent Prosoft client for NetWare (version 1.1) in response to the announcement at and decided to give this client one more try. The past versions have been quite problematic and not worth much, to say the least.

This latest version has been rock-solid in the testing phases! No core dumps, no system hangs, no need to reinstall the client multiple times. It worked as advertised on the first install!

This is really a huge plus for us since this native client supports long file names, (RSA) encrypted logins, and there aren't any of the annoying ".DS_Store" files left all over the file system! (Do any other file servers or clients offer this??) Performance is on par with the Novell's NFAP software -- which is top-notch. Even logging in to our NetWare servers through the internet using a wireless home network and Mac OS 10.2.2 with this client was reliable and effortless. And I was able to browse for NetWare server resources after logging-in over the internet, too!

I'm quite impressed with the overall quality and performance of this client, especially considering past IP Client efforts haven't lived up to their billing. This one has.

Reader raves on Prosoft NetWare Client 1.1.2 for Mac OS X.

January 24, 2003
Michael Campbell has good things to say about Prosoft Engineering's new NetWare Client for Mac OS X 1.1.2, which we reported on January 8. (The new version allows users to make aliases of NetWare volumes and improves browsing of networks.) Campbell says:

I just purchased the latest client from Prosoft for X 1.1.2 and I must say that I am impressed, browsing now works, password expire now works which was an issue on the old client. We have a mixed NT and Novell 5.1 and when the login password expired Mac users would not get a warning, however with 1.1.2 when the password expires it informs you.

A brilliant client and well worth the price.

SSL Authentication for Mac browsers on Novell networks.

March 6, 2003
Sandy Bizjak told us about Novell Technical Information Document 2965091, which describes a patch that enables Mac web browsers to use SSL authentication on Novell networks. Bizjak reports:

The patch is Proxy.nlm v3.71e and a minor change to Sys:Etc\Proxy\Proxy.cfg.

I've just installed it on BorderManager 3.7 SP2 (on NetWare 6 SP2) and tested it with Internet Explorer 5.2.2 (on Mac OS X 10.2.4).

It worked OK, only problem is an IE warning about an untrusted certificate (now if only I knew how to tell IE for Mac to trust my Certificate Authority which is used to create certificates for BM).

Novell RConsoleJ for Mac OS X.

March 7, 2003|
John Endahl reports a port of Novell's RConsoleJ for Mac OS X:

Jeffrey Sessler of Scripps College has successfully ported Novell's RConJ utility for remote access to the console of a Novell server to Mac OS X. Those that frequent will recognize his name. At any rate, here is his post about the utility, and the link to the download.
For those of you out there who would rather administer your NetWare boxes from Apple's Mac OS X, I've managed to get Novell's Java-based remote server console "RConsoleJ" running on Mac OS X. I've only tested it on 10.2.2-10.2.4 but it should run on any version that supports Java 1.3.1.

I tested RConsoleJ OS X against my NetWare 6 and 5.1 servers with perfect results. You can download a Disk image w/ readme from the following URL. The package is about 5.5 MB.

For those of you interested in running ConsoleOne on Mac OS X... I have succeeded in getting it to run, load snapins, etc. but without the support of an underlying client it is not of much use. I'm going to take a look at the Linux/Unix versions to see if they are more client-independent.

Many thanks to Jeff for making this available to those of us in Novell shops!

Cross-platform problems with Now Up-to-Date on NetWare

March 7, 2003
Blake McCormick

My department switched from Macs to Compaqs running Windows 2000 5.00.2195 Service Pack 3 with Ethernet to a Novell NetWare 5.1 Server where we store many separate calendars for different projects. We are not using a Public Events Server computer or any of those features.

We were very happy to learn of Now Up-To-Date 4.5 for Windows being released, as that was our previous Mac calendaring solution. Some of our users still have Macs and we were happy to see this cross-platform solution. It's not going very well.


Mac-to-Windows and Windows-to-Mac leaves fonts really messed up. Even Windows-to-Window, fonts get screwy. It's almost as though Windows says, "Use the 11th font in the list" rather than "Use Arial Narrow".


On the Mac side, after working on a calendar for a while, we will suffer a Disk Access error and lose changes and be crashed out of the program.

On the Mac side, if you open a calendar then fix the fonts and then switch to a month with more than one or two events, it will crash.


Many times, if you open and revise a calendar on a Mac started on Windows, when you go to print it as a PDF, the fonts will go insane and print one large letter per day on the schedule.

If you open a PDF on Windows created on a Mac and then move to the next page, it will crash Acrobat.

Regardless of the event font size selection you make, when making a PDF in Windows, the event fonts goes down to about 6 point type. This was happening on four out of five Windows machines. Yesterday, the 5th one started having the problem.

We now have to do this to make a usable PDF and integrate it into our workflow.

  1. Finalize the schedule on your Windows machine, save it, close it.
  2. Go to the Mac, locate the schedule on the server.
  3. Drag the file to the Mac desktop, which will create a copy.
  4. double-click the copy to open.
  5. "Save As" to the desktop using the shortest filename you can (for example: Exit 9 schedule 0.90 should be something like "E9 090 Mac")
  6. Close the original file, open the copy you just made.
  7. Under Define select Calendar Layouts. You'll have to set all the fonts. I use Times New Roman for the first thing and Arial Narrow on all the others. Set banners to small. OK and Save. You're ready to Print.
  8. Under File, select Print. On the window, check out the drop-down menu to the left (it will say "Copies and Pages") and select "Now Up To Date". This is where you will set your headers. The fonts will look strange on the headers window, but don't sweat it, they'll be OK.
  9. Once that's all set, click the "Save to PDF" button.
  10. Save the PDF to the desktop of the Mac, use a simple name, make sure to append the file extension (in our example, "E9 090 Mac.pdf").
  11. Move that PDF you just made up to the server.
  12. Go back to your PC, open the PDF you just moved to the server.
  13. Don't try to modify or flip pages at this point, Acrobat will crash. Immediately save the PDF file to the server with the correct name (in our example, "E9 03 pilot sched 090 030226.pdf")
  14. Now add your cover.

The support forums at Poweron Software don't seem to be reporting these problems. The responses via email have been somewhat lackadaisical. We have not yet initiated a fee support call yet.

I wondered if any of your users are reporting similar problems and if they have come up with any solutions.

The Macs are Mac OS X 10.2.4 and running the Prosoft OS X client to access the Novell server. One of the Macs is a 450 MHz G4 with 768 MB of memory. Another is a 867 MHz Silverhammer G4.

If you've seen this problem, please let us know .

Problems with Macs running on NetWare network

June 11, 2003
Vadim Gorelik reports three problems with Macs on a NetWare network:

We have a 50/50 Mac and PC environment running on NetWare network. As it goes, the PCs are virtually problem-free, but Macs present us with a load of issues. We are currently in the process of upgrading from NetWare 5 cluster 1.01 to NetWare 6 cluster 1.6 and I am wondering if anyone out there has encountered same/similar problems and what they did/do about it.

1) Blinking icon - when our Mac users mount any volume, once in a while, the mounted volume icon can blink and do one of three things:

(a) Just blink with no negative effect;
(b) If files are open, give an error message stating that Volume cannot be dismounted;
(c) Just loose the icon along with the volume

2) Slowness of the volumes - while working on Quark documents from the server, users may start experiencing slowness in file access and even directory contents redraws. The slowdown cannot always be confirmed by looking at the CPU utilization on the server and can only be fixed by rebooting either the server, or even the entire cluster

3) If user is working on a file and experiences a computer crash, after reboot the file appears to be locked (In use) and the only way it can be fixed is to reboot the server.

 GoToMyPC - Access Your PC from Anywhere
Control a PC from a Mac over the Internet

| Top of This Page (MacWindows NetWare report) |

Other MacWindows Departments

| Product Solutions | Reports and Tips | News Archives | Site Map |
MacWindows Home |

Serving the cross-platform community since November 15, 1997.
This site created and maintained by
Copyright 2006-2007 John Rizzo. All rights reserved.