Skip to main content

AFP Problems with Mac OS X Tiger Update 10.4.11

I recently installed a Synology DS209 NAS in a customer’s site and was very happy with its level of performance and ease of setup.  Using SMB/CIFS I was getting about 40MB/s copying a file from it to my MacBook running Windows 7 under Boot Camp.  That is seriously fast!  My D-Link DNS-323 manages about 12MB/s and a 512GB Apple Time Capsule I’m currently playing with struggles along at about 7MB/s.

Things were a bit slower over AFP which seems to be fairly much to be expected.  One Mac running Leopard was fine, another running Tiger 10.4.5 was also fine.  However, one of the customer’s machines was giving awful trouble.  This old iMac G5 had been updated some time back with 10.4.11.  The shared folders would mount but you could barely use the share for a second before it ground to a halt and the Finder became unresponsive and had to be Relaunched.

I tried everything I could think of… updating firmware on the NAS, changing the network switch, playing with TCP/IP and AppleTalk settings, doing an Archive and Install on the iMac and installing all the updates.  All to no avail.  The other Mac in the company running Tiger was fine, why not this one?  Eventually, after a day of fruitless work it struck me: the Mac that was working fine was on 10.4.5, the troublesome iMac was on 10.4.11.  I did an Archive and Install on the iMac but didn’t install the Mac OS updates… all was fine!  I had to put on 10.4.8 for Illustrator CS3 to work properly but this update didn’t cause any problems.  Whew!

So, in conclusion, I can say that if you have an old iMac G5 running Tiger and you want to have functional AFP performance DO NOT INSTALL 10.4.11.  It will break AFP.  Perhaps it was an update between 10.4.8 and 10.4.11, who knows?  However, when you re-install Apple Update will prompt you to update to 10.4.11.  Don’t do it!

Comments

Post a Comment

Popular posts from this blog

Resolve WSUS Server issue that gives "Cannot save configuration because the server is still processing"

This is a pretty infuriating error and can sometimes crop up as a result of running a "wsusutil reset" command. First of all, give the server some time, and then a bit more...  but you've probably already done this. These steps may help to resolve the situation: - Install Microsoft SQL Management Studio (free download) - Run SQL Management Studio and start to connect to the WSUS database - Enter this in the "Server Name" box:  \\.\pipe\MICROSOFT##WID\tsql\query - Expand the "Databases" tree - Right-click on "SUSDB" and choose "New Query" - Paste this query in:     UPDATE tbSingletonData     SET ResetStateMachineNeeded = 0 - You should see a message like "1 row affected", which is good - Quit SQL Management Studio - Open "Services" and restart the "WSUS Service" - Now, open WSUS
Post a Comment
Read more

Evolution MK-249C MIDI Keyboard Mac OS X Problem

Mac OS X generally seems capable of dealing with just about anything you can throw at it. However upon connecting my trusty Evolution MK-249C MIDI keyboard up to my 2nd generation MacBook it steadfastly refused to play ball. This keyboard has always been instantly recognised by Windows XP and so it was surprising to encounter this. The M-Audio website (M-Audio took over Evolution it appears) offered no real assistance. There was no driver available for Mac OS X 10.4.9 as the keyboard is supposed to be "Class Compliant" which apparently means it doesn't need one... strange. Eventually after consulting some forums I found the fix. The problem seems to be related to Mac OS on the Intel MacBooks. There is a patch on the M-Audio site but only for MacOS 10.1.5. This must be downloaded and installed. Here is the link: http://www.m-audio.com/index.php?do=support.drivers&f=596 Upon restarting the OS the keyboard was recognised by Mac OS and GarageBand had no trouble tal...
11 comments
Read more

Jamf Pro DEP Enrollment Sync failed: Communication error. Awaiting next sync

 This error catches me out every so often when a customer of mine gets new iPads and I have to enrol them.  It's often been some time since I've last done this job and sometimes the MDM Server token needs to be refreshed (for want of a better term) before sync can re-commence between Apple School Manager and the customer's MDM (in this case Jamf Pro). Here are the list of steps to take: Log in to Apple School Manager (ASM) in one browser tab, and your MDM in another tab. In ASM, click your account name on the bottom left, and click "Preferences". Under "Device Management Services" click on your MDM service (Jamf Pro in my case). Click "Download Token" and allow the p7m file to download. In your MDM service, you'll need to upload the p7m file into its "Server token file" area. In Jamf Pro, click into "Settings" and then go into "Automated device enrollment", which is in the "Global Management" area. Cl...
Post a Comment
Read more