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

Where are SCANPST.EXE and/or SCANOST.EXE?

I sometimes have to deal with customer computers whose Outlook PST or OST files have become corrupted. Very often the fix is to run SCANPST.EXE on the offending PST/OST file. However, every time I go to do this I forget where the two executable files are. Here is where they are on a Vista machine running Office 2007: C:\Program Files\Microsoft Office\Office12 I hope this helps.

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

Logon Scripts in Group Policy not running

Problem Was having difficulty with a logon script I had created and was deploying to users via Group Policy. The script was to customise printer settings for certain users. But it just wasn't running when the users would logon to their PCs. The GPO was applying properly, and I could run the script manually without issue. Cause It turns out that it was happening because, by default, logon scripts don't run for 5 mins after logon occurs on a Windows client PC. Solution This can be adjusted by setting the "Configure Logon Script Delay policy" to "Enabled" and then configuring a better delay. Note: if this policy is set to disabled or not configured, the default delay of 5 mins will apply. I initially set this delay to "0" but found that wasn't successful. Perhaps the script needed a small delay. So I set it to "1" (1 minute) and it worked nicely. I must also note that during the troubleshooting process, I read many recommendations to e...

Artifact Weblog

Search This Blog