CNET también está disponible en español.

Ir a español

Don't show this again


Mac OS X 10.3.3 (#6): Connecting to Windows shares - fix; Server connection consistency improved; more

Mac OS X 10.3.3 (#6): Connecting to Windows shares - fix; Server connection consistency improved; more

Connecting to Windows shares - fix Several users have been receiving the message "The Alias YOURSERVER could not be opened because the original item cannot be found" when trying to connect from a Mac running running Mac OS X 10.3.3 to Windows systems via the Finder.

MacFixIt reader Peter Monahan has found what appears to be a fix:

"Your Windows XP or Windows 2000 Computer must have at least One Shared Folder. Sharing only the Drive is not adequate in 10.3.3 If you do not have a shared folder (directory) then you will receive the "original item cannot be found" error when you attempt to connect from a Mac.
  • Create a shared folder and double-check the Windows security privileges.
  • If you want to share an entire Drive on a Windows XP or 2000 Computer, the share name must be Eight Characters or less (i.e. C_PETER or C_DRIVE) or you will not be able to view it or select it from the Finder drop down menu.

"In some cases you may need to delete the Windows Share and then establish a new share if you connect but can't see the contents of a drive. Once done and if you still have connectivity problems, either Restart the MAC, or delete the cached information by using the finder and selecting GO>>FOLDER and then type /var and hit enter. Then look in the "automount" folder and delete the folder called "network".

"Aliases now work as a result. Username and Password are now stored in Keychain. We can connect from finder in 10.3.3 to Windows Computers (as long as there is at least one shared folder). We can select aliases to load at start-up under System Preferences>>Accounts."

Server connection consistency improved A TidBITS article notes that Mac OS X 10.3.3 resolves some of the inconsistencies between the "Connect to Server" and "Network Browse" options outlined in Apple Knowledge Base article #107804 (which may now need to be updated).

"Mounting a server via Network browsing is now practically identical to mounting one though the Connect to Server dialog. A Network browser-mounted volume appears on the Desktop and in the sidebar of Finder windows; it is listed in the hidden /Volumes directory (use Go to Folder in the Finder's Go menu to see it); you can store the password necessary to mount it in your Keychain; and you can dismount it by dragging it to the Eject icon in the Dock, Control-clicking it and choosing Eject, or clicking its Eject button in the sidebar. Along with those improvements, you can now see Samba (Windows-style) workgroups in the Network browser."

We previously noted a difference in speed between Connect to Server and Network Browse server connections, though we have not yet been able to determine if the margin has closed in Mac OS X 10.3.3.

FireWire problems In addition to problems mounting FireWire drives reported yesterday, several readers are flagging other miscellaneous issues with FireWire connected devices.

One of the most common problems, and one that has been noted with previous Mac OS X updates, is a faulty update (to Mac OS X 10.3.3) process when FireWire devices are connected. Simply disconnecting offending peripherals usually allows installation to continue. MacFixIt reader Terry Freedman writes:

"Attempting to update via the Combo Upgrader from 10.3.2 to 10.3.3 on a G4 tower kept hanging. Unplugging the firewire external drive eliminated the problem."

iTunes not seeing iPod Stephen Northcott reports a problem with his iPod not being visible to iTunes after the Mac OS X 10.3.3 update, for which we are seeking confirmation. "Since updating to Mac OS X 10.3.3 my iPod will mount correctly and be useable as a Firewire drive but will not be seen by iTunes.

"Plug the ipod in and iTunes starts automatically as usual. Indeed it launches iTunes each time I restart the machine with an iPod connected. But the iPod will not appear in iTunes."

Remote Desktop connection Jason Fleetwood-Boldt and a handful of other readers are reporting that after upgrading to Mac OS X Server 10.3.3 (from Server 10.3.2), they are no longer able to access my server via Apple Remote Desktop.

If you are having a similar issue, please let us know.

More on new Lexar drivers We previously reported that Lexar was investigating an incompatibility between their flash memory devices and Mac OS X 10.3.3. We've now received word that an update is imminent. A Lexar technical support representative writes:

"We are testing the drivers for jumpshot on Mac OS X 10.3.3. Once it is completed, we will post the information our website. We will also inform you about this."

GoLive 6.0.1 required for Mac OS X 10.3.3 Some users are reporting that an update to Adobe GoLive 6.0.1 is required for use with Mac OS X 10.3.3. Cliff Mould writes:

"After updating to 10.3.3, Adobe GoLive 6.0 started crashing - mainly when changing a window - source view to layout view, or into a javascript window. I then updated GoLive to 6.0.1 and the problem so far appear to have been fixed."

More on Dock problems Yesterday we reported problems with some Dock icons losing their link to their original application. We've since received reports of a additional Dock irregularities since updating to Mac OS X 10.3.3:

Stephen Zilber writes "On restart or login, all dock icons of files/folders residing on an external firewire drive come up as grey question marks (those on the internal drive are fine). Simply right clicking on the question icons (without selecting "show in finder") brings them back to normal. In addition, icons for Mail, iChat AV, and Address book keep being added to the dock - even though I do not use any of them."

Evans Glausier adds "I too have experienced problems with gray question mark since installation of 10.3.3. I experience the problem with Quicken 2004 and Splash ID. It seems to occur every 2-3 days after I delete the old icon and reinstall a new icon into the dock."

Deep sleep We're beginning to investigate some issues with deep sleep that have cropped up after updating to Mac OS X 10.3.3. Marc Rosete writes:

"After updating to 10.3.3, just having the USB hub plugged in to the computer will not allow my computer to deep sleep, even if no devices are attached to the hub.  What?s worse, is when I attempt to sleep the computer (either via the Apple menu, the power button, or the radio button on the login screen), the cursor will disappear (the monitor may or may not go to sleep) and the computer will ?nap? (fans still running), but I will not be able to ?wake? the computer up.  Only solution is to reboot via the reset button.  My keyboard is connected directly to the computer and the mouse to the keyboard.  The hub is connected to the computer.  Same behavior if I switch the ports the keyboard and hub are connected."

Another reader is having problems with automatic sleep: "Since updating from 10.3.2 to 10.3.3, the computer will no longer go to sleep automatically, per the settings in the 'Energy Saver' control panel (the disks and fans continue to operate). I can put the computer to sleep manually, and wake it up without any problem whatsoever, and the display (Apple 17" Studio Display LCD) will sleep just fine (using the time specified in the Energy Saver control panel). The only problem seems to be going to sleep automatically."


  • article
  • #107804
  • difference
  • let us know
  • More from Late-Breakers