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

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

Re-arm ESXI Evaluation License

Needed to get a little more time out of my ESXI trial so that I could migrate it to Hyper-V. This pair of commands came in very handy and gave another 60 days: rm -f /etc/vmware/vmware.lic /etc/vmware/license.cfg reboot To use them, you need to: Put your ESXI server into Maintenance Mode Enable Secure Shell access (SSH) Enable Console Access Then ssh to the server (in Windows 11 you can just type ssh username@serveripaddress and then enter password) Otherwise, you could use something like PuTTY ( https://www.putty.org/ ) Hope this helps.

Turn off "BitLocker waiting for activation"

This can be a pain when attempting to "sysprep" a PC's storage drive (usually the C: drive) or take an image of it using something like Acronis SnapDeploy. In such cases, the software will complain about this BitLocker status. I keep forgetting about this every time I go to take an image! It isn't immediately obvious how to get around the issue... do you go for "Turn on BitLocker" and then turn if off when it has finished encrypting the drive? Well you probably could if you had the time, but there's an easier way. Using the "manage-bde" tool via an administrative command line gives lots more options, and allows this to be turned off. Tip: handy way to open an admin command line is to hit W + R, then type "cmd" and then hit CRTL + Shift + Enter. Typing "manage-bde -status" will show you some more detail, but the command you need is: manage-bde -off c: This may take some time, depending on how much of the drive has already...

Artifact Weblog

Search This Blog