Mac OS X 10.4.2 (#8): More on FireWire drives unmounting; Ethernet connectivity problems: Make sure DHCP is selected; more

CNET staff

Sept. 2, 2009 11:51 a.m. PT

5 min read

More on FireWire drives spontaneously mounting Users continue to report issues with FireWire drives spontaneously unmounting. We previously noted that this issue primarily affects RAID configurations, or drives with faulty external power supplies. However, we've now received reports of some drives without power supplies (drawing power from the FireWire bus) that exhibit the same problem.

The problem seems especially pronounced when copying large chunks of data.

MacFixIt reader Sven Merckens writes:

"The error with the FireWire-Drives occurs also with external 2.5"-FireWire-Drives without separate power supply. I have this problem with a SaroTech Pocket Hard Disk Drive. There is a 80GB 5400rpm 8MB Cache Samsung Drive installed.

"While copying files to this drive (6-7MB is ok, more data results in an error) the drive is disconnected, an '-36'-error is shown or a KernelPanic occurs.

"I tried the drive on the FireWire-port of an 20" Cinema-Display (DVI) and also directly at the Front-FW-Port of a G5 Dual 1.8 (Revision A)."

Sometimes these issues can be resolved by switching FireWire ports or using an externally powered FireWire hub. Some bus-powered drives do not draw adequate power from the front FireWire port on Power Mac G5s, or the FireWire ports of Apple Displays.

Ethernet connectivity problems: Make sure DHCP is selected We continue to receive reports of lost Ethernet-based network connectivity under Mac OS X 10.4.2.

MacFixIt reader Gred Lawhorn writes:

"Ethernet failed on my iMac 17" - I assumed that the port had failed, and installed an Airport Extreme Card. In my case, the iMac never even recognizes that the ethernet cable has been plugged in."

In some cases, Mac OS X 10.4.2 apparently changes network settings to a configuration other than DHCP for network environments that require it, requiring the user to manually change the setting for any active TCP/IP location back to DHCP.

To do this, open the Network pane of System Preferences, select the appropriate Ethernet port or other active network connection, and select "Configure."

Click on the TCP/IP tab, and select "Using DHCP" next to the "Configure IPv4" menu selection.

Jack Rodgers is one reader who had success with this workaround:

"I experienced a similar problem and found that opening the Network preference pane and resetting each of the TCP/IP Location options, where appropriate, to DHCP solved the problem.

AirPort issues We continue to cover issues with AirPort connectivity after applying the Mac OS X 10.4.2 updater (or, in some cases, the AirPort 4.2 updater).

MacFixIt reader Jerry D reports that, in his case, selecting "Keep looking for recent networks" in the Network pane of System Preferences resolved his inability to connect to local networks.

Jerry writes:

I experienced a consistent problem in that every time I started up or restarted "I had to go into Airport Utility and run through set up each time. After fighting this for 2 or 3 weeks and futzing with settings over and over, I hit on a setting that cured this (maybe everybody already knows to check this setting, but I didn't) - In Network Preference, behind the Options Button - I had to select 'Keep looking for recent networks' under 'If no recent networks are found' - That fixed this issue."

Mail.app: More on problems with SMTP servers Users continue to note significant issues with ability to send and receive mail, as well as overall sluggish performance from Mail.app 2.0.2 -- the new release included with Mac OS X 10.4.2.

MacFixIt reader Cheryl Fuller writes:

"Count me as another person with ongoing problems with Mail since upgrading to 10.4.2 -- this after never having had problems with Mail before. It takes forever to open with long periods of 'application not responding' showing. Mailbox will show as empty when opened, then after a long delay the mail in it will show. Both IMAP and POP accounts are showing these issues. I am seriously considering downgrading to 10.4.1."

Randy Smith adds:

"I thought I had fixed my problem with Comcast and Mail.app but that was not the case. It seems that all of my Comcast mail accounts will not send any mail. I can receive mail just fine but when sending I am constantly asked for my password even though all my information is correctly entered and had been working at least up to the 10.4.1 update. The only way I can send email is to use my .Mac account which works fine.

More on malfunctioning network adapters -- ISDN modems A number of readers report loss of network adapter connectivity under Mac OS X 10.4.2 -- particularly with some older ISDN modems.

Wendy Vaan Der Drift writes:

"I have an ISDN connection via a NT1 Plus II DVO MODEM, after updating to 10.4.2 my modem connection disappeared. Kept getting error message that the Modem could not be found. I made sure the modem script was in the modem scripts folder, but to no avail. Tried rebooting, to no avail. Tried zapping pram, repairing permissions all to no avail. Ended up reverting to 10.4.1. When I did this the modem was recognized and all started working again. Tried reinstalling the 10.4.2 combo installer, but the same thing happened, not recognizing the modem script. So I had to again revert to 10.4.1. Any suggestions or people with similar problems would be appreciated."

Similar issue? Please let us know.

Previous coverage:

Resources

let us know

Mac OS X 10.4.2 (#7): Loss...

Mac OS X 10.4.2 (#6): Slee...

Mac OS X 10.4.2 (#5): Slee...

Mac OS X 10.4.2 (#4): More...

Mac OS X 10.4.2 (#3): More...

Mac OS X 10.4.2 (#2): Comm...

Apple releases Mac OS X 10.4.2, Mac OS X 10.4.2 Server [Download Links, Release Notes]