Access Your Mac® or PC from Anywhere

Access Your MacĀ® or PC from Anywhere

Mac OS X 10.5 Leopard Cross-platform Issues

Reports and Tips regarding working with Mac OS X 10.5 and Windows

72 Hour Apple Black Friday Sale

Updated July 2, 2010


On This Page:

72 Hour Apple Black Friday Sale

GoToMyPC - MyPC is on my iPhone.


If you’re using Leopard about any problems or tips.

Leopard's cross-platform features

The new OS, Apple's first in 2 1/2 years, includes a (non-beta) release version of Boot Camp, called Boot Camp 2.0, for booting Macs with Windows. Although there are some improvements in configuring and using networking, Leopard doesn't add major new Windows compatibility features. There are, however, a number of incremental improvements in cross-platform usability, configuration, and functionality. Click here for a list and description of the improvements, changes, and new cross-platform features in Leopard.

NOTE: For reports about Boot Camp, see our Boot Camp in Leopard Tips and Reports page.

Version History

Leopard client/server 10.5.8 update improves AFP, security

Monday, August 10, 2009

On Thurdsay, Apple released the Mac OS X 10.5.8 update and the Mac OS X Server 10.5.8 update, which include stability improvements as well as the latest security updates. The client and server updates list improved reliability for AFP file sharing. Apple said that the client update improves compatibility with Managed Client, a feature enables Mac OS X Leopard to control client preferences. Other server improvements include more consistent VPN throughput regardless of load, and better reliability in propagating file system permissions.

If you've used this update on the client or server if it fixed or caused any problems.

Leopard 10.5.7 client update fixes AD binding problem, AFP server search bug

Wednesday, May 13, 2009

The Mac OS X 10.5.7 update that Apple released yesterday fixes a number of bugs, two of which we have been covering. One is the problem of Leopard Macs losing Active Directory binding. The other a bug with searching AFP server volumes. Both problems were caused by changes made in the Mac OS X 10.5.6 update... Read entire story here

Mac OS X Server 10.5.7 addesses minor issues

Wednesday, May 13, 2009

Yesterday, Apple released Mac OS X Server 10.5.7, an update that fixes a number of small bugs and issues. A partial list of these fixes:

  • Fixes an AFP file server problem with viewing nested sharepoints. ?If you mount an AFP volume that contains another sharepoint, the nested sharepoint will now be visible.?
  • Addresses a delay in seeing Finder label changes made by another user to a file located on an AFP volume. Such changes will now be immediately visible to other users.
  • Administrators can now uses Server Preferences to remove sharepoints.
  • Improves Directory Services reliability when promoting an Open Directory replica to Open Directory master.
  • Improved logging and log rotation by Mail service processes.
  • The Mail service /var/amavis/amavisd.pid file is now cleaned up on relaunch if the Mail service unexpectedly quits.
  • Improved wiki editing in the wiki service

if the OS X Server 10.5.7 update fixes or causes problems for you.

Leopard 10.5.6 addresses bugs, performance, security

Wednesday, December 17, 2008

Monday Apple released Mac OS X 10.5.6, an update to its Leopard operating system that fixes a number of problems, as well as enhances support and plugs security holes.

Apple had one warning about accessing Mac-based AFP file servers:

If you are using Mac OS X 10.5.6 (client) to connect to a Mac OS X Server 10.4-based server, it is strongly recommended that you update the server to Mac OS X Server version 10.4.11.

Apple also said that the update improves compatibility with smart cards such as the U.S. Department of Defense Common Access Card (CAC), which is sometimes used for access to Active Directory (enabled by Thursby's ADmitMac CAC and Centrify's DirectControl ).

One reader reported that the update fixed a file sharing problem that we had previously reported with 10.5.x. However, some users at the Apple Discussion forums are reporting problems with installation of the update.

If the 10.5.6 update fixes (or causes) any cross-platform problems with Leopard (particularly with file sharing)

Apple Leopard 10.5.4 fixes Adobe server issue, improves VPN

Thursday, July 3, 2008

This week Apple released the Mac OS X 10.5.4 and Mac OS X Server 10.5.4 updates. Although a relatively minor update, 10.5.4 fixes a problem with saving and reopening Adobe Creative Suite 3 files on a file server, according to Apple. We've previously reported that the issue can lead to corruption of the Adobe file.

Apple also said that the update improves reliability of the built-in L2TP VPN client and that 10.5.4 "addresses an issue that may result in a partially installed X11 application."

Apple also released Mac OS X Server 10.5.4 update. It improves the reliability of Directory Services, according to Apple.

If you've tried the Mac OS X 10.5.4 how it affects these and other Leopard problems.

Leopard 10.5.3 released, provides cross-platform bug fixes

Friday, May 30, 2008

On Wednesday, Apple released the Leopard Mac OS X 10.5.3 update. Apple's description of the fixes indicate that at least some of the cross-platform networking bugs that we have reported may have been fixed. Early reports from readers also indicate that the update does fix some of Leopard's problems.

Here are the Apple-listed fixes in 10.5.3 that may address problems we have reported, with links to the problem reports:

One reader confirmed the last item, that 10.5.3 fixes the issue of Safari crashing when accessing a Microsoft ISA proxy.

Two readers said that the update fixes the problem of copying files to a Windows server by leaving only 0-byte files on the server. However, one of the two readers said that file copy is very slow.

Another reader said that the 10.5.3 update fixed a problem with Parallels Desktop being unable to allocate memory.

whether or not the Leopard 10.5.3 update has an effect on you cross-platform problems.

Apple says Leopard 10.5.2 addresses AD bug, but other network problems not in bug fix list

Wednesday, February 13, 2008

On Monday, Apple released the Mac OS X 10.5.2 update and the Mac OS X Server 10.5.2 update. Among Apple's list of bug fixes are two cross-platform networking issues, involving Active Directory binding and accessing AFP network volumes. However, many of the widely reported Leopard cross-platform bugs, including problems with browsing and logging onto Windows servers, are not mentioned in Apple's list of fixes.

Apple said that the update fixes problems with binding to Active Domains, which was widely reported with 10.5.0 and 10.5.1. Apple also said that the 10.5.2 update fixes "a hanging issue that may occur when connecting to an AFP network volume." Third-party developer Group Logic has previoulsy reported that Leopard contained bugs in the AFP protocol.

There was one other cross-platform bug fix regarding accessing printers shared with Windows:

Resolves an issue with some printing options, such as landscape orientation, number of copies, two-sided printing, and so forth that may not have functioned with some printers shared by Microsoft Windows.

Missing from Apple's list of 10.5.2 update fixes are the problems related to browsing and/or logging on to Windows network shares, the most widely reported problems by MacWindows readers.

Apple also doesn't mention if the update fixes problems with virtual private networks and the issue of Safari crashing when accessing a Microsoft ISA proxy. Leopard Boot Camp problems are also not mentioned in the bug fix list.

Our first reader reports about 10.5.2 are mixed. whether Leopard 10.5.2 fixed any of these issues for you.

Apple ships Leopard 10.5.1 update. Friday, November 16, 2007 -- Apple has released Mac OS X 10.5.1, the first upgrade to the Leopard release of three weeks ago. Apple didn't list fixes for the problems readers have been reporting about file sharing, Active Directory, virtual private networks, or other issues. The closest the Apple web page came was this:

Addresses an issue in which Microsoft Windows shared folders may be read-only when connected via SMB.

One interesting change was with the firewall. Apple had been criticized by security experts because the "Block All" setting did not, in fact, block all connections. In 10.5.1 Apple didn't enable it to block all connections, but changed the name to "Allow Only essential services."

Leopard 10.5.0. Friday, October 26, 2007 -- Apple released Mac OS X 10.5 Leopard today at 6 pm. The new OS, Apple's first in 2 1/2 years, includes a (non-beta) release version of Boot Camp, called Boot Camp 2.0, for booting Macs with Windows. Although there are some improvements in configuring and using networking, Leopard doesn't add major new Windows compatibility features. There are, however, a number of incremental improvements in cross-platform usability, configuration, and functionality. Click here for a list and description of the improvements, changes, and new cross-platform features.

Other Leopard Info

Leopard Server’s wiki server can affect AD binding | Top of Page |

Monday, October 29, 2007

Apple tech article 306750 warns that when running Mac OS X Server 10.5 bound to Active Directory, using the Wiki Server can cause problems with users authenticating to Active Directory. Apple's solution is to set authentication for Wiki Server that comes with Leopard Server (wikid) to clear text. The article explains how to use Terminal to set Wiki Server authentication in clear text.

Apple explains why this is needed:

This is required because, by default, the wiki server uses CRAM-MD5 authentication, which is not supported by the Active Directory plugin.

Because sending clear text passwords is not secure, Apple recommends configuring the wiki server to use SSL.

Security analysts say Leopard firewall security weaker than Tiger's | Top of Page |

Wednesday, October 31, 2007

Security experts quoted in an eWeek story said that Leopard's firewall security holes that don’t exist in Tiger, the previous version of Mac OS X. The story quotes several researches who tested the new Mac OS X's built-in firewall.

One researcher discovered that Leopard's "block all incoming connections" setting does not in fact block all connections. He found that it allows several connections through the firewall, including ntpd (Network Time Protocol daemon) connections and NetBIOS name server connections.

Users do not have the option to tighten security by tweaking the configuration. As we've previously reported, Leopard has removed the configuration options that Tiger had, including blocking access to specific ports, restricting TCP or UDP access, or allowing only specific services, such as file sharing or FTP access. Users only have the "block all connections," choose applications to allow to connect, or allow all connections (turn the firewall off).

Another tester found some inconsistencies in the settings. He discovered that if file sharing was turned on, the "block all incoming connections" allowed other Macs to see the Mac, though not connect to it. This means that the "Block all" setting was allowing Bonjour broadcasts through the firewall.

Another noted concern was the fact that the Leopard upgrade installation deactivates the firewall by default, even if it was previously on. Tiger did not behave this way.

Leopard bug can delete data with file transfers

Wednesday, November 7, 2007

A number of sources around the Internet are reporting a bug in Leopard that deletes data when the OS is interrupted during a file move between volumes. If you are moving (but not copying) a file, group of files, or a folder between volumes and the connection stopped during the move, Leopard will delete the files/folder form the original volume as well as any copies. The move can occur between local drives or between local and network storage.

The bug has been reported by Macintouch, eWeek, and others. The workaround is to do a copy instead of a move, then delete the original.

Current news on the MacWindows home page.


Reader Reports and Tips

REPORTS ABOUT LEOPARD 10.5.0

Leopard problem mounting Win servers | Top of Page |

Monday, October 29, 2007

Stacy Rothwell reports a problem connecting Mac OS X 10.5 Leopard Macs to Windows servers. The problem occurs only when file sharing is turned on:

After a clean install of 10.5 on my Mac Pro, I was able to connect to my Win 2003 Server twice before it would just time out. Now it always tells me the server isn't responding. I can reach it just fine (under my account) from other Windows PCs and, in fact, if I run Parallels under 10.5 I can, indeed, get to the Win 2003 Server via Parallels.

The REALLY strange thing is in my home I have 5 Windows PCs and 2 Macs. One of the Windows PCs will automatically show up just fine under the new Finder but none of the others will. This Windows PC that shows up is no different than any other. It is on the same workgroup as all the others, etc.

It turns out if file sharing on the Mac is turned OFF, then all my Windows PCs will show up and connect just fine under SHARED in the Finder.

As soon as I turn on File Sharing, then it breaks. None of the Windows PCs will connect any more under their Windows names. Must go back to using IP addresses.

If you turn file sharing off and then REBOOT, it all works normally again.

More readers report Leopard not seeing Windows shares

Wednesday, October 31, 2007

A number of readers responded to Monday's report of problems mounting Windows shares with Leopard. Several readers reported that turning off file sharing allowed them to connect to Windows shares. For others, this didn't work.

Rob Groome:

Yes, I see this problem as well. By turning off Mac File Sharing, I can now see my Windows network and access shared files and printers. I wasted two days messing around with Windows IsDomainMaster and MaintainServerList registry properties with SOME success but the "ups" disappeared whenever a Windows machine was rebooted.

Suffice it to say, Mac OS Leopard is NOT ready for prime time when it comes to Windows SMB networking!

Gary Pownall:

Yes I have exactly the same issue and it's driving me mad!! How this got by Apple beggars belief.

Mark Gordon said that turning off file sharing did not work with his PCs running Windows Vista:

I have the exact same problem as Stacy Rothwell but the turning off file sharing does not make the other Vista machines show up under shared. My Leopard machine only sees one of my Windows Vista machines under shared on the sidebar although if I go to connect to server for any of the Vista machines I can connect. The Leopard machine under WINS is part of the same workgroup as the Vista machines.

Adam Bradford also had no success with turning off file sharing:

I also am having difficulty file sharing on my home network with OS X 10.5. All of the Windows based machines on 10.4 would come up in NETWORK and I could connect by typing in my username an password on those machines. On 10.5 I can't even seem to get the shared tab in Finder! I tried Enabling and Disabling File sharing but with no success.

If you've seen this problem with Leopard

More symptoms of Leopard Windows file sharing problems, and a suggestion

Friday, November 2, 2007

Readers continue to report problems with accessing Windows file shares in Leopard. While some confirmed the previously reported symptom of not seeing Windows shares, other readers reported new symptoms, including not being able to use Connect to Server. One reader can’t print to a PC printer, and another reported that file sharing simply stopped working after a few days. For another reader, the Windows shares appear and disappear randomly.

Erik Ableson figured out a way to connect:

I've had a few issues not being able to access Windows shares, but on investigation it appears to be specific to DFS shares. They mount correctly, but I am denied access to the shares. However, when I manually direct the connection to the underlying server share it works just fine, except that I have to authenticate (kerberos doesn't auto connect me).

Jason Dodd simply confirmed the problem:

I'm having the same issue with 10.5 not showing Windows shares. I can't figure out where to put workgroup info, either.

Elsewhere in today's news, several readers described how to enter the workgroup and other info. (Click here to read that article.) But while Shane Moore can enter the workgroup name, it doesn't get saved. He also gets login errors, but doesn't see the problems with Linux shares:

I am also experiencing issues accessing my Windows Shares after installing Leopard. I can access the shares via Parallels, but not from the base Leopard OS. Attempts at adding the workgroup under WINS fail (it never saves the information). Turning on/off local file sharing doesn't help either.

The Go menu's Connect to Server (smb://whatever) doesn't work, often giving me login errors regardless of what user/pass combination I use. I AM ABLE to connect to LINUX shares just fine. Only my Windows XP/2003 machines are inaccessible. No Vista machines are present on the network.

Harold can't edit shares or print to PC printer:

Sharing with a PC pre-Leopard was fine, but after the upgrade, I am having some troubles.

1. I can view the shared PC folders on the Mac, but it says I do not have privileges when I try to edit within the shared folder. (I never had this problem prior)

2. The printer connected to the PC that I share through the network is non-functional now. (It seems like the printer & fax setup is more confusing than before.)

Mark Owen is having better Windows connections with Leopard:

Previously, shares on Windows computers were unavailable in Tiger but after I upgraded to Leopard, they showed up immediately. I connected easily where before I would get error messages saying the alias was not available. Happily I'm not having Windows connectivity problems.

Earl Arnett started out with better file sharing with Leopard. Then it all stopped:

For the first few days, Leopard recognized the Windows computers on my home network in an even easier fashion than Tiger. So I thought, "Great!". Today, after no significant changes, suddenly Leopard does not acknowledge the network. Internet is OK, but the network is invisible, doesn't show in Finder and the Windows computers don't see the Mac. It's a mystery that doesn't offer any obvious solutions.

Mark Pouley also has a mystery, with Windows shares appearing and disappearing from the Mac's view at random:

I'm having a similar problem with Leopard and Windows machines. I have 3 Windows desktop and one Windows laptop machine in my house and I have Leopard installed on my iMac (20" Intel white edition).

When I installed Leopard none of the Windows machines showed in "shared" but I could connect to an external drive on one windows machine using the IP address. I thought I had a network problem and poked around without really changing anything.

About an hour after install, for no reason, the laptop appeared in the list (it is a new Sony running Vista) this was odd. A few minutes later, all the machines showed. While poking around to see how this worked (clicking on the drives, seeing if all shared volumes were accessible, etc) all of the machines "disappeared." Over the weekend the machines have appeared and disappeared without notice and without any clear clue as to what is causing this issue.

If you've seen any of this

Current news on the MacWindows home page.

Configuring Leopard for connecting to Win file servers | Top of Page |

Monday, October 29, 2007

Stacy Rothwell finds that Leopard's new method of connecting to Windows file servers has some holes in functionality:

In 10.4 when telling your Mac to work with Windows networking, there was a place you could specify the workgroup, and it just worked. I always got a NETWORK icon in the Finder and it ALWAYS connected no matter what workgroup a machine was on. It just worked.

Under Leopard, the network icon is gone and OS X will only show you machines that it can see. Otherwise you must go into CONNECT TO SERVER and type the silly SMB connection.

Also, I can no longer figure out where to set the default Windows workgroup and Windows PC name that was so easy to find in 10.4.

TIP: Configuring Leopard to see Windows file shares: WINS tab-> workgroup name

Friday, November 2, 2007

A couple of readers sent us instructions on enabling Leopard to see Windows file shares and where to enter the workgroup name.

Matt saw the previously reported file sharing problem and described the settings to fix it:

I can confirm this problem as well. However, in my case I solved it by going into the "advanced" options for System Preferences --> Network --> Ethernet. Under the WINS tab I entered the workgroup name for our PC network and the DNS server address. All PCs on that domain then appear under the "Shared" list.

Daniel Hoit also sent configuration info for accessing Windows shares, and disagreed with a previous reader about Leopard's file sharing:

Samba based services are updated to reflect revisions to the open source Samba project in Leopard, and are not a step backwards. The addition of packet signing alone is a huge and welcome addition.

As for the poster's complaints regarding WINS workgroup and Finder browsing, the options are still there in Leopard. You can configure the WINS information in System Preferences/Network/ Advanced/WINS section. Choose a workgroup, and choose a wins server if you have one on your network.

The sidebar also has an "All..." option that should be the equivalent of Tiger's "Network" browsing option in the Finder. In my experience, network browsing has always been a little iffy. Its almost always been more reliable to access SMB servers through a command-K connect to server dialog, and then bookmark the server for easier access later. YMMV, but in the least Leopard doesn't downgrade anything in the SMB services area.

If any of this configuration advice solved your Leopard file sharing problems

Current news on the MacWindows home page.

Reader verifies WINS fix for Leopard share browsing problems

Monday, August 25, 2008

Bryce Wray said that a previously published suggestion (above) works for clearing up Leopard browsing of network shares:

Thanks for the WINS fix for Leopard! The item on Nov. 2, 2007, re WINS settings worked like a charm for me. I'm running OS X 10.5.4.

Tips and workarounds for Leopard accessing Win file servers

Monday, November 5, 2007

Several readers wrote with workarounds for Mac OS X 10.5.0 problems accessing Windows files servers. Previously, we reported suggestions that turning off file sharing enabled Leopard to see Windows shares. Other readers offered other configuration changes.

Gregg Guarnera offered an explanation as to why turning off file sharing works, and offered a file sharing tweak that does the trick:

I was having this same problem after I installed Leopard. My Windows file shares would sometimes show up but not be accessible or would not show up at all. There seems to be a bug in Leopard where it has problems connecting to Samba (Windows) file shares if you are sharing your Mac files without using Samba. This is why turning off file sharing helps.

The solution is to go to System Preferences | Sharing and select "File Sharing". If you have file sharing turned on click on the "Options..." button and make sure the option "Share files and folders using SMB" is checked. Click Done. That should do it.

John Buchanan changed DHCP settings on his wireless router:

I updated to Leopard from Tiger yesterday. With Tiger I could easily connect to my Windows computer either via Network in Finder or via Connect to Server. After the Leopard upgrade I could no longer connect, similar to other users posting reports to macwindows.com.

None of the suggestions at MacWindows.com solved my problem. Then I started looking at the DHCP server settings on my Linksys WRT54G router, and saw that I had my fully qualified domain name in the Domain Name field...so I tried changing this to my Windows workgroup name, then renewed my DHCP lease on my MacBook Pro, and voila, there was my Windows workstation (WinXP SP2).

Shane Moore updated his previous report with this note on his success. He made changes to his passwords and fiddled with his wireless connection:

I was able to connect to my Windows machines finally.

1) Passwords can't have any special characters including "%,$,etc". Changing the passwords or escaping them before entering them into the smb:// password dialog helps.

2) I had to make a new location for my wireless connection. Automatic would not allow me to properly change my workgroup. Duplicating automatic and naming it something, then changing the workgroup allowed me to see all machines on the network without a WINS server. This was not extremely reliable though. The machines would randomly disappear/appear from Finder.

Note: See this article below for step-by-step instructions on how to do this.

Kevin Wheeler changed his firewall settings:

Like many of your readers, I "woke up" after installing Leopard to realize I couldn't access my shared Windows directories. On a hunch, I checked out my Firewall settings (Security > Firewall > Advanced) and turned "Enable Stealth Mode" off. Suddenly, there was a new entry for "SHARED" in my Finder pane and everything seemed fine again. I have no idea if this will be stable, as I just discovered this particular problem.

If you've tried any of these suggestions

Reader verifies AirPort workaround for Leopard file sharing

Tuesday, April 1, 2008

Allen O'Loughlin verified a suggestion for overcoming the a problem using Leopard to log onto a Windows server over AirPort:

I was able to connect to my Windows share after following Shane Moore's two-step process: 1.) Changed my password. 2.) Recreated my wireless connection.

More details on our Leopard Tips and Reports page.

TIP: Turn off IP6 on AirPort station for Leopard file browsing problems

Monday, April 7, 2008

David Josephs had a problem with Leopard browsing for files over an AirPort network. He tried some of the fixes on our Leopard Tips page, but found the solution not on the Mac, but the wireless router:

I changed the Samba file in Terminal tip but this did not work. There have been a lot of tips about turning off IPv6 on the remote Mac machine that did not work for me. What did work was when I turned off IPv6 on my router (changed from Node/Tunnel mode to local-link only on my AirPort Extreme router); all of the other computer shares (PCs and other Macs) immediately showed up in the SHARED section of the Finder. I can now see a Mac Mini, 2 Win XP and one Vista machine on the network now. I can fully browse the shares.

If you've tried this

TIP: Wireless router software for fixing Leopard problems mounting Win shares

Monday, April 28, 2008

David Kim had problems Leopard and file sharing over a wireless connection. He tried several of suggestions on our Leopard Tips and Reports page, and sent us a new one:

I've been reading this discussion on several occasions over the last few months. It is very helpful. Several of the fixes resulted in transient improvements. Most helpful was the delete/recreate location workaround.

However, the key fix for me (stable for 2 weeks now) has been to replace my router software. I had been running DD-WRT v23 and later v24RC6 (the worse offender) on a LinkSys WRT54GL WDS system (a popular choice).

I switched to the Tomato firmware and haven't had a single glitch since. It is a world of difference for both of my Macs. Also, this product is excellent in many other respects.

If you've seen a similar effect

Readers link Leopard's file sharing woes to firewall

Wednesday, December 5, 2007

Two readers discovered that they could enable get around Leopard's problems browsing Windows networks by setting the firewall to "Allow all incoming connections." This is not ideal for security, as it is similar in effect to turning the firewall off.

Wes Hsu reported his finding:

I didn't read through all of the suggestions, but after getting down to Kevin Wheeler's suggestion to turn off the firewall's "stealth mode," I decided to look there.

In my Firewall, "Enable Stealth Mode" was already turned off. Instead, I turned on "Allow all incoming connections". I then connected through Finder (cmd-K) using smb://windowsComputer/C$. I authenticated and I was in. I now have a SHARED category in my Finder with that machine listed. I now need to figure out the exact settings (ports, etc) so that I don't have to allow all incoming connections. But, I'll take it for now, as having access to my Windows machines is more important to me right now.

As a little background, File Sharing is OFF on my Mac so that suggestion didn't work for me.

Shane Palmer looked at the firewall log to verify that setting the firewall to "Allow all incoming connections" allows the user browse a Windows network in the Finder using Leopard:

I have already upgraded to Mac OS X 10.5.1 and it does not help.

I believe it is probably all related to the firewall. I turned on firewall logging (System Preferences>Security>Firewall). You must click on "Allow only essential services," then click the Advanced button. (This appears to be yet another bug since you can't click it if you have "Allow all incoming connections" selected. Some people may want to enable Stealth Mode without turning on the application firewall.) Next, check Enable Firewall Logging. Click the Open Log button. This opens the log in Console so you must switch back to System Preferences and click OK. When you now try to browse the Windows network you will start seeing a bunch of entries similar to the following:

Nov 26 17:34:49 COMPUTERNAME Firewall47: Deny nmbd data in from 10.10.X.X:138 uid = 0 proto=17

Nov 26 17:35:05: --- last message repeated 1 time -s

As soon as you switch the firewall back to "Allow all incoming connections" you will stop seeing any new nmbd entries in the firewall log.

This assumes that they have correctly set up their Windows networking info in System Preferences>Network>Ethernet (or whatever interface you use)>Advanced>WINS.

If you've manipulated Leopard's firewall settings to enable access to SMB shares

Turning off Stealth Mode fixes Leopard file sharing issue

Friday, June 5, 2009

Laura Smith verified a previously reported fix for problems with Mac OS X 10.5.x displaying network file shares. The fix was shutting off a Leopard advanced firewall setting called Stealth:

After working many hours on the problem of not seeing other computers on the network, in addition to having my Airport settings constantly reseting themselves, I found and followed Kevin Wheeler's suggestion and changed the firewall settings of "Enable Stealth Mode" to off. I could see the other computers on the network instantly. Thank you for your post Kevin!


Adding a location (turning off auto-location) to fix Leopard file sharing

Wednesday, December 5, 2007

Tom Neff verified a previous suggestion to fix his Leopard file sharing problem:

I had the reported problem - couldn't see Windows/SMB file shares. Tried various of the tips - nothing worked - Then I tried the tip about turning off Automatic location and adding a specific Location. All of a sudden the WINS Workgroup and NETBIOS name changes that had been failing to "take," took permanently, and from that moment I saw all shares

Reader confirms "turn off Automatic location" fix for Leopard browsing of Windows shares

Wednesday, December 12, 2007

Patrik Fredriksson of Gothenburg, Sweden verified a suggestion from last week to enable Leopard to browse for Windows shares. The suggestion was to turn off auto-location and add a location manually. Fredriksson said:

I can confirm that (at least for me) this works.

Previously, I could connect to shares fine, but they would disconnect without any reason "just like that". After speaking to Apple support, this was suggested and the drives have not disconnected since.

I have also added a WINS name manually that I use at work.


Tip: Turn off IPv6 to get Windows file sharing to work; previous password tip also verified

Monday, November 19, 2007

Christopher Ferrante found another workaround to Leopard problems with Windows file sharing:

By turning off IPv6 I was able to see all my Windows PC shares.

Ferrante didn't elaborate, but here's how to do this:

  1. Choose Apple > System Preferences, and then click Network.
  2. Select the network connection service from the list, and then click Advanced.
  3. Click TCP/IP.
  4. Click the Configure IPv6 pop-up menu and select Off.

If you've tried this if it worked for you.

Previous reader reports have suggested such things as turning File Sharing off or making various other configuration changes.

One of these previous suggestions involved removing certain characters from passwords. Simon Yates verified the password suggestion, and noted that the problem persists in 10.5.1:

I previously reported that I could not connect to any Windows shares with 10.5. After reading further at MacWindows, I read that passwords with special characters could be the problem. I removed the special character and was able to connect using a registered user. I still had to enter the password every time I restarted the machine.

With Leopard 10.5.1, special characters are still a problem, yet I no longer have to enter the password on restart.

After 15 hours with AppleCare, it is truly amazing that they recommended a complete reinstall and never once mentioned the password as a potential issue.

It is not a problem for Tiger at all. I run both 10.4.10 and 10.5.1. Tiger never had any trouble at all. Surprisingly, Mac is UNIX based, which recommends and supports special characters in the passwords.

Another reader fixes Leopard file sharing problem by turning off IPv6

Wednesday, December 5, 2007

Diego Cantalapiedra verified a previous suggestion of turning off IPv6 to enable browsing Windows shares in Leopard:

Turning off IPv6 works for me. After enabling SMB File sharing and turning off IPv6, I can now see and browse all the PCs at my institution.

Turning off IPv6 is just one of many very different (and strange) workarounds that readers have reported for enabling Leopard to browse and connect to SMB file shares. (See our Leopard Tips and Reports page for more.) This workaround may have something to do with an inconsistency in how Leopard uses IP in file sharing. Last month, we reported a Group Logic tech article that stated that "the [Leopard] sidebar also seems to default to using IPv4 addresses whereas the Connect to Server windows default to IPv6 addresses."

If turning of IPv6 works for you

Another reader verifies "turn off IPv6" fix for Leopard browsing of Windows shares

Wednesday, December 12, 2007

Ernesto Salcedo is another reader who could not browse Windows network shares after upgrading to Leopard. He verified a previously reported suggestion: "Turning off IPv6 worked for me!"

More reports that turning off IPv6 works for Leopard browsing of Windows shares

Monday, December 17, 2007

Two more readers reported success with turning off IPv6 to get file browsing to work in Leopard:

Brett Polakowski:

I used your hint, turned off IPv6 and I can now browse Windows 2003 shares via the mount that comes up in the sidebar. Previously, if I went to that mount point it would say "Connecting" for a moment then change to "Connection Failed." It's all much better now.

Ron McBeth:

After upgrading from Tiger to Leopard, I also lost the ability to see the various Window computers on our network. Your tip to turn off IPv6 worked for me.

However, another reader reported that this did not work for him, and recommended relaunching the Finder.

Reader's Leopard file sharing problem not fixed by turning off IPv6

Wednesday, December 19, 2007

Ron McBeth previously reported that turning off IPv6 fixed his Leopard Windows file sharing problem. He now says it didn't take:

I may have spoke too soon. It worked the day I tried it. I have had to restart since then (added the new Apple updates) and now it doesn't give me the Windows computers on our network.

Another reader turns off IPv6 to fix Leopard file sharing

Monday, January 7, 2008

Turning off IPv6 is one of the many workarounds that readers have reported for dealing with the problem of Leopard not seeing Windows shares. Although this doesn't work for everyone, it did work for Tom Kirby:

I had the problem of my Mac not finding Windows shared folder. The method listed of turning off IPv6 is what finally made my Leopard system see my XP machine's shared folder. I'd also changed some of the other things mentioned at MacWindows, but turned my firewall back on and the shared folder still shows up for now. Now on to solving access to the windows machine's printer!

Turning off IPv6 works for browsing Win files in Leopard 10.5.4

Monday, September 22, 2008

Ryan Lloyd said that turning off IPv6 in Leopard does indeed get around a problem and enables Leopard to see Windows shares on the network, this time in 10.5.4:

Just wanted to let you know this tip allowed me to see a machine on the Windows domain that I couldn't see previously. I could see about 100 machines on the domain, changing this setting on my Mac Book Pro, Leopard 10.5.4 actually did the trick!

Turning off IPv6 helps reader's Leopard browse for shares

Monday, September 29, 2008

F.G. Rios reports success with the previously reported tip about fixing Leopard's file browing problems by turning off IPv6:

I read this tip on your blog after having all of my shares disappear after installing 10.5.5. When I turned off IPV6 they all came back!

Note that some readers have reported that this didn't work for them. For most, however, there is no harm in trying it.


Reader agrees Leopard file sharing chokes on special password characters

Thursday, December 27, 2007

Lewis Parker verified previous reports (here and here) that removing certain characters from Windows file server passwords can clear up Leopard file sharing problems. According to these reports, password characters that were okay in Tiger no longer work in Leopard. Parker said:

I couldn't get to my shares from a Windows 2003 server after a recent password change. When trying to connect, the authentication dialog would pop up and after I entered the password the "Connecting to server..." message would just sit there and crank. It wouldn't fail but it wouldn't ever connect. I had to relaunch the Finder (through Force Quit) to get it to go away.

Sure enough, I had a percentage sign in the password that was causing the problem. No more special characters in passwords, and it works.

However, some other readers have reported that this tip has not helped them.

TIP: Another workaround for Leopard file sharing: turn off SMB Relay Attack

Wednesday, November 21, 2007

Neal Jackson offered another workaround for problems mounting Windows shares with Leopard:

I have found that my PC Firewall software allows Leopard unhindered SMB sharing by turning off SMB Relay Attack detection.

I'm no expert but I guess Leopard is using this networking protocol in a primitive manner that could render the network potentially vulnerable to SMB hijacking attack exploits.

If you've tried this suggestion

Reader feedback on firewall Leopard file sharing workarounds

Monday, December 17, 2007

A reader named Zeno said the firewall suggestion worked to enable Leopard to access file sharing, but the SMP tip did not:

Hello, I tried the suggestions for turning off the internal Firewall and the shared PC machines on our network immediately showed up. I also tried the enable SMP in the allow only essential services and this didn't work. I have a G4 Dual 1GHz running 10.5.1.

TIP: Manual IP, WINS config solves reader's Leopard file sharing problem

Wednesday, December 5, 2007

Nicholas Manzoli solved his Leopard file sharing problems by configuring IP and WINS manually:

Before upgrading to Leopard, I could see all PC's and network attached storage (NAS). Now, nada. I did see everything for a very short time (minutes) just after the upgrade, restarting for the first time. Same on four machines that I upgraded.

After a lot of frustration, I was able to fix my file sharing problem. I solved it by going into the "Advanced" options for System Preferences --> Network --> Ethernet and I changed the Configuration to 'Manual" then I entered the same IP address that was there when the configuration was automatic. I then went into the WINS configuration and entered my Workgroup name under NETBIOS (press enter) and selected the workgroup again in the next box.

I applied the changes and all of my PC's, NAS's etc just started showing up. Been up and running for about an hour and they are still there. I tried this on four machines (2 Intel Minis, a PowerBook G4, and a MacBook) and it worked on all. The laptops were a bit more work - had to create a new location and copy in all the details. Make sure the NetBIOS matches your workgroup name. It might take a few tries to make that stick (though I don't know why).

If you’ve tried this

Users can't see files inside shares

Monday, November 5, 2007

Some readers are reporting different symptoms of Leopard file sharing problems. Here are some more.

Kirk Rheinlander can't see inside network folders:

10.5 Leopard from a Powerbook G4 to a Win2003 server share point. The "connect to server" function works fine, giving me a mount point as specified (a blue disk icon on the desktop too), but none of the content of the directory is visible. A PC, same credentials, works fine, but my PB does not see any files. Get Info shows the volume as a SMB (NTFS) volume, with permissions reflecting read/write. However, attempts to create a folder or copy a file fail.

Tried renaming machine to a shorter name, turning sharing on/off/on, removing credentials from the keychain, even opening up permissions on the Windows directory - no success.

Also, my wireless connection seems to go away. Signal strength does not degrade, but all of a sudden, no connectivity. Shut down Airport card and restart it, and viola! It works.

Simon Yates also can't see items inside shares:

I can connect 10.5 to my Win2003 SVR but the shares must be full control on sharing and security to everyone.

I can limit everyone to read and execute and the shares are still operational.

However, if I remove everyone from security, the share will mount most of the time, but Finder will not display any objects within the shares. While trying to connect to a share with restrictive permissions, the gear at the bottom right spins to no end. I do not get error messages and have to open a new finder to be able to access other files.

I access my shares daily for all my files. All worked with 10.4.10. Apple had me reinstall the OS from scratch - there was no difference.

Earl Pee also can't see files inside of shares:

First off I have the family pack so that I could experiment with more than one Mac. On the MacBook Pro, I did a clean install. Connected it to my network and presto I could see my files on the windows machines.

On the Mac Pro however, I see the shares, but cannot view the contents of the files. So it seems that I have to access as another user, cool right? Nope.

I hit disconnect and nothing happens. It never releases the share or allows me to log in as the user that has the privileges to see the files.

On the plus side... I can now print on my hp 1200 that's connected to a PC. Before I couldn't from the Mac.

More reports of Leopard not seeing Windows network

Wednesday, November 14, 2007

We've had many more reports of Macs no longer being able to see Windows file shares after upgrading to Mac OS X 10.5 Leopard.

Amir Zelcer says his networked computers disappeared:

After making a clean install of Tiger and then clean install of Leopard on my brand new MacBook Pro - no network computers are displayed. All are visible when Tiger was on, but they all disappear in Leopard. The support people here have no idea what's its all about.

Peter Labrow says the previously reported tip of turning off file sharing doesn't work for him:

Like others I can't see Windows servers under Leopard. They just don't show in the Finder, nor does turning file sharing on/off help. These are 'real' Windows Servers, not just other PCs, they are visible from other PCs and from 10.4.10

Edward Olszewski says his PCs can access the Mac, but the Mac can't see the PCs:

I have a brand new 24-inch iMac that came with Tiger. I was blown away by how easy it was to integrate it into my home network of Windows XP PC's.

Now after upgrading to Leopard, I cannot see any of the Windows computers on my home network. Before I would see my workgroup name and I could select my PC's. Now no Workgroups appear at all. There is no “Shared” category in the Finder.

The only way I can access the PC's is to click on the Apple, select recent items, and select the PC's from the servers section. I can't access the PC's by any other method.

Both my Mac (Leopard) and 2 PC's (Windows XP) are connected to a router with cables. Strangely enough, I can access the iMac from the PC's with SMB selected and I can print to all the printers from my iMac that are connected to my Windows PCs with no problem.

Chris James updates his previous report:

John, Just to give you an update, I haven't been able to fix the networking problems yet. "Mac Help" under Leopard says that if you cannot see a Windows Computer in the Finder, it is probably not on your subnetwork and you have to use "Go Connect to Server" from the file menu. This is definitely NOT how Tiger worked and is a step backwards if this is what we are stuck with. The exact same network settings are used under both operating systems. Tiger clearly shows all the Workgroups on the network and is easily browsable,

Leopard just shows the Apple computers, which happen to be here and on today regardless of Workgroup or subnet. No Browsing is available whatsoever.

TIP: Another workaround for Leopard file sharing: re-launch the Finder

Monday, December 17, 2007

Jeff Schlegel tried without success some of the other tips we've reported for file sharing with Leopard. He then came with a new one:

I've been plagued with the Leopard share access problem. Everything worked fine for the first hour, but then all the Windows/NAS shares disappeared. Tried the IPv6 trick, firewall has always been off, basically tried everything but the shares wouldn't show up in Finder and I couldn't "go" to them either.

My fix? If I re-launch Finder, everything shows back up and works perfectly. I re-launch through Main Menu but I'm sure there are other ways to do it. It usually stays working until the machine goes to sleep, and then (randomly) the problem can reappear until I re-relaunch Finder.

If you've tried this if it worked for you.


Random disconnections of mounted Windows Shares in Leopard

Wednesday, November 21, 2007

Matt Sielski, like some other readers, noticed that Leopard file sharing worked at first, then it could no longer access Windows shares. When he did get it working, the mounted shares abruptly disconnect:

Shortly after the Leopard upgrade I could easily browse to my Windows 2003 Server shares with the SHARED area in the Finder. Now, a few weeks later, using the SHARED area just shows "Connecting..." when I try to browse my network. I have to mount the shares with Finder's Go > Connect to server > smb://IPADDRESS/sharename. Once I do that, I can then browse through the SHARED area, however it makes it confusing as there's access to files through the automatically displayed entry for the share there, as well as the one I explicitly mounted.

The most recent development, unfortunately, is that shares I've mounted are randomly disconnected (after about 10 or 20 minutes of use) and no attempt at reconnecting works -- I get a "Connection failed" message if I try. I then have to reboot to get another 10 or 20 minutes of access.

So, consider me very displeased with the step back that Leopard has given us with regard to SMB sharing with Windows. I don't know what to install next, the 10.5.1 update or my 10.4 disk.

Current news on the MacWindows home page.

Fix for Leopard SMB dismounting problem: turn off AirPort

Tuesday, April 1, 2008

Anton Schep found that the problem of random disconnects (here and here) is linked to DHCP. Turning off AirPort while connected to Ethernet fixed his problem:

I found the solution to my SMB disconnects. I use a laptop at work which normally uses a wired connection with fixed IP as a first choice, but there is wireless connection in the building too and my laptop pulls an IP number from the DHCP server via Airport. The Airport connection is (normally) not doing anything as all the traffic goes over the wired Ethernet connection. Apparently, after the 5 minute inactivity the Windows server starts talking to the wireless connection and then fails to reconnect, as the laptop is still using the wired Ethernet.

By turning off Airport the SMB share stays connected. I just have to remember to turn it on, when the wired connection is not available (like at home or elsewhere in my building).

Anybody know how to write a launchd script which automatically turns on Airport is not available and off when it is not?

If you have an answer to his question or have tried this suggestion

Another case of Windows shares disconnecting

Monday, October 13, 2008

Adriana Shmahalo has a problem with Leopard where Windows shares disconnect or disappear without warning:

Have the same problem as another user. Updated to system 10.5.5 and it got worse. I think it started happening since 10.3 update. My Windows shares behave very strange: sometimes they show and sometimes they don't and today is not a good day. I was able to see them for a brief moment and they disconnected again. This has nothing to do with any other network connections - I can go online just fine.

If you've seen this problem

Further description of shares disconnecting from Leopard

Thursday, October 16, 2008

Dan Ball responded to our reports of Windows shares randomly disconnecting from the Mac. One of his users reports that folder icons in Windows are appearing with a minus sign (-) next to them:

I just got a report on this from one of our instructors. With our setup I use WGM to mount shares as login items using the logging in users credentials. I just got a report that the shares periodically will show on the desktop as folders with a negative symbol and the users have to logout and back in again for them to show properly. However while the issue is happening with the folders showing as folders with the negative symbol users can still go through applications save dialogs and save to the network shares still.

So I'm not sure at this point what's going on, I haven't seen it for myself yet.

Running Intel and PPC iMacs. (iSight PPC iMacs and Early 2008 iMacs) All running 10.5.5 with latest updates. Open Directory server is Mac OS X 10.4.11 Server with latest updates and our Windows Domain is 2003 R2.

If you've seen this

Current news on the MacWindows home page.


Readers say workarounds for Leopard file sharing woes are unpredictable

Thursday, December 27, 2007

Two readers report that none of the many workaround for Mac OS X 10.5 Leopard file sharing problems work all the time. Previously, some readers have said that one or another workaround works, while others report that they don't. Yet others say workarounds work only some of time.

Stephen Roberts said the workarounds are erratic:

I just wanted to let you know that I have tried most all of the suggestions posted on your site including turning off IPv6, turning off the firewall on my iMac and PC, choosing a different password without symbols, turning file sharing off, and editing the name of the workgroup. None of these things have fixed the problem and browsing for network servers; they seem to yield different results every time. It's very unpredictable.

However, I have learned a couple of things:

1. I think that editing the name of the workgroup in the Advanced Network settings does have an effect. It seems to have an easier time finding the Windows machine, even though for me the connection still fails.

2. Turning off Simple File Sharing on the PC allows me to "Connect to Server" as a registered user, giving me access to every file on the PC. With that setting toggled on I could only connect as a guest which only gave me access to my shared documents folder.

I hope this helps others out there. I'm giving up. I will just use Connect to Server from now on.

David Searles points out that the 10.5.1 upgrade did not address the problems, and also reports erratic behavior:

I wanted to confirm that Apple still has not fixed any of the Windows file sharing issues it introduced with Leopard. Every boot of Leopard is an adventure when it comes to Windows file sharing; some days nothing at all shows as "Shared" resources, other days SOME resources show up for a fleeting appearance. Very distressing!

One would think they really don't give a hoot about correcting their screw-up. How difficult can it be to look at the code they changed between Tiger and Leopard to find the bugs?

Note: one previously reported tip not mentioned in today’s report has to do with changing firewall settings.

Reader TIP: use same subnet to get around Leopard file sharing bug

Wednesday, January 2, 2008

Deanna Santangelo offered yet another fix for Leopard's problems accessing Windows shares:

I was unable to connect to my Windows XP shares from the Mac even though my Windows XP machines could connect to Leopard shares. After several hours of trying different things I found it worked if I moved the Mac to the same subnet as the XP machines. I have no idea why this was the case since the other direction worked fine. I don't have any ACLs configured on the router.

If you've tried this suggestion if it worked for you.

Reader uses Connect to Server to deal with Windows shares disappearing off Leopard sidebar

Wednesday, January 2, 2008

D. Harminder reports another bit of odd behavior with Leopard problems browsing Windows shares:

I've had the same problem as others after upgrading to Leopard, with my Windows PCs disappearing off the Leopard sidebar from time to time. This was usually resolved with a Mac reboot.

After some time, I've found that if I connect to a drive using the GO- >Connect To Server, then giving the smb://... drive URL, ALL of my Windows PCs reappear in the sidebar! And all starts working again as normal.

TIP: Instructions for configuring AirPort/Leopard for Win share access

Wednesday, January 2, 2008

Jake Braun had success fixing Leopard's file sharing problem over AirPort. He used a previously submitted suggestion to create a new location for the wireless connection, and not use the Automatic setting. Braun sent us step-by-step instructions on how to do that and configure the proper settings:

My iMac (Leopard 10.5.1) can now connect to some of my shared volumes on the Windows XP. The "magic bullet" seemed to be creating a new "location" in network rather than using the automatic setting, as suggested by Shane Moore. I was then able to enter my WIN workgroup on the iMac network preferences, and it didn't disappear! For sharing printers attached to the XP machine the key was entering the IP address of the XP machine in addition to the workgroup name.

For other OS X newbies like me, here are the steps:

  1. Click on Airport symbol at top of screen and choose "Open network preferences" (you can also get there via System Preferences" icon in Dock).
  2. Click on down arrow next to "Location" and choose "Edit locations."
  3. Click on "+" and type in name (I used Home).
  4. Click on "AirPort" in the box at the left to make sure you are configuring the right connection. I stayed with default configuration, typed in the name and password for my WiFi network.
  5. Click on Advanced.
  6. Click the AirPort tab at top; add network if necessary and the security info.
  7. Make sure you are connected to the wireless network.
  8. Click on WINS at top.
  9. NetBIOS name should be filled in and gray (mine showed "iMac").
  10. Click drop-down menu on Workgroup and you should see your Windows workgroup name.
  11. Click on Plus key and enter the IP address for the Windows machine you want. (You can get this on your Windows machine by going to start, run, type "cmd" and press enter. This brings up a DOS window. Type ipconfig and press Enter).

Entering the IP address in addition to the workgroup appears to be essential to be able to see shared printers attached to the XP machine.

TIP: DNS command-line configuration -- a final answer for disappearing Win shares in Leopard's sidebar?

Monday, January 7, 2008

We've reported numerous varied suggestions for Mac OS X 10.5 Leopard problems with Windows server browsing and file sharing. Some work for some people, and some work only temporarily.

Kevin David found a solution in a blog that involves typing in some configuration commands in Mac OS X's Terminal command-line utility. The blog gave these instructions:

Type this in Terminal:

$ sudo pico /etc/smb.conf

Then add the following line to the [global] section:

name resolve order = lmhosts bcast wins

Save it, then disable and reenable file-sharing from the Network [sic: we think this should be Sharing. -Ed] panel, checking "Advanced..." to make sure that SMB is enabled. After a minute or two, your Shared should be back in the sidebar.

The blog claims that the root of the problem is a DNS issue, which is similar to what one of our readers once reported.

Kevin David says this edit works to fix the problem:

This bug was driving me insane until I stumbled over this fix a couple of weeks ago. Since I've done that, machines appear in my sidebar and stay there.

If you've tried this We caution, however, that if you've never used a Unix shell command-line before, you may not want to experiment with this approach.

Readers says Terminal DNS edit doesn't fix Leopard file browsing

Wednesday, January 9, 2008

Neal Tobochnik reports that Wednesday's suggestion to use a Terminal command (directly above) did not help Leopard's problem with browsing for Windows shares:

I followed Keven David's suggestion. It worked until I rebooted the computer. Repeating the procedure did not help. BTW you must change file sharing from the share control panel not the network control panel.

Readers verify and correct DNS command-line configuration fix for disappearing Win shares in Leopard's sidebar

Monday, January 14, 2008

Two readers verified a command-line fix we reported for the Leopard's Windows share browsing bug. Neal Tobochnik, who previously told it didn’t work, got it to work with a small corretion:

Actually I finally got your tip to work. You have to turn off and on file sharing in the Sharing panel not the Network panel. Also in the Sharing Panel options you have to check the SMB option.

Max Minkoff also reported success:

Wow! I just tried this and it worked immediately and fantastically. I can't confirm that things don't go in and out, as I've just done it a few minutes ago, but it was really a charm.

Now if I could just get my VMWare Win XP machine to see the servers also... But I'll keep looking.

More success with the command line fix for Leopard file browsing problems

Wednesday, January 23, 2008

John McGrath reports that the suggested Terminal command fixed his problems with Leopard file browsing:

I tried the command line fix. So far this seems to have worked. None of the other fixes stuck.

Reader says command-line Leopard file browsing fix works, but not always

Friday, January 25, 2008

Bill Paulson said the command-line fix listed on our Leopard Tips and Reports page improved the problem with Leopard not seeing Windows servers, though not completely:

I'm on a very large network, and Leopard's always been very flakey about displaying Windows shared drives.

I tried the fix at your site, adding:

name resolve order = lmhosts bcast wins

to the /etc/smb.conf file.

As best I can tell, this has improved the behavior. Prior to doing this, I never saw the full list of more than 500 workgroups within Alcaltel-Lucent. After doing this, it usually shows the full list, though not always.

Variation on Terminal fix for Leopard file sharing

Monday, February 18, 2008

Katie Berryhill verified the Terminal DNS-configuration command fix for Leopard file sharing, though under some interesting circumstances:

The terminal fix for Windows sharing under Leopard worked great. Interestingly, though, I didn't have to finish it. I entered the command in Terminal, moved the cursor to the "global" section, and started typing (and, in fact, had mistyped it so far) and my Windows shares popped into view. I corrected the misspelling, finished typing the command, saved it, and they were still there. When I re-enabled file sharing, the Mac was visible to the PCs (when it hadn't been before).

NETBIOS name: Another theory and suggestion for Leopard File browsing

Wednesday, January 9, 2008

David Cohen (who writes for MyMac.com) has another theory and suggestion about Leopard's problems with Windows file browsing:

You have plenty of suggestions for fixing the Leopard Windows sharing issue, that I see are all a bit hit or miss. I think the reason for this is because a lot of the things people are trying are fixing the real root issue by accident.

The Leopard advanced network settings has a WINS tab, and in this there is a NETBIOS name field. This is auto-generated by Leopard - it looks like it uses the MAC address to generate it. However, if what is put in there is not compliant with the NETBIOS settings of the Windows network you are connected to, then browsing will not work, because the WINS server will not acknowledge the WINS requests coming from Leopard.

The actual NETBIOS name requirements supported vary depending on the flavour of OS running on the WINS servers on the network. I would suspect the best route to success is to use the most basic NETBIOS name requirements, back from the old Windows NT 4.0 days - stick in no more than an 8-character alphanumeric into the NETBIOS field, and all Windows browsing will be restored.

I had two Leopard machines, one which would browse and one which would not. The browsing one had an 8-character WINS setting, and the non- browsing one had a MAC address in the WINS field. Removing the MAC address and putting in a simple word in the WINS field IMMEDIATELY reinstated browsing.

If you've tried this if it worked.

Reader says "no go" to NETBIOS change to solve Windows sharing issue

Monday, January 14, 2008

Tom Hughston reported that "The NETBIOS name change to an 8 alphanumeric name did not solve the problem." That problem being Leopard's problems with Windows file browsing.

Hyphen havoc with NetBIOS name for Leopard SMB/CIFS file sharing

Monday, June 16, 2008

Robert Winterhalter reports that a hyphen in the NetBIOS name causes problems for Leopard filesharing with Windows. Some previous reports have also pointed to problems with NetBIOS names (here and here). Winterhalter said:

One thing I've discovered that may be causing some of the SMB/CIFS issues with 10.5 is that for some reason the Mac OS is not allowing the "-" character in the NetBIOS name, and it drops everything after it as well. This is causing havoc at my site because the NetBIOS name seems to be trying to default to the domain name, which for us is "XXXX-NNN", where XXXX is specific to a subnet, and NNN is specific within that subnet. Thus ALL computers in the same subnet end up with the same NetBIOS name.

Many thanks to the contributors of your site, as it's been quite helpful.

If you've seen this

TIP: Using uppercase workgroup name for Leopard file sharing

Monday, January 7, 2008

Rich Kosiba was seeing Leopard's file sharing problems while trying to access network attached storage (NAS). He fixed his problem by changing the workgroup name to all uppercase in System Preferences:

I have a Tritton NAS here, not sure what OS it runs. I had no problems connecting to it with Tiger but had many problems with Leopard. Some of the tips from your site got me to connect but there were no files in any of the shares once I connected.

It turned out to be a case-sensitivity issue with the workgroup name. My workgroup name was all lowercase in the System Preferences but I noticed that whenever I type the workgroup name in Windows or on the NAS it is automatically converted to uppercase. Changing the workgroup to all uppercase in System Preferences resolved my issues.

If you've tried this suggestion

We've also had previously reported suggestions regarding workgroup names.

Restarting Leopard provides relief from file sharing woes...

Friday, January 25, 2008

Jason Wood reports that restarting Leopard provides temporary relief from Windows file sharing problems.

I was just reading the reports you have of people who cannot connect to Windows servers with Leopard. I thought I'd let you know that I have the same problem and rebooting seems to help--usually. Very unusual.

If you've tried this

...and so does a clean install

Andy Peat in the United Kingdom said fixed his file sharing issue with a clean install of Leopard:

I too have had real problems with this, tried all the possible fixes on the net WINS, DOMAIN network configs, absolutely nothing. This machine was an upgrade from 10.4 I did a clean install on a Mac at work and all the windows shares popped up like a dream. So for me it looks like it could be an upgrade account issue.

If you've tried this

Restart helps when Leopard disconnects Win shares

Monday, January 28, 2008

Michael May agrees that restarting helps with Leopard file sharing problems. His problem is that Leopard disconnects a Windows share and can't log back on:

Yes, I am getting a similar SMB problem to the one others are reporting: I'll come back to my desk to find the SMB share has disconnected, then when I try to reconnect, I get: Connection failed ... The server may not exist or it is not operational at this time. Check the server name or IP address and your network connection and try again." Rebooting does the trick, but nothing short of that: Log out/in, or relaunching Finder does not help. I have encountered this just in the last few days, so it's not Leopard in general, but must be one of the security updates or something else.


Windows shares appearing and disappearing from the Mac's view at random

Friday, November 2, 2007

Mark Pouley has a mystery, with Windows shares appearing and disappearing from the Mac's view at random:

I'm having a similar problem with Leopard and Windows machines. I have 3 Windows desktop and one Windows laptop machine in my house and I have Leopard installed on my iMac (20" Intel white edition).

When I installed Leopard none of the Windows machines showed in "shared" but I could connect to an external drive on one windows machine using the IP address. I thought I had a network problem and poked around without really changing anything.

About an hour after install, for no reason, the laptop appeared in the list (it is a new Sony running Vista) this was odd. A few minutes later, all the machines showed. While poking around to see how this worked (clicking on the drives, seeing if all shared volumes were accessible, etc) all of the machines "disappeared." Over the weekend the machines have appeared and disappeared without notice and without any clear clue as to what is causing this issue.

If you've seen any of this

More on Windows shares disappearing from Leopard's view

Wednesday, April 16, 2008

Andreas Tagger reports having the problem with Windows shares appearing and disappearing from the Mac's view at random:

We are having the same problem as Mark Pouley on our network here at the office and we cannot figure out how to fix it. One thing that seems to help is to disconnect the Netgear swtiches from the chain that connects to the server. I am not sure if this is a solution or not. Basically all our PC servers are "moody." They seemingly appear and disappear at random.

If you've seen this problem

TIP: Aliases as a workaround for disappearing Win shares in Leopard

Friday, April 18, 2008

Peter Shindler discovered a simple workaround to the problem of Windows shares disappearing from Leopard:

I am the IT manager of a company, and we have several Mac users in the office. We have shared folders on of our servers, and this problem was happening.

What I have found that helps is to create an alias of the share. When the share disappears, click on the alias, and it reestablishes the share-it pops back up right away.

If you've tried this

TIP: fix for disappearing files on Vista share

Friday, April 18, 2008

Ray Drury found that the name of the folders on a shared Windows Vista machine caused trouble with Leopard access:

We have a Vista share which we access via our Macs. It all works fine under OS 10.4.11 but our new Mac running Leopard 10.5.2 mysteriously can't see some of the folder contents within a share on the Vista PC. The symptoms are, click on a folder and no contents are shown, when you click away the folder disappears. After lots of hair-pulling, we have discovered that the folders in question have a 'space' at the end of their name, removing this space allows the folders to be viewed as they should.

If you've tried this

Tip verified: Removing space made files visible

Monday, April 28, 2008

Dave verified a previously reported fix for a Leopard problem with files disappearing from mounted Windows shares. The fix cleared up some other symptoms as well. Dave reports:

I had a server with three Macs and many a few PCs on it. Our temp used one folder alone for hundreds of files, but some of her folders and files were not visible everywhere. The PCs and OS 10.4 Macs can see all the files fine.

The 10.5 Mac had these issues:

  • Sometimes could not see all folders
  • Opening a folder found zero items inside (even though they existed)
  • Folders would show wrong dates, 0k, and blank icons
  • Clicking off the folder made all the blank icon folders disappear completely

After much searching I found your site with this recent solution: The file names have a space at the end. Remove the spaces and the files/folders all show up properly. It worked perfectly.

Random appearing/disappearing of Win shares from Leopard

Friday, June 5, 2009

Philip Mayall confirms a previously reported problem with Mac OS X 10.5.x where files on Windows shares randomly disappear from view:

Regarding your report Windows shares appearing and disappearing from the Mac's view at random, this happens to me on my iMac 2.66 Intel Core 2 Duo running 10.5.7 connecting to my WinXP machines.

Previously, we reported a workaround that involves removing a space at the end of the name of files and folders on the Windows shared drive. If you've tried this fix for this problem


Another Leopard problem with Win servers; shares turn into aliases

Friday, January 25, 2008

Chris Pope reported another odd problem with Leopard file sharing with Windows server. It sounds similar to the reported problem of being able to mount servers and not being able to copy files. Except in this case, the shares turn into inaccessible aliases:

I have a G4, just did a fresh install of Leopard, 10.5.1. Used to use Tiger (we have 2 other machines running Tiger), in a small office, with a Maxtor Shared storage plus, network drive.

After installing Leopard (it went pretty much to 10.5.1) I am able to connect to the Maxtor SMB share, but 4 out of 12 directories cannot be accessed. If you click on the directory, it changes from a folder to a 0kb alias.

After a heap of searching and not really finding anything, I copied the 4 offending directory's from another machine and renamed them (they are considerable in size and hold most of our company data) I was then able to access most of the directories beneath the original faulty root directories. Some directories are still exhibiting this alias issue.

I have seen a work around for samba servers to update the smb.conf file with the line USE UNIXESTENSIONS = NO (or something very similar) but this is a Maxtor drive and without serious pain I don't think I'm going to get access to the smb.conf file.

If you've seen this


Reader says Leopard 10.5.1 does not fix SMB file sharing problems | Top of Page |

Monday, November 19, 2007

David Searles reports that the Leopard file sharing problems are still occurring after the Mac OS X 10.5.1 update:

When I first installed this update and turned File Sharing back on, everything looked to be working. I was psyched! But the next day after a reboot, Windows networking is once again GONE and now turning File Sharing off does NOT bring it back. So until Apple fixes this disaster, I'm stuck without ANY access to my Windows network!

Christopher Ferrante also said that the 10.5.1 update did not fix the problem.

Please note that we have been reporting a variety of different workarounds for 10.5.0, though no absolute fixes yet.

Leopard 10.5.1 problems writing to mounted Windows drives; 10.5.1 fixes at least one problem | Top of Page |

Monday, November 19, 2007

Jean Robert Opgenort in The Netherlands reported Leopard problems copying files to Windows drives on both on a network and in a virtual machine. He also said that the 10.5.1 update fixes one problem:

I am still having problems writing files from my Mac (running Leopard 10.5.1) to mounted Windows drives -- both folders on the Windows 2003 Server (SMB/NTFS) at my work and the Windows XP virtual machine (NTFS/ Parallels) on my Mac. Here are four situations where it works and where it doesn't work.

1. Guest account on mounted Windows shared folder: writing (dragging and dropping) from Mac to Windows works OK. This was problematic in 10.5.0, but fixed in 10.5.1.

2. With any type of account, reading and copying from Windows to Mac works OK.

3. Authenticated user on mounted Windows folder: writing (dragging and dropping) from Mac to Windows does *NOT* work. Leopard stalls when copying files (> 4kb) to Windows, sometimes producing a -36 error code (stating that the Finder cannot complete the operation because some data cannot be read or written). I cannot even connect to my virtual machine as an authenticated user. I am always logged in as a guest even after choosing the "Connect as" option.

4. Dragging and dropping directly into the Parallels virtual machine (thus not via the mounted drive) works OK.

So the writing problem seems to be related to mounted drives.

More readers with 10.5.1 problems writing to volumes via SMB | Top of Page |

Wednesday, November 21, 2007

We've had more reports of copying data to SMB file sharing volumes with Mac OS X 10.5.1.

Glenn Josephsons also sees the problem with writing to volumes via SMB with a USB drive attached to an AirPort base station:

The 10.5.1 update problem with SMB/CIFS shares doesn't only affect access to shared Windows drives. It also affects external drives hung off the USB port of an Airport Extreme base station, since it uses CIFS. I have a G4 PowerBook running 10.5.1 and it cannot even see the 1 TB external I have attached to the AEBS. My iMac with 10.4.11 has no problem with it, and neither does my Dell running XP Media Center. There have been several workarounds suggested on the Apple forums, none have worked for me and apparently for most others.

I also have a shared drive on the PC that the 10.4 machine works fine with that the Leopard machine can no longer access. All this at least worked to some extent before the 10.5.1 patch.

John McGrath:

I have been experiencing the intermittent visibility of Windows shared files on my MB with Leopard 10.5.1 (the larger update). I have tried all of the combination of settings on the Mac that are suggested by other readers and the only one that consistently works is turning off AirPort and tuning it back on (I also get the occasional lose of connection after the Mac has gone to sleep). I have two Windows systems a Win 2000 that can be manually connected routinely and an XP Pro that requires the Airport reset about half of the time. Neither of the Windows machines appears automatically in the shared space on Finder and nothing shows up in the network window.

Jeffrey McGuire said that 10.5.1 update did not help accessing Windows computers:

Have now updated to 10.5.1 and things have actually gotten worse!

Recap: within 20 minutes of turning on my first Mac at home, I was inside my Windows computers on my home network.

Now Leopard 10.5, I couldn't find for the life of me how to connect to my Windows computers again. Tried turning file sharing on and off on the Mac. It didn't change anything. I got "share" and my Windows computers to appear in the Finder by configuring System Preferences|Network|Airport|Advanced|WINS to be in my specific (Windows) workgroup.

I confirm Jean Robert Opgenort's reports as far as they relate to my system:

Under 10.5: I could move data from Win XP machine to Mac, but not Mac to Win. - The "connect as" dialog opened but didn't do anything. I was only logged in as "guest" no matter what I did.

Now under 10.5.1 when I click on "connect as" I sometimes get an error that the server has disappeared and selecting the Windows machine in the Finder "shared" section produces a blank.

Don't know if it is related, but the Parallels clipboard is very spotty. I never know how long it will work. Copying and pasting in and out of the virtual XP machine always craps out sooner or later. Also: XP VM producing horrible freeze/hang situations in Office and also in Explorer functionality.


Reader can log onto Win server but can't copy files -- 0-byte files left | Top of Page |

Wednesday, January 9, 2008

Duncan Maclay can get onto his Windows server from Leopard, but has the previosly reported problem of copying files to Windows drives:

I can mount all my shares on a wide selection of Win 2000 and XP boxes, my NAS and indeed on the Win 2003 server. What's more I can read, open and close files on any of them no problem. So far, so good. But here's the thing: I cannot save on the Win 2003 server. When I save, it creates a file, beachballs around a bit, bleats about privileges (despite me being logged on to the server with an admin account) and leaves a file on the server with the right name and 0 bytes in it. I am tearing my hair out.

If you've seen this

Workaround for Leopard write problems to Windows shares-- SMB signing

Monday, January 14, 2008

Duncan Maclay offered a workaround for the problem where Leopard can't write to volumes via SMB even though they can connect. (See also here.) His workaround:

In the interim I have resolved the issue. It has to do with SMB signing on the server. In order to get the permissions to work properly, you have to create a GPO [Group Policy object] on the server. This appears to a new development under Leopard which was not *necessarily* the case under Tiger.

If you’ve tried this workaround if it worked.

Joel Farthing describes the problem:

I have the same problem as the reader who reports being able to read files on windows network shares but not save. Creates a file with 0 bytes. If a solution becomes apparent, I'd appreciate hearing about it. Thanks.

Ville Vartiainen said "I have exactly this problem too. I hope there is a fix very soon!"

Marek Absolon said "I have the same problem."

More on disabling SMB signing to fix Leopard file copy problem

Monday, January 28, 2008

Maarten Vink confirmed a suggestion for the Leopard problem of being able to log on to a Windows share but not copy files:

I had the problem described here with Mac OS 10.5.1 and a Windows 2003 server. Connecting to shares mostly worked, but reading and writing files almost always failed completely or created 0-byte sized files. The fix suggested by Duncan Maclay (disabling SMB signing on the server) resolved this.

We note that Duncan Maclay's suggestion involoves creating a Group Policy object (GPO) on the server and disabling SMB signing. Microsoft describes how to do this in a downloadable document called Connecting Mac OS X 10.3 and Higher Clients to a Windows Small Business Server 2003 Network. See the section called "Disable SMB Signing on the Server."

Apple says Leopard file copy problem a known bug

Friday, April 18, 2008

Dave (no last name) reported the Leopard 10.5.2 file copy/SMB signing problem to Apple, which replied that this was a known problem:

I have the issue with OS X, where by I can't write to NTFS shares on W2K3 servers with SMB signing turned on, even with IPV6 disabled for the interface. I haven't tried turning the signing off (as suggested by some of your readers), but that's a ridiculous fix (good luck convincing your domain admins to downgrade their enterpise security for OSX users).

To recreate the issue:

Create a folder named test that contains two files one named ._test.txt and test.txt on OSX and copy to an SMB share on W2k3.

This results in spurious errors about permissions and locked files.

Copying a file larger than 4k results in the error:

"The operation cannot be completed because you do not have sufficient privileges or some of the items."

Using mount_smbfs from a shell on OSX results in the error: "Permission denied"

Using smbclient from a shell on OSX results in SUCCESS!!!

If you do need to drag and drop in your gui world, Thursby's DAVE will work, though it'll cost you $120

This is the response I had from Apple:

Hello Dave,

After further investigation it has been determined that this is a known issue, which is currently being investigated by engineering. This issue has been filed in our bug database under the original Bug ID# 5635546...

More reports of Leopard file copies resulting in 0-kbyte files

Monday, February 25, 2008

We've had two more reports of Leopard users who can log onto Windows servers but can't copy files. Alain has a workaround that works for Office files, but not others:

I have the same problem as Duncan Maclay, with Leopard 10.5.2. Drag & drop to copy a file to Win 2003 server doesn't work. Result: File with 0 kb. When I open, lets say a Word document, and save it from within the application to the Win 2003 server, it does work! Investigating this further, I learned that Word, Excel, text and PDF files could get saved this way. Photoshop, Indesign, Illustrator and SketchUp files cannot be copied in this way.

What does this mean -- does size matter? SMB signing is already disabled (Was default in Win 2003 server RC2). I saw a 'how to' that seems interesting, but I'm not sure whether I want to do the registry fiddling to disable the scalable networking components.

Stuart Newman has the problem with files he created, but NOT with files he didn't create:

I'm having an odd problem with Active Directory that might usefully be highlighted on your ace website.

I CANNOT copy files from local machine into server directory (exception: a 4k .TXT document). This is, as you can imagine, pretty crucial. I also cannot move folders that I have created. Mac OS X asks for authentication, makes a copy noise, but nothing happens.

Attempts at creating new files (i.e. copy from local drive to server directory) leave a Zero KB file with the same filename, visible from other machines.

I CAN do the following:

  • Move files and folders that I have NOT created around with alacrity
  • Open files on the server and copy them to my local machine
  • Create new folders and name them
  • Rename files and folder
  • Delete files and folders

Details of my system:

  • Running OS X 10.5.2, Mac Book, 2.2 GHz, 2GB RAM
  • Active Directory, NTFS, Win 2003 Server, using a static IP (no DHCP)
  • IPv6 turned off (tip from web)
  • Bonjour turned off (tip from web)
  • Server root itself is not mounted on desktop but two 1st-level subdirectories (the ones I work off) are mounted as drives.
  • In terms of permissions I have full control over a wide range of directories.

I have bound to Active Directory using Directory Utility and it says that "the server is responding normally". Log in is fast and Directory Utility claims the server is responding normally.

TIP: Reader found out-of-sync server preventing file transfer

Monday, April 7, 2008

A reader reporting the problem of Leopard not writing to volumes via SMB tried without success the suggestions on our Leopard Tips page. He accidentally fixed it with time syncing:

Nothing listed at your site fixed the problem for me. However, when I went into work one day, all of a sudden I could copy from Leopard to the Windows server.

After scratching my head for a while about what had changed--no updates or changes had been made to either machine--I realized the only thing that had happened between Friday and Monday was the change to Daylight Savings Time.

It would seem in my case at least, the problem was caused by the clocks on the two servers being out by just over a minute. With the time change, they both managed to get back into sync and hey presto I could copy from the Mac to the Win server.

If you've seen this issue

Leopard connecting to Windows server, 0k files, and crashing the server

Tuesday, March 18, 2008

Chris Dodsworth reports the Leopard problem of being able to log onto Windows servers but with no read/write access. In his case, the copy crashes the server:

This is exactly the same issue I am having, well a few to be precise with 10.5.2 and Windows servers. It is driving me nuts trying to work it out.

A number of iMacs running 10.5.2 can see the Mac shares on the server running Windows SBS 2003 fine. The minute any files are copied you get the progress of the items being copied, seems to appear on the server and then just hangs. In most circumstances the copying crashes the whole server. Have tried binding the iMacs to AD, but no joy. SMB sharing (with AppleTalk turned off) doesn't help either.

The only workaround was to copy the data to a NAS unit and then have shortcuts for both PCs and Macs.

We have some previously reported suggestions here.

Another report of Leopard 0k file problem crashing Windows server

Tuesday, April 1, 2008

Bryan O'Malley verified a previous report of a reader who not only saw the Leopard 0k file-copy problem, but that it also crashed the server:

I just wanted to follow up on your March 18, 2008 post on your site.

I have this exact same problem with my Windows SBS 2003 server, and I have tried the Group Policy Object work around, and it doesn't help. The server still crashes, and a reboot of the server is the only way I've found to get everything back up and running.

I'm not clear if this is a Microsoft problem or an Apple problem, but it's extremely painful.

If you have any ideas for a workaround

Current news on the MacWindows home page

IPv6 didn't solve Leopard writing problem to Windows

Tuesday, March 18, 2008

Mark Prouty said turning off IPv6 doesn't fix Leopard's 0 k file copying problem:

I have a Mac Pro which I just bought, but it is a year old model. I could easily read files off a Windows machine, but not write. Authentication was not an issue on the Windows side, since I needed proper credentials to even read the file. The Mac reported the following: "The operation cannot be completed because you do not have sufficient privileges for some of the items."

After turning off IPv6 on that interface solved this problem, I don't get the error dialog box anymore, but the file is still 0 bytes long. So this did not fix it.

I have the same problem whether I copy to server 2003 machine, or a Windows Vista machine, or a Windows XP machine. Same exact symptoms.

Suggestions for Leopard 0k file copy-to-server problem: DAVE and smbclient

Tuesday, April 1, 2008

Klaus did some investigation of the Leopard problem getting 0-byte files on Windows server when copying files to the server. He says that Thursby Software's DAVE does not have the problem. The smbclient command in Terminal also works. Klause said:

I have the same issue. I mount our share in the company on a Windows 2003 Server and cannot copy files to it. All files have 0 bytes, but I can create directories. My password has special characters in.

I did some test and here are my findings:

  • Can not copy with Finder. I get size 0 bytes and Finder error.
  • Can not copy when mounting via command line:

mount -t smbfs
Error: Permission denied

I CAN COPY with smbclient command in Terminal Here it works fine and I can copy.

I also tried the trail version of DAVE and had no issues to save files on the same server. I also changed my password, but it still contains special characters (before it had a @ sign in) In my opinion it is the smbmount (smbfs) module in the Leopard core system that causes the problem.

Current news on the MacWindows home page

Path Finder utility gets around Leopard zero-k file copy-to-server problem

Wednesday, April 16, 2008

Stefan Krause found that a utility can workaround Leopard's file copy problems that result in 0-kbyte files on Windows servers. Readers have previously reported that the problem doesn't occur when using Thursby Software's DAVE or the smbclient command in Terminal. Krause discovered the problem also doesn't occur with Path Finder from Cocoa Tech, a utility that bypasses the Mac OS X Finder:

I have been struggling with the same problem for months: I can mount and access shares and copy from the shares to my Mac but can't write to them. Using a first-generation MacBook Pro with OS X 10.5.2. Today, I fired up Path Finder, not expecting to have much luck, but I actually managed to move files and whole folders to the share without the slightest problem. Other user's mileage may vary, of course.

However, directly below, a reader reports that Path Finder didn't work for him.

If you've tried Path Finder or Thursby's DAVE to fix this problem

Reader says Path Finder no go, but DAVE works for Leopard zero-k file copy problem

Friday, April 18, 2008

David Sly tried a suggestion regarding Leopard file copy, unsuccessfully, but other suggestions worked:

In response to the topic "Path Finder utility gets around Leopard zero-k file copy-to-server problem," it did not work for me. Yet Thursby's DAVE and ADmitMac, and SBMclient via the terminal do work for me.

Workarounds fail readers in file copy, 0-byte file bug

Friday, May 23, 2008

Two readers said that workarounds we've reported for a Leopard 10.5.2 problem of being able to log into a Windows server, but having 0-byte files left on the server when trying to copy files.

Casey Jensen tried two workarounds without success:

I am having this problem as well. One of my users at work upgraded from Tiger to Leopard and is now on 10.5.2. He can create directories on the server, but copying files gives him an error prompt that states that he doesn't have permission to read one or more items in the item. The files are then actually created on the Windows server, but are 0 KB and cannot be opened.

The times are not out of sync on the server and the client, so that's not the issue. Disabling SMB signing didn't work either.

Pea also tried turning off SMB signing without success:

Just wanted to let you know, that I've wasted the whole day on that issue. My Server is a Win 2003 RC2 server with Active Directory and a few shares, nothing special. Client is a 24" iMac with OS 10.5.2 (all recent updates). The workaround did not work (SMB signing deactivated in group policies).

We've previously reported that Apple acknowledges this as a known problem. If you have a suggestion for this problem

Leopard 10.5.3 update may resolve the"0 byte file copy" problem

Friday, May 30, 2008

Two readers report that Apple's new Leopard 10.5.3 update has fixed the Leopard-only problem of leaving only 0-byte files on a Windows server when trying to copy files. One of the readers, however, says that the file copies are very slow.

Joel Farthing is having no problems after the update:

I'm cautiously optimistic that the 10.5.3 update has fixed this problem: the 0-kb issue has disappeared for me. Before the 10.5.3 update, any attempt on my part to move or copy a file from my PowerBook G4 running OSX 10.5.2 to my company's Windows Server SMB drives resulted in a 0-kb file and a permissions error. I attempted, successfully, to use a trial version of Thursby's DAVE software to correct the problem. After uninstalling DAVE and upgrading to 10.5.3, the problem seems to be fixed.

Rault Kehlor can copy files, but very slowly:

I just updated to the new 10.5.3 in hopes that it would FINALLY let me copy to my Windows servers. Well, after some playing around, it seems that files WILL copy. It takes forever, but I was able to copy a 77MB Toast file to and from the server. It seriously took about 25 minutes. Like others have noted, creating/deleting folders, or copying small files, works fine. It's weird that the behavior changed, but not totally fixed. If DAVE can do it, why can't Apple?

If you've seen this problem whether or not the 10.5.3 affects it.

Readers agree, Leopard 10.5.3 fixes 0-byte file copy problem

Tuesday, June 3, 2008

Several readers confirmed to last weeks report that the Mac OS X 10.5.3 update fixes Leopard's problem of copying files to a Windows server leaving only 0-byte files on the server. Readers also commented on the update's effect on printing, with differing opinions.

Casey Jensen:

The 10.5.3 update seems to have fixed the issues with copying files to a Windows server and leaving the 0-byte ghost files. My co-worker no longer has issues after I instructed him to download the update. It certainly, however, has not fixed Windows printing problems!

K. Kerekes found that the update also eliminated the "._" issue:

I have definitely seen this problem, and 10.5.3 does definitely seem to fix it. I have previously assumed that the problem was due to OS-X's stubborn creation of "._" files conflicting with a security policy on the Windows side. Now it appears that these file are no longer created when copying to Windows Server volumes.

Michael Jackson said that it helped his printing, but still has some share access issues:

10.5.3 seems to have fixed this. I can read/write/delete on my own Windows directory on a WIn2003 SMB server.

Printing works as well now, the logon credentials are accepted.

Still one issue, though: I can access some, but not all of the other directories. (It all works fine from my secret windows laptop, so it isn't a permissions issue on the server). Still something a bit weird here.

TIP: Reader says 10.5.3 didn’t fix 0-kb file problem, but AD user tweak does

Monday, June 9, 2008

Gordon Barnes wrote to say that Mac OS X 10.5.3 update hand no effect on the Leopard 0-byte file copy problem. He fixed it with an Active Directory tweak. Last week, readers reported that the update had fixed the problem. Barnes said:

I have suffered the much-publicized 0kb file saving issue from Leopard to Windows 2003 share. I was pretty sure that this was not a permissions issue. The user had had no problem on his previous Panther machine, nor was there any issue for him saving to the drive from Windows XP.

Reading that 10.5.3 was likely to cure the problem I applied it. No change whatsoever. Problem is still there.

I decided to investigate the permissions problem further. I noticed that all the permissions on the individual shared folders had his user account added only by virtue of him being part of a Group in AD. So, as an experiment, I then added him as an individual user and gave him the appropriate permissions and this fixed everything! Perfect saving. Problem fixed.

What's going on here? Is it that any AD-bound Leopard machine does not understand AD Groups? Certainly other users with AD-bound Tiger machines have no such problem. I'm no expert in either Leopard or Windows 2003 but this does seem odd.

If you've seen this issue or fix with the 10.5.3 update

Reader verifies AD fix for 0-kb file problem

Tuesday, July 22, 2008

Matt Wheeler verified that adjusting Active Directory fixed Leopard's 0-kb file copy problem.

Neither 10.5.3 nor the 10.5.4 update fixed this issue, but the tweak explained at MacWindows fixed it. Windows Server 2003 + User accounts in Active Directory security groups = Unhappy Mac. Used to work fine in 10.3.X and 10.4.X. Upgrading to 10.5.X broke it for us. Thanks for this fix!

Neither 10.5.3 nor the 10.5.4 update fixed this issue, but the tweak explained here fixed it. Windows Server 2003 + User accounts in Active Directory security groups = Unhappy Mac. Used to work fine in 10.3.X and 10.4.X. Upgrading to 10.5.X broke it for us. Thanks for this fix!

Reader says 10.5.4 didn't fix Adobe file saving issues with Win Server

Tuesday, July 22, 2008

Tony Sterckx in Belgium is having problems with saving Adobe files to Windows Servers. He is running Leopard 10.5.4, which Apple reported as having fixed the problem. Sterckx reports:

We work on a daily basis with Adobe and Windows Server 2003. Since Leopard came along, we noticed Adobe failing to save InDesign, Illustrator or Photoshop files on our server. Various problems like:

  • Opening in read-only
  • File not found upon saving
  • Error saving

I don't know how many of these things have been fixed by previous updates, but I work on 10.5.4 and some still occur on my Mac, and even more with some of my colleagues.

If you've seen this problem in Mac OS X 10.5.4 or know of a fix


Reader says Leopard files copied to SMB server remain invisible | Top of Page |

Monday, February 18, 2008

Minqiang Wu reports a problem when he copies a file from Leopard to an SMB (Samba) server:

When I copy a file to an empty folder of a Samba share on Leopard, the file is not visible. Copy a file into this empty folder, it will not show the copied file in the folder. The file is really copied, and it will show up until you 'eject' it and reconnect it.

If you’ve seen this problem

Suggestion for Leopard invisible file problem: turn off IPv6

Wednesday, February 20, 2008

Oliver Block responded to Monday's report of Leopard files copied to SMB servers becoming invisible. Block has seen the problem and offers a workaround:

Regarding the post below, one of my colleagues fixed this problem for a customer by disabling IPv6 on the Leopard machine that is acting as an SMB client.

Turning of IPv6 has also been offered as a workaround to another Leopard bug, problems with seeing Windows shares on the network.

If tried turning off IPv6 for the invisible file problem

Reader verifies turning off IPv6 for Leopard invisible file problem

Friday, March 7, 2008

Clement Shimizu reports that turning off IPv6 fixes the problem where files copied to a Windows server remain invisible:

I just wanted to let you know that I too had a Mac-to-Windows file copying problem (the Leopard invisible file problem) that got fixed using your suggestion of turning off IPv6.

TIP: Turn off IP6 on AirPort station for Leopard file browsing problems

Monday, April 7, 2008

David Josephs had a problem with Leopard browsing for files over an AirPort network. He tried some of the fixes on our Leopard Tips page, but found the solution not on the Mac, but the wireless router:

I changed the Samba file in Terminal tip but this did not work. There have been a lot of tips about turning off IPv6 on the remote Mac machine that did not work for me. What did work was when I turned off IPv6 on my router (changed from Node/Tunnel mode to local-link only on my AirPort Extreme router); all of the other computer shares (PCs and other Macs) immediately showed up in the SHARED section of the Finder. I can now see a Mac Mini, 2 Win XP and one Vista machine on the network now. I can fully browse the shares.

If you've tried this

Leopard can't see certain files on server while Tiger users can

Monday, April 7, 2008

Alexander Gambill is another reader reporting that his Leopard users can't see some files on Windows Servers:

I have a client that is running Leopard on 2 machines that are connected to a Windows domain. Random files that are present on the server will be invisible to the Leopard users, however the users still running Tiger do not have this issue. Once a user on another machine copies the file or folder to the same location, it becomes visible to the Leopard user. The issue has occurred 3-4 times and never involves the same file. This only affects the Leopard users.

If you've seen this problem

More on Leopard not seeing files that Tiger can

Wednesday, April 16, 2008

Alex Pryor responded to previous reports of Leopard users not being able to see certain files on Windows Servers:

Responding to the complaint from Alexander Gambill on Monday, April 7. I have experienced the same behavior of Leopard on SMB shares both from the Windows Server 2003 machines and the CIFS shares on a 10.4.11 server. Tiger clients can see all files and directories but Leopard clients see directories as files or lose files all together. The files remain but are inaccessible by any 10.5.2 machines. I can't limit the problem to the most recent security patch (which did list some samba security elements) because I deployed the patch across all the 10.5 machines at the same time. None of these machines are bound to the Active Directory (all file servers are accessed by password instead).

If you've seen this problem

TIP: Workaround Leopard not seeing files that Tiger can

Thursday, January 22, 2009

Catherine Cotter offered a workaround for reported problems with Leopard users not being able to see certain files on Windows Servers, while Tiger users have no problem. Cotter's tip:

You probably have an update or solution to this problem, but I just wanted to add that my Mac Pro is running 10.5.6 connecting to a Windows 2003 file share and myself (and the Leopard users I support) still encounter this issue from time to time. The following work around seems to deal with the problem-

  1. Via cmd on the Windows server, navigate to the corrupted file/folder.
  2. Use the dir /x /a command to view the short names as well as the Explorer folder names.
  3. Use ren to rename the corrupted folder (using its short name as this is what becomes corrupted) to a new name of less than 8 digits/characters. Now when you navigate (via Windows Explorer) back to the file/folder, it will have the new short name. From there, you can rename the folder to whatever you want, and it will no longer be 0k or inaccessible to Leopard users.

If you've tried this fix

Current news on the MacWindows home page


Problems accessing Leopard from Windows | Top of Page |

Wednesday, October 31, 2007

J. G. Owen's Windows machines could no longer access his Mac after upgrading the latter to Leopard:

I just installed Leopard with a non-clean install but it seems to work OK *except* I can't see the mini from my windows XP machines anymore. The Windows command that used to work was:

net use m: \\JAMES-OWENS-COM\gregor

but now no soap.

Owen posted more about this problem at his blog.

Another report of trouble seeing Leopard from Windows

Monday, November 5, 2007

Jochen Bedersdorfer verifies the problem of not being able to access Leopard shares from a Windows PC:

I got the exactly same problem after upgrading to Leopard from 10.3 on my PPC Mac Mini. The net view on the Windows machine will display my machine \\minime, but trying to mount any shares (which worked before), results in System error 64: "The specified network name is no longer available."

If you've seen this problem with Leopard

A suggestion for enabling Windows to see Leopard file sharing:

Wednesday, November 14, 2007

We've had one suggestion and lots of reports about the problem of Windows PC's no longer being able to access a Mac after an upgrade to Leopard. One reader is experiencing a loss of data.

J. Jason Burford offered a configuration setting suggestion:

I have found a way to make it work.

  1. Make sure you have the correct work group on the Mac. Under Network settings click Advanced; it is the WINS tab. It will not save in Automatic mode you must save a custom location.
  2. Enable SMB sharing.
  3. On the PC (XP) open settings, Accounts, on the upper left hand side is a link to Manage network passwords. Delete the ones that are not workings and re-add them. They are usually:

"SMB MAC Name"
XP user name\administrator
Password

If you've tried this suggestion

A reader named Bee, however, did enable SMB file sharing, as Burford suggested above, but it did not work:

I am also having this issue. I turned on SMB file sharing and trying to connect to my mac with my PC the same way when I still had 10.4 but no go.

Luis Garza said Leopard was configured:

I have the same problem at work. My boss's Windows XP machine and every Windows machine on our network cannot see my Mac after installing Leopard. I've made sure all the settings in the sharing pane in preferences are setup but nothing doing. Before with Tiger, he could access my home directory and external drives that I had shared using Swift Share. I have no problem seeing his machine or any others on our office network.

Dr. Evan Sorokin experiences loss of data.

I have an office medical practice with a Mac Pro tower that was hosting files and PC's around the office linked to it. I never had a problem with TIGER. Installation destroyed the network. The PC's delete files when they try to work with them. Everything is horrible. I went to the Apple Store yesterday and the response from the techs was "What problem?" Their only answer was "Go to the Apple support site and look for help." I am extremely frustrated.

J.P. Norair tried using a custom smb.conf configuration file, without success:

I have a situation where I like to connect to my Mac from my work PC laptop. I had spun my own smb.conf back in 10.2, and it has worked great until Leopard, which eschewed it for a newer template. After adding the line "netbios name = [computer name]" I was able to see the share on the Windows PC, but that's the end of the functionality. When I try to open it in Windows, it simply won't authenticate. (And I do know my own password).

If I use my old smb.conf, it still doesn't work. I'm guessing that there's a bug or simply a lack of foresight in the built-in configuration of the Leopard SMB daemon. I hope the guys at Apple sort this one out sooner rather than later. It's a real deal-breaker for installing the Leopard on any kind of corporate mac.

A reader named Eugenie said file sharing started out working until stopped cold:

I have the same issues as mentioned by Earl Arnett on this page.

Another tip for enabling Windows to see Leopard file sharing:

Monday, June 16, 2008

Arvid Tomayko-Peters sent in another suggestion for solving problems with Windows PC seeing Leopard file shares. He is running the 10.5.3 update, which did not fix the problem. What did work was using a previously reported suggestion (directly above) with the addition of another step:

I tried your suggestion here to get my OS X 10.5.3 Mac to show up on a Windows XP machine. It did not work, but what ended up working was doing the suggestion plus turning off per-account SMB sharing in the sharing options dialog for each account and then turning it back on again. (I had used FireWire to transfer my account from a Mac running 10.4.11.)

Tomayko-Peters added more to this tip directly below:

Update to tip on enabling Windows to see Leopard file sharing

Tuesday, July 15, 2008

Arvid Tomayko-Peters sent a revisal to his June 16 tip for enabling Windows to see Leopard file sharing (directly above). He adds one more setting change to his previous suggestion:

Actually, what seems to have done the trick (in OS X 10.5.4) is to set not only the workgroup in the Network settings > Advanced > WINS tab, but also to enter a custom name for the Mac. It had a pre-generated seemingly random name, but it said that that name was already in use. So I just changed it to something else and set the workgroup to the one in the list and then my mac showed up in Windows XP sharing. I did also disable and re-enable the SMB sharing on each user account as I had done last time I had to do this (in 10.5.3), so I'm not sure whether or not that is also necessary to do.

This tip is in response to reported problems with Windows PCs accessing Leopard shares. If you've tried this suggestion

Another workaround for Vista PC accessing Leopard file sharing

Wednesday, November 21, 2007

Brent Blumenstein offered another workaround for the problem of Windows PCs not being able to log into Leopard file sharing. (There is a previoulsy reported workaround here.) Here, Blumenstein is specifically talking about Vista:

On an XP machine I can logon to a Leopard file share and access the shared files without issues using just a Leopard user name, and this is so whether the XP machine is a member of "workgroup" or some other name. But on the Vista machine a weird syntax is required, and this is true whether the Vista machine is a member of "workgroup" or some other work group name.

Here is the Vista solution I found: When logging on to access the Leopard shares from Vista the user name must be in this form:

DOMAIN\username

NOTE: Capitalization of DOMAIN is essential!

I do not think this has anything to do with the work group name. When I default everything in Leopard it shows up as a member of "workgroup" when viewed from the Windows side, so Leopard is apparently set up to use "workgroup" as the default work group name.

The conclusion about naming work groups in peer-to-peer networking that I had come to even before starting to fiddle with Leopard (my first Mac experience BTW) is that being a member of the same named work group has been de-emphasized on the Windows side (if it ever was an issue): I can connect my XP and Vista computers easily whether they are a member of the same named work group or not. I am simply warned in the docs that discovery might take a little longer.

So, where did the DOMAIN token as required when logging on from Vista come from? Is it Leopard requiring this, or is it Vista?

Meanwhile, I am able to access my Leopard files from Vista (and XP) with approximately the same reliability I am able to share files among my Windows computers.

Note that our Leopard Tips and Reports page has previously reported tip that differs from this one.

If you've tried either of these suggestions

TIP: Solution to sharing Leopard on a Win AD Domain

Friday, March 7, 2008

A reader named Grant sent in a suggestion getting around problems with Windows PCs accessing Leopard shares. The main idea is to create a local user account on the Mac with file sharing already turned on:

For those of us using only domain accounts on our Macs within a Windows Active Directory Domain, we just get used to the idea that we can access the PCs from the Macs but not necessarily so the other way around.

Try this -- it worked for me and now all sharing on all Macs and PCs is working seamlessly:

  1. System Preferences > Sharing > Confirm File Sharing is enabled
  2. System Preferences > Accounts > Create yourself a local user account on your Mac with admin rights
  3. System Preferences > Sharing > File Sharing > Options > Confirm that you are sharing files using SMB
  4. Access your shared folders from a PC > Voila

It appears that by creating the local user account with file sharing already turned on you are initializing the Mac to show itself correctly. You can even now safely go ahead and remove the local account that you no longer need.

If you've tried this

TIP: Iomega NAS firmware update fixes Leopard file access problem

Tuesday, February 5, 2008

Daniel Quarte reports that a simple update fixed his Leopard problem with an Iomega network attached storage (NAS) device:

I'd like to contribute to the Mac OS X 10.5 Leopard Cross-platform Issues page. I bought a MacBook yesterday and encounter the same issues as everyone else trying to connect it to my Iomega NAS. After trying most of the techniques offered in your article with no success, I decided to check on the Iomega website and fortunately I found a simple solution: firmware upgrade. This solution will, obviously, not work for everyone, but might save time for those who have the same NAS. This is a link to the Iomega website about the Leopard problem.

Reader says 10.5.2 doesn't fix problem accessing Leopard from Windows

Friday, February 15, 2008

Adam Radestock says that the 10.5.2 update did not fix Leopard's problem of not being accessible to Windows PCs:

I have been experiencing the same problem as Jochen Bedersdorfer, in that any Windows PCs cannot access my Mac's shared folders and report an error: "The specified network name is no longer available."

This is particularly annoying for me, as I'm the only Mac user in a company full of Mac haters.

I have tried everything under the sun to try and fix this, but to no avail.

I updated to 10.5.2, and cleared out all my shared folders, and started again, but still no luck. I am on an Active Directory Domain, which has worked fine. I think the stumbling block may be that Apple have set Samba up to only authenticate against it's Users list, so when a member on Active Directory tries to log in, it fails.

if how 10.5.2 affects this issue for you.

TIP: To enable Win to see Leopard file sharing, reset Computer Name

Friday, May 9, 2008

Like some other readers, David Tarleton's Windows PC could no longer see networked Macs after a Leopard upgrade. He then discovered the cause:

We just updated our Macs in the office to Leopard, and suddenly, the only Windows machine in the office could no longer log in.

We tried all the suggestions on the site, which were helpful, but the we discovered what actually was causing the problem:

The upgrade to Leopard CHANGED THE NAMES OF THE COMPUTERS. So, the old shortcuts on Windows no longer correctly pointed to the right boxes.

To fix it, go to System Preferences>Sharing>Edit, and make sure that the hostname there is the same as it was before. You can hover over the link on the Windows machine and it will show you. On one of our Macs, we had to restart to make the name change stick.

Once we got the names back, the computers all talk to each other fine.

If you've tried this how well it worked.

TIP: Getting Vista to access Mac file sharing

Tuesday, July 29, 2008

Douglas Cooley in Ontario, Canada sent a fix for a previously reported problem of Windows Vista accessing Mac OS X shared files. He reports:

I had almost the same problem as P. Norair except that I had always used the Windows search feature to find the Mac's shared address in a PC (instead of .smb.conf). Now with my Vista Ultimate install (on a Mac Pro) would not authenticate my Tiger (10.4.11) shares on my iMac. It would show them but refuse to authenticate. I followed the advice given on a web page at Tech Republic and it solved my problems.

See the section after the bold faced Mac Access esp. after the words, "Note that, in some cases, I've seen Windows Vista refuse to process the username/password between the Windows and the Mac..."

It fixed the problem for me but I should emphasize it only applies to Vista Ultimate.

The Tech Republic article includes screen shots of Mac OS X and Windows Vista Ultimate, with directions for both. Here is a section on Vista settings:

To enable access to shared Macintosh resources within Vista Ultimate:

  1. Click Start.
  2. Type secpol.msc in the search box and press Enter.
  3. Windows Vista will display a warning message; click Continue.
  4. Windows Vista's Local Security Policy console will appear. Highlight Local Policies.
  5. Double-click Security Options.
  6. Scroll down to the Network Security: LAN Manager Authentication Level policy entry and double-click it.
  7. Change the value from the default setting of Send MTLMv2 Response Only to Send LM & NTLM -- Use NTLMv2 Session Security If Negotiated, then click OK. (Figure J).
  8. Close the Local Security Policy console.

If you've tried this

Verification of fix for Vista accessing Leopard shares

Friday, August 15, 2008

James Balderson had success with that a procedure we recently reported to fix a problem of Windows Vista accessing Mac OS X shared files. He said simply "Thank you this works perfectly."

If you've tried this workaround

Current news on the MacWindows home page.

New Parallels Desktop 4.0 for Mac Run Windows and Mac apps without rebooting! Now with more 3D Graphics Support, 50% faster, improved Mac OS integration, speech recognition, more notbook battery life, and more. The best of both worlds.

Problems with Windows clients access to Leopard Server on Active Directory net | Top of Page |

Wednesday, November 21, 2007

Terry Druery from Australia reports this problem with Windows clients and Leopard server:

With Mac OS X 10.4 on our G5 XServe, Windows clients could mount a share with no problems using a logon script on the Active Directory server, Windows 2000. We upgraded to Mac OS X 10.5 and then to 10.5.1 and no go. The same user can connect to Leopard Server from a Mac without issues.

Windows machines give an error message about incorrect password in the text window that presents as the logon script is run. Same setup as before. Server not bound to AD users exactly the same passwords the same. The Windows users can log on IF I give them admin privileges in the Workgroup manager. Understandably I am reluctant to do this.

If you've seen this

Windows problems accessing Leopard Server: 10.5 SMB turns off by itself

Wednesday, December 12, 2007

Sourabh Chakraborty has the file sharing problem with Windows clients accessing Leopard Server. He provides some detail:

We've been having similar problems with the Windows file sharing with the new Leopard server.

This is what happens. It looks like the SMB service on the Leopard server turns off on its own and then of course Windows connectivity to the server is lost. Surprisingly the SMB service turns itself back on after some time (anywhere from a couple of hours to six or seven approximately).

If you've seen this problem

Vista accessing Leopard sensitive to case

Wednesday, January 9, 2008

A reader called Ed had the known problem of accessing Leopard files shares form Windows Vista. He took a suggestion for the reverse (Macs accessing Windows), but it worked:

I was unable to authenticate to my file shares on Leopard 10.5.1 from Windows Vista Ultimate. Received eDSAuthFailed messages in my samba log on leopard. I solved these problems by using MACHOSTNAME\accountname instead of using machostname\accountname as was suggested on your website.

If you've seen this work


Manually configured DNS helped speed Leopard networking for reader | Top of Page |

Wednesday, December 12, 2007

A reader named Steve found our discussion of slow network performance with Mac OS X 10.4.10 being related to DNS issues. He saw the problem with Leopard and found a workaround:

I found your discussion titled Mac OS X 10.4.10 update causing net slowdown and other net problems useful. I recently fixed my problem and wanted to share it.

DNS lookups in Firefox and Safari have been slow at home, although it's fine on networks outside my home (such as the wireless network at work). My setup is a Leopard MacBook Pro, although problem also happened on Tiger, AirPort Extreme (n), with separate ADSL modem.

When I got an iPhone I couldn't get a good wi-fi connection. The Mac help forums suggested checking the iPhone's DNS entries, and if the router's IP address was listed, remove it as a DNS address. This fixed my iPhone problem.

As the DNS was assigned (via DHCP, I guess), rather than manually configured, I thought that the same problem might be happening on my MacBook Pro. Sure enough, when I checked DNS in System Preferences / Network, the router IP was listed as the first DNS entry. I removed this IP address and left the other two IP addresses, and DNS lookups in Firefox and Safari have been noticeably quicker since (effectively instant, as they used to be before these problems began).

Current news on the MacWindows home page.


Leopard/Safari crashes with ISA Proxies | Top of Page |

Wednesday, October 31, 2007

John Holley of Auckland, New Zealand, reported problems with Safari crashing when trying to access a remote network through Microsoft Proxy Server:

There is still no adequate support for using a Windows 2003 Proxy Server. The bugs e.g. Safari crashing when trying to connect via a proxy, are still there. Worse occurs nows as iDisk syncing using the proxy settings causing the Finder to lock up/crash!

In Tiger, network apps would crash when trying to use a ISA proxy as set in network settings. The exception to this was Firefox which specifies it's proxy setup in the app and works fine.

Well Leopard is no different, in fact it is worse. Apps like Safari still crash but also as processes like filesync to crash and the Finder get's all screwed up. I cannot fathom why a proxy connection causes OS X apps to crash. I'm am hugely disappointed that Apple has not fixed this known bug from Tiger. After all, if Firefox has no problems, how hard is this to fix?

The problem relates to HTTP Authentication. It is a significant barrier to Macs in Windows shops using ISA in a more secure mode.

If you've seen this problem with Leopard

More Leopard problems with ISA Proxy, and a workaround

Friday, November 2, 2007

More readers reported problems with Safari crashing with Microsoft ISA Proxy connections. Several readers said that the problem does not occur with the FireFox web browser.

Robert Carper recommends a third-party program:

I've had the same problem with Safari in Leopard crashing when attempting to access secure sites through our ISA proxy server. In the early days of OS X I had used Authoxy from HRSoftWorks to get functional proxy access. I just tried that again tonight and it does seem to work nicely in Leopard. I've gone to a few secure sites with no issues at all.

Rick Shields only crashes at one web site: Apple's .Mac:

I to can confirm that my Safari crashes when going through the MS ISA proxy. But it is not all the time. It happens exclusively when I try to log into my .mac mail via the webpage. So far that is the only page. And I can confirm the syncs for .mac are not working either.

Brent Westmoreland saw the problem with Tiger, and says it's worse in Leopard:

There is still no adequate support for using a Windows 2003 Proxy Server. The bugs e.g. Safari crashing when trying to connect via a proxy, are still there. Worse, as it now occurs as iDisk syncing using the proxy settings causing the Finder to lock up/crash! In Tiger, network apps would crash when trying to use a ISA proxy as set in network settings. The exception to this was FireFox, which specifies its proxy setup in the app and works fine.

Leopard is worse. Apps like Safari still crash but also processes like filesync crash and the Finder gets all screwed up. I cannot fathom why a proxy connection causes OS X apps to crash. I'm hugely disappointed that Apple has not fixed this known bug from Tiger.

The problem relates to HTTP Authentication. It is a significant barrier to Macs in Windows shops using ISA in a more secure mode.

This author is right-on and the problem did persist through 10.4. When you place a Macintosh behind an ISA proxy you inevitably get prompted relentlessly, applications crash and the entire system takes on an unstable feeling. In 10.4 it was possible to use squidman ( http://homepage.mac.com/adg/SquidMan/index.html ) as a local caching proxy and configure the ISA box as an UPSTREAM proxy. This is a mildly complicated workaround, but solved a lot of headaches. Unfortunately, squidman will not be ported to leopard for a few more weeks and my success at compiling squid from source on 10.5 has been disastrous thus far.

Daniel, like the previous reader, found that FireFox works:

I'm experiencing the same issue, on my company network I cannot connect via the ISA proxy server when using Safari. on the same system using either: Firefox within OSX 10.5 or MS Explorer within Parallels and Windows XP no problem! the problem has actually caused Safari to crash several times, reset did not help.

The same system worked fine under 10.4.

For older reports on Microsoft Proxy Server, see our Macs and Microsoft Proxy Server Special Reports page.

Reader verifies tip about Windows ISA Server and Leopard

Wednesday, November 7, 2007

Brent Westmoreland updated his report from last Friday about Leopard problems with Safari crashing with Windows ISA Proxy Server with a note verifying a tip from another reader:

Authoxy is indeed a success! Thanks for the tip.

Rick Shields updated his previous report saying that the problem occurs with more web sites than he first thought, and reports a bug with QuickTime:

I can verify that the problem occurs with a lot more than just Apple's page. The first “standard” 20 pages I go to a day seemed ok, but now tons more don't work.

I have tried Authoxy in the past and never got it to work.

Apple also has not fixed the QT via Proxy either...I had submitted a bug to them last year on that via the developer side. Everything works on a Windows box but if you go to a Mac a lot of times you get the QT ? instead of the QT movie. The issue seems to be they use QT with anonymous connections. Which in our case, using an ISA proxy requiring passwords won't work.

Current news on the MacWindows home page.

Another workaround for ISA Proxy problem in Leopard

Monday, January 14, 2008

Andrew Kingdom has the problems with Leopard's Safari crashing with Microsoft ISA Proxy connections. He also sees the problem with Software Update. Other browsers don't seem to have the problem:

I have both Safari and Software Update crashing under Leopard (10.5.1) when they attempt to authenticate to Microsoft ISA Server 2006 (version 5.0.5720.100) or Microsoft ISA Server 2004 (version 4.0.2163.213). They are crashing with proxy authentication, not authentication on a website (it's not even getting as far as the Internet).

Firefox, however, works fine. I also tried Microsoft's ancient Internet Explorer 5.2.3 for Mac, which works fine. So it seems to be Apple's own authentication that is crashing when confronting MS ISA proxy. Ironically this also means Apple isn't receiving crash reports from us (as they would have to go through the same proxy).

This crash occurs on the Intel Mac minis I'm testing, both when they are bound to Active Directory, and also unbound. It doesn't occur with a direct Internet connection (no proxy).

There are other workarounds above.

TIP: Fix Leopard ISA Proxy crashes with a reinstall

Monday, January 21, 2008

Vincent Kroll solved his problem with Leopard/Safari crashing with ISA Proxies by reinstalling Leopard in a particular way:

I've had the same problem. But after reinstalling the system software (while the Macs are connected to the affected network) with system archiving options, my problem was solved. I've reinstalled 5 Macs (3 Mac Pro and 2 iMacs 24" Mid 2007), all these Macs are running fine now. Strange, but it works.

Security update may be behind Leopard's Safari and Software Update with ISA proxies

Wednesday, January 23, 2008

Andrew Kingdom said that a recent security update is the cause of Leopard's problems with ISA proxies, which causes Safari and Software update to crash:

I've further tracked down the culprit with the issue I previously reported. It appears as soon as OS X "Security Update 2007-009" (1.1) is installed, not before.

Recently, a reader reported that reinstalling Leopard made the problem disappear. This would be the case if the bug is with the Security Update, as the reinstall would erase the update.

If you can confirm or refute that the Security Update 2007-009 is the cause of the crashes with ISA proxies

Reader agrees, security update causes Leopard ISA Proxy Safari crash

Monday, January 28, 2008

Charles Burton corroborated the previous report that the ISA Proxy Safari/Leopard crash may be caused by a recent Leopard security update:

I am experiencing the anomaly of Safari crashing when our ISA proxy settings are in place in the OS. This only began recently therefore I would affirm that it is likely a security patch that has caused this issue. My Tiger machines are operating normally but the Leopard machines crash Safari. Other Internet access applications like Apple Update function normally.

Current news on the MacWindows home page.

Readers reports 10.5.2 update fixes ISA proxy problem

Wednesday, February 20, 2008

Andrzej Pawelczyk in the UK says that 10.5.2 fixed Leopard's problem with ISA Proxies. He also verified another report that it was a Leopard security update that caused the problem. Pawelczyk said:

In our network we are using ISA 2006 as a proxy server. I have noticed that Safari (using proxy) was working fine with Leopard 10.5 and 10.5.1. After I have installed Security Update 2007-009 v. 1.1 Safari and Software Update start crashing with proxy settings. The good news is that after installation of 10.5.2 update problem with proxy not existing any more. So looks like they fix it and it work for me.

If you can comment on the 10.5.2 update's effect on ISA Proxy issue

Safari crash under MS ISA proxy continues under 10.5.2

Monday, March 3, 2008

Dr. Duncan Lamont of Scotland says that the Leopard problem of Safari crashing with ISA Proxy continues in Mac OS X 10.5.2. One reader previously reported that the 10.5.2 update fixed the problem. Lamont reports otherwise:

Simply adding my support to the Safari crash problem. I have never been able to persuade Safari to run without crashing on our NHS intranet connection. A MS ISA proxy is used and I've tried numerous work-arounds including applications that set the mac as a proxy itself then connect using their own protocols to the ISA proxy. None have worked under any flavour of OS X at least for the last 3 years. I am using 10.5.2 currently, which was a clean erase and install version so I can't blame it on any inherited settings from Tiger. Firefox however is reliable and connects without issue when separately configuring its proxy.

The most annoying thing about this is it prevents me using the Citrix web client on my Mac since this uses Apples own proxy settings to connect through the ISA proxy. As such, it doesn't work either. When I need to use the Citrix client, I end up using a vodafone datacard to establish a separate connection. I am very surprised that such a long running problem that is so easily replicated could be left unfixed for so long.

Safari working through MS ISA Proxy with 10.5.3

Friday, May 30, 2008

Duncan Lamont reports that the Leopard 10.5.3 update fixes a problem with Safari crashing when accessing Micrsoft ISA Proxy. The update doesn't fix, however, a problem he has with the Citrix client for Mac. Lamont reports:

This is a followup to my previous account of years of frustration trying to persuade Safari to work through a MS ISA proxy. I am very happy to report that the 10.5.3 update has finally fixed the problem. Previously Safari and anything else that relied upon the network preferences for proxy configuration and authentication would crash or fail to authenticate with the secure proxy. Firefox worked reliably despite this since it used it's own proxy configuration. I had given up hope of this ever being fixed so I was surprised when the 10.5.3 update fixed the problem. Not only does Safari function fine, the widgets on dashboard now function as expected when connected through the proxy.

However, I still haven't managed to persuade the Citrix secure client to work through the MS ISA proxy on a Mac, it works fine without a proxy and with Windows XP through the proxy.

If you've seen this problem whether or not the 10.5.3 affects it.


Repairing Disk Permissions in Leopard broke Safari 3 | Top of Page |

Wednesday, November 7, 2007

Anyen Ho reports that running Repair Disk Permissions in Disc Utility affected Safari 3 negatively:

I found a weird issue with Safari 3 in Leopard. I am using leopard on a MacBook Pro 2.2 GHz santa rosa. The disk utility found incorrect code, but after it fixed the incorrect code, friendster.com can't enter the new comment, new friend request. It worked before repairing disk permissions. Is Leopard or the dsik not compatible with OS X applications? It is fine with Netscape and FireFox, though. Weird.

If you've seen this problem

Current news on the MacWindows home page.


TIP: Make Leopard faster | Top of Page |

Wednesday, November 7, 2007

Albert Mowatt forwarded us Unix command to run in Terminal that to improve the performance of Leopard:

After an upgrade on several machines I noticed that the machines were sluggish, like a just fed cat. More than a few opened sometimes slower than Tiger. Then I remembered a fix!

sudo update_prebinding -debug -root / -force

Input your admin password (or root if your have a root). Whatever it takes to get the sudo working. Afterwards, run a few programs to test. They will spring to life. I noticed a few (acrobat, safari) still had to be opened at least once then from there on; Watch out.

Besides, it's never a bad idea to update your prebinding anyway.

We recommend backing up before using this procedure.

Current news on the MacWindows home page.


Leopard Mail 3.0 problems with Exchange OWA/IMAP | Top of Page |

Wednesday, November 14, 2007

Posts to the Apple discussion forums are reporting problems with Leopard's Mail 3.0 accessing Exchange Server via IMAP, something that previous versions of Mail can do.

Chenoa Osayande found a potentially useful new feature in Mail 3.0 regarding Exchanage but can't get it to work:

I noticed that Leopard Mail now has a box for OWA, but I have not been able to get it working. This feature is available in Microsoft Entourage, as you are probably aware. The neat thing about it is that it allows you to enter the OWA settings in Entourage and be able to receive and send mail without having to be on the corporate network via VPN, or be concerned about proxies.

I called Apple support, and the rep read from a manual and told me that this is now supported, but it definitely does not work the same in Mail as it does in Entourage. This is the last thing that is holding me back from ditching Entourage.

If you've had problems with IMAP in Leopard Mail, or have a suggestion for OWA,

A review of Leopard Mail 3.0 with Exchange Server and IMAP: slow initial connects, faster IMAP

Monday, November 19, 2007

An anonymous reader (identified as "Macguitarman") commented on a previous report about Leopard's Mail 3.0 when using with Exchange Server and IMAP. The previous reader said "Leopard Mail now has a box for OWA, but I have not been able to get it working." Macguitarman replied with a review of what works and what doesn't with Mail 3.0 and Exchange:

I do not think this OWA functionality ever worked in any version of Mac OS X Mail.App, 1, 2 or 3; it only works in Entourage.

IMAP works fine in Mail App 3, Leopard 10.5, when connectingport 139 to Exchange Server (at least I know our environment, Exchange 2003). There are issues however,

What's Broken

When initially setting your Exchange account in Mail App 3, whether you input the actual IP address or DNS name of the Exchange server, it can take 2-10 minutes to connect, for both the Incoming mail server and SMTP settings. This was instantaneous in 10.4, Mail App 2. I'll try it again in 10.5.1, we'll see.

Since there are still Active Directory Binding issues with 10.5 and still in 10.5.1, email address name lookup in Mail App was not working in 10.5, seems to work on and off in 10.5.1, again related to 10.5.1 Binding to AD and staying bound to AD.

What is Fixed

-- Mail 3.0 in 10.5 is much faster when connecting to Exchange servers either via IMAP or Exchange pull down (Note, the "Exchange" pull down is not MS's MAPI, it is IMAP plus WebDav.) Since we are on the same version of Exchange Server 2003, I assume Apple has done something within Mail App that speeds it up, updated IMAP code, who knows.

-- The folders in Mail App when clicked, no longer disappear, upon Mail App 3 setup, your mail comes down from the Exchange Server and populates your folders, rather quickly as opposed to Mail App 2.

In Mail App 2, when you clicked to another mail folder within the Exchange account or another account (say .Mac), one's email subject headers would disappear from the list and take 30 seconds to minutes to refresh. This would give the user the impression that their email was deleted, but it was just jokingly slow in updating / filling the view.

In Mail App 3, no matter where you click, your mail (subject headers") never "disappear" from the viewer, while all activity is going on in the background. This is great.

-- There is a Mail Activity indicator / bar in the lower right pane, to verify activity, also good (Apple-0 still also provides the Activity Window)

I'll have to try just inputting the OWA settings, with no other settings and see if this works, but it never has in the past.

what you think of Leopard's Mail 3.0 and Exchange Server.

Readers on Leopard 10.5.1 Mail/Exchange syncing problem

Monday, November 26, 2007

Two readers responded to a report from last week about problems with Leopard's Mail 3.0 taking a long time to connect with Exchange Server. One reader said the problem still occurs with the Mac OS X 10.5.1 update; the other said the update fixed the issue.

Greg Stasko agreed with a previous reader that the issue still exists:

I'm running into the issue where it takes quite a while to establish a connection from Leopard 10.5.1 Mail with the Exchange Server. I connect to my company network via the Cisco VPN client, and that connection will occur, as expected. However, my mailbox stays offline. I know, though, that the connection is working, because I can access the intranet and mail via a browser.

The account is defined just as an IMAP account, not Exchange. And I did not have this problem pre-Leopard.

Eric Likness believes that the 10.5.1 update fixed the problem:

I had the same issues that Macguitarman had with Apple Mail and Exchange 2003. Headers would disappear, it would take forever to update. Similarly, things have been quite a lot better with Apple Mail 3. However, I saw some similar issues with Apple Mail 3.0/10.5 until the 10.5.1 update. This was related to the Exchange InBox syncing:

Everything works with Exchange 2003 using Apple Mail's Exchange account setup dialog boxes. However under the 10.5.0 there was a continuous syncing being done every time Apple Mail would check the Exchange 2003 Inbox, whether or not anything had changed, it would sync up every message. As a test I also setup the same account as IMAP, and it still did this full sync every time you opened Apple Mail. I didn't see this behavior with a Unix based IMAP account so I began to suspect it was how Exchange IMAP works.

With the 10.5.1 update, Apple Mail now just does a quick check to the Exchange email using IMAP settings or the Exchange account settings. Both sync once when setup then just check periodically to see what has changed since the last time it was checked. So the continuous background syncing has stopped with the 10.5.1 update.

Current news on the MacWindows home page.

Reader problem: Mail.app won't sync with OS X Server, and a resolution

Wednesday, March 5, 2008

Jason Lisi reports that Mail.app on his Leopard MacBook Air doesn't sync with Mac OS X Server's IMAP server. Readers have reported some other Leopard problems with IMAP servers, but these had been with Exchange Server. Lisi also resolved the problem:

I have an IMAP server (XServe running OS X Server Tiger) for my mail, iMac at the office running Leopard, MacBook Air for the road running Leopard.

The iMac, connected at all times to the Internet, syncs with the IMAP server perfectly; changes made on the iMac are reflected on the IMAP server. When the MacBook Air is connected to the Internet, same result.

However, when I am on the road and not connected to the Internet and reading my mail, the changes I make (deleting spam, filing messages in subfolders) do not get synced with the server. When I connect the MacBook Air to the 'net, all the deleted messages repopulate my inbox and the filed messages become un-filed back into the inbox.

When I had used a PowerBook G4 running Tiger, offline changes to Mail would work just like it would if connected.

After a few hours' worth of testing on this issue, I believe it has resolved itself. I decided to download Thunderbird and set it up with the identical settings to Mail.app. After going through the IMAP sync and downloading my gsigs of email messages, I tested Thunderbird, finding it to work properly.

Oddly, then Mail began to behave. I have to assume that using another IMAP client must have affected a cache somewhere, but can't put my finger on the issue.

If you seen this or other issues with Mail.app and IMAP

Current news on the MacWindows home page.


Prosoft NetWare client incompatible with Leopard; upgrade now available

Thursday, November 29, 2007

Emily Herndon notes that the Prosoft Engineering NetWare client doesn't work in Leopard:

I just updated my loaner iBook G4 (for work) to Leopard this weekend without realizing that Netware Client for Mac isn't compatible. So now I can't access the servers that I need to, and I hear that there is no fix from Prosoft for a while.

Prosoft Netware Client for Mac beta out

Wednesday, December 19, 2007

Emily Herndon previously reported that the Prosoft Netware Client for Mac was not compatible with Leopard. She now reports that a beta is available:

Prosoft engineering now has a beta update of Netware Client for Mac. It solves the bug with Leopard.

Prosoft NetWare Client 2.0.1 update adds Leopard support

Monday, April 28, 2008

Prosoft Engineering has released NetWare Client for Mac OS X 2.0.1, and update that adds full support for Mac OS X Leopard. The update is a free download to owners of NetWare Client 2.0.

The Prosoft NetWare client previously was incompatibile with Leopard. This current version has been in beta since December

Current news on the MacWindows home page.


First reader reports on 10.5.2 update: Win browsing fixed, file sharing still broken

Wednesday, February 13, 2008

Our first reports from readers about the Leopard 10.5.2 update describe problems that are fixed and those that aren't. Two readers report that browsing for Windows shares now works, but one reports that logging on to the share is still a problem. Another reader reported that he still can't create mobile directories in Active Directory:

Noah Aboussafy said that share browsing works in 10.5.2, but the file sharing problems is not fixed. He tried most of the suggestions described on our Leopard Tips and Reports page.

Leopard 10.5.2 does not fix the file sharing problem with Windows. I've tried many of the suggestions described at MacWindows, including:

  • Turnning IPv6 off
  • Turnning off, and on and off SMB sharing
  • Editing smb.conf
  • Adding hosts entries
  • Creating a new network location
  • Adjusting the subnet mask
  • Turning off both systems firewalls

10.5.2 will still not connect to SMB shares on my PC, it DOES show up in the side bar now but it simply won't connect and the "connect as" button does nothing.

Jason Lambert also reported that browsing for Windows shares now works with the 10.5.2 update. It also fixed a permissions problem he was having:

I had two specific issues that have resolved themselves since the 10.5.2 update.

1. All of the computers on my network with shares (2 XP Pro, 1 Vista Ultimate, 1 Mac Mini, 1 MacBook) now show up in the left-hand "SHARED" list of the Finder window consistently. Previously, only my Mac shares would consistently show up, even though I always have a Vista share connected on my desktop (showing up as a shared drive icon). With 10.5 and 10.5.1 I would have to choose "Connect to Server" to see these shares because I usually couldn't browse for them.

2. The big issue for me has to do with credentials. My Vista machine contains a large network share with Music, Pictures, and Videos (the default "My Documents" folders). With 10.5.1, even though I entered my Vista admin credentials while using "Connect To Server," I didn't have full write/change access to the root of these folders (the folders even used to show up with the padlock mini-icon on them). After 10.5.2, it appears the credentials are being passed correctly as I can now create folders and files at the root of these directories (and no more padlock).

It's just brilliant to have no-hassle access to my PC-based network with Leopard now.

Jonathan Pittman still can't create a mobile home directory in an Active Directory environment;

I attempted the suggestion that says to go to the search policy and add the specific domain the computer is in. When I click the "+" button to add, it is empty. I only have "Active Directory/All Domains." I do not have my specific ad domain listed. Furthermore, I cannot find anywhere to enter my domain information manually.

Binding to the domain was never a complete problem for me. It would spin and spin and spin, but would eventually bind. I now have Mac OS X 10.5.2. Again, binding is not an issue, but I cannot create a mobile home directory. I had this issue with 10.5 and 10.5.1. Oddly enough, I have another computer with 10.5 that was able to bind and create a mobile home directory.

whether Leopard 10.5.2 fixed any of these issues for you.

Current news on the MacWindows home page.

Readers report Leopard file sharing issues persist after 10.5.2 update

Friday, February 15, 2008

Enrico Luca is still having problems with accessing hidden shares:

I downloaded the update last night and tried accessing our hidden shares on the Windows 2003 servers at work. (These shares have $ signs in their passwords/addresses). Still no luck. The non-hidden shares appear automatically in the Finder. No problems there.

David Searles found that the update fixed file browsing only temporarily:

When I first installed the Leopard 10.5.2 update, I saw every one of my Windows PCs and was able to access shares and was a very happy camper. I said to myself, FINALLY Apple has fixed this mess.

Well, all it took was for me to boot my iMac the following day and voila, the entire Windows network is gone AGAIN! One would think it shouldn't be too difficult to see what they changed between Tiger, which worked, and this Leopard mess.

Current news on the MacWindows home page.


Leopard 10.5.2 and MS DFS support

Monday, February 18, 2008 [updated 10.30 am pst]

Joseph Swenson reports that Apple added partial support of Microsoft's Distributed File System (DFS) to the Leopard 10.5.2 update:

By pure random chance I have discovered that Apple, clever monkeys that they are, have snuck MS DFS support into 10.5.2. It appears to be limited at the moment, as Access-based Enumeration isn't working, and neither are permissions (I don't have access to diddly squat, even though I should), but it's a start.

Josh Wisenbaker disagrees:

There is no DFS support in 10.5.2. Access-Based enumeration is also a totally server side process. The server decides what to present based on the ACLs and the identity of the user logging in. It has nothing to do with the client at all.

Microsoft describes Access-based Enumeration like this: When Access-based Enumeration is enabled, Windows does not display files or folders that a user does not have the rights to access.

If you can confirm Swenson's report


Reader: Leopard 10.5.2 broke my NAS access

Monday, February 25, 2008

Mitchell Fulkerson was doing okay with Leopard until he installed the 10.5.2 update. Now he can't connect to his network attached storage device:

Leopard was working fine on my network, connecting to Windows machines, but my Maxtor NAS device, but as soon as I applied the Leopard 10.5.2 patch, I can't connect (or even see) my NAS device or windows machines.

I know everything is still up and running because my windows machines can see and access it.

The update was supposed to fix a lot of things, like the transparent menu bar, etc. Just now I can't see my local windows network or NAS device.

Earlier this month, another reader reported that an update from Iomega fixed a similar problem with an Iomega NAS device.

If you’ve seen this issue with Mac OS X 10.5.2

Current news on the MacWindows home page.


Reader's Mac usurping network's DHCP server

Tuesday, March 25, 2008

Shon Hall's Mac is handing out IP addresses to PCs, and the network admin is not happy:

Suddenly, my MacBook Pro is acting like it's the DHCP Server at my work's Windows network. All I do on my laptop here is access the network, mostly for E-mail and browsing. I've been connected fine to this network over wireless and Ethernet for over a year and a half with no issues.

Now, suddenly, the IT person is telling me I have to take my laptop off of the network, because it's handing out DHCP addresses when clients need to renew their lease, and his Server backs off thinking there's someone else doing it. Oddly, I can connect somewhat halfway via wireless, but that is not really connecting to their network, and cannot see their shares. I haven't changed any of my settings at all. MacBook Pro 17" 2.14 GHz Core Dou 2 GB RAM OS X 10.5.2 (with all current updates).

If you've seen this or can offer advice

Mac’s Internet Sharing can cause bad DHCP behavior

Thursday, March 27, 2008

Several readers responded to a report of a Mac usurping network's DHCP server with the same suggestion. Christoph Sahm:

Shon Hall probably has turned on Internet Sharing in the System Preferences. This causes Mac OS X's built-in DHCP Server to start handing out IP addresses.

Joshua Galvez:

I imagine Shon probably has Internet Sharing turned on. In Leopard it is found in the Sharing pane of System Preferences.

Jeff Dyck and Doug Trickey also suggested the same.

Shon Hall, however, said that wasn't the problem:

That's one of the places I looked. The only thing I have turned on there, is File Sharing, and Bluetooth Sharing... Neither of which looks like it hands out any IP Addresses.

Chris Vavrinek suggested another possibility:

Your Network Admin just wants the big bad Mac off his network. Could be because it is a personal computer rather than a company laptop. If you wanted to push his buttons ask him for the Mac Address of the machine that is handing out DHCP addresses, compare it to yours if he can produce it. If you are running Mac OS X and not Mac OS X Server I do not think this is possible. You would have to hack a lot of Unix files to get DHCP to magically start handing out addresses. Get a Sprint or Verizon Card and get your mail at work through that.

Current news on the MacWindows home page.

Reader suggests AirPort at fault for Mac giving out IP addresses

Tuesday, April 1, 2008

Doug Trickey added to previous suggestions as to why a Mac would give out IP address on a network. Trickey says a misconfigured wireless router could be the cause:

Another possibility is this person is using an Airport or other router that is misconfigured. This actually happened to me recently. I had been using an AirPort Express at the elementary school where I teach for a couple years when the tech people complained that it was serving IP addresses. To fix the problem, I configured it in bridge mode.


Leopard Security Update disconnects mounted shares

Tuesday, March 25, 2008

After Anton Schep installed a security update in Leopard, mounted Windows shares disconnect after a few minutes:

I have been using "Connect to Server" to mount a SMB share from a Windows 2003 without a problem since I upgraded to Leopard (which resolved the digital signing issue). However as of Monday, which coincides with me having applied the latest Security Update, I can no longer keep the share mounted longer than about 5 minutes. Then it disconnects and I cannot reconnect at all. After a restart I can reconnect and it appears that after a couple of hours I can reconnect again, but in both cases I get kicked of after 5 minutes. Linux machines don't have a problem mounting the same share.

There was also another report of a similar disconnect problem last fall. Click here to view.

If you've seen this problem

Current news on the MacWindows home page.


Reader says Leopard 10.5.2 did not fix AFP file share problems

Monday, April 7, 2008

Although Apple stated that the Leopard 10.5.2 update addressed problems with accessing AFP shares, Kevin Schanely reports that he still sees problems:

This issue of file sharing from Leopard to Windows 2003 apple shares is STILL not resolved in our Mac/Windows school environment. We have plenty of Macs that run Tiger 10.4.11 and connect via AFP to our Windows 2003 Server shares just fine. Leopard, however, is still a problem even after the 10.5.2 update patch.

Third-party developer Group Logic has previoulsy reported that Leopard contained bugs in the AFP protocol.

If you're still having AFP file sharing access after the 10.5.2 update

More on Leopard AFP problems with Windows 2003 Apple shares

Wednesday, April 16, 2008

Two more readers reported on Leopard's AFP file sharing problems with Windows 2003 Server. Kevin Schanely, who first reported the problem, said that Apple suggests using clear text passwords, which are not secure:

I heard back from Apple today and the solution at least for our problem comes from the Windows Server 2003 side. Changing the enable authentication on the File Server for Macintosh shares to "Apple Clear text or Microsoft" seems to have fixed the issue of connecting to Apple shares located on a Windows 2003 x32 server.

Jeffrey Belmonti verified that the problem occurs with Windows 2003 and not Windows 2000:

I am too having problems. We recently moved our server to Win 2K3 and now I can read files, connect and view files, even open files, however it appears that connection is lost soon after and auto saves fail. When I try to save the file it states that I do not have write permissions. Leopard with Win2K Server worked perfectly but there seems to be some quirks with Win2K3 Server and Leopard.

Leopard's AFP file sharing with Win2003 Server: can’t change passwords

Friday, May 23, 2008

Brendan Geary is another reader reporting problems with Leopard and AFP file shairing. However, where one reader found a workaround in clear text, Geary did not:

I'm seeing a Leopard AFP file sharing problem with Windows 2003 Server. On the server side, when I change the enable authentication on the file server for Macintosh shares to "Apple clear text or Microsoft" I am no longer to change AD passwords on 10.4. I cannot change the password on 10.5 no matter how authentication is set on the file server.

If you've seen this problem


Leopard inserting AFP in front of SMB server paths, and a workaround

Monday, October 6, 2008

Ed Chavez is having a problem with accessing SMB file shares in Leopard, but found a way around it:

I was able to successfully bind the Mac to Active Directory but when I would try to connect to server it would always fail. The error indicated Finder was adding an AFP prefix. In other words, I would type in smb://servername/share which would fail. The error message would say cannot connect to afp://smb://servername/share.

Enabling and disabling file sharing had no effect. I was able to resolve this by using the Kerebos application found in Core Services. I had to manually add a Kerebos ticket for the user. Once I did, Finder no longer added the AFP prefix.

If you've seen this problem

TIP: Simpler fix for Leopard inserting afp:// in front of smb addresses - don't use backslashes

Monday, October 13, 2008

Jonathan Hutchins sent in an easy fix for an issue with Mac OS X inserting afp:// in front of an smb:// path in the Connect to Server dialog (Go menu):

There is a simple solution:

smb://<servername> works.

smb:\\<servername> will cause OS X to insert the afp:// prefix (and won't work).

We note that Mac OS X will turn the backwards slashes in the correct (Unix) forward slashes. (Why it adds afp:// is a mystery to us.) We also note that this behavior is not limited to Leopard, but occurs with Tiger (10.4) as well.


LEOPARD 10.5.3

Leopard 10.5.3 update fixed reader's cross-platform printing issue | Top of Page |

Tuesday, June 3, 2008

Larry Hanes said last week's 10.5.3 update fixed a Leoaprd problem printing to a Windows server printer:

The 10.5.3 update fixed my cross-platform printing issue. Ever since I bought my new MBP with Leopard in April, I have been unable to get it to print to my HP LaserJet 6MP connected to my Windows 2000 SP4 system. I installed 10.5.3 and immediately was able to print to my printer.

how the 10.5.3 update affected your cross-platform Leopard-specific printing issues.

Reader verifies Leopard 10.5.3 update fixed a cross-platform printing issue

Friday, June 20, 2008

Katy Franz verified a previous report that the Mac OS X 10.5.3 update fixed a printing problem:

After months of frustration and listening to the ridicule from my Windows/Linux-biased husband, I found your site today and saw that the latest update might fix my printing issue. Sure enough, it prints just fine now. I was able to print in February but then whatever they did, broke printing. I've been printing from my daughter's PC for months. I was ready to take the MacBook back.

Another reader says Leopard 10.5.3 fixed net printing issue

Friday, June 27, 2008

Paul Gardner-Stephen agreed with a previous reader that the Mac OS X 10.5.3 update fixed a cross-platform printing issue:

Just to let you know 10.5.3 has solved our problems with printing to a Samba print server. In the past printing using lp from the command line would work, but the GUI print dialogs would hang. Now it all works beautifully.


Leopard 10.5.3 bug with AFP servers can corrupt Adobe CS3 files | Top of Page |

Monday, June 9, 2008

Group Logic reports that the recent Mac OS X 10.5.3 update can corrupt Adobe CS3 files located on AFP file servers. This can occur with Mac OS X Server, Group Logic's ExtremeZ-IP, or other Windows and Unix-based AFP servers. Posts in discussion forums around the Internet report the problem with Photoshop and Indesign.

Group Logic recommends either delaying updating Leopard to version 10.5.3, or to only work on Adobe files from the local hard disk. Since Adobe CS3, adobe has been recommending not opening files that reside on file servers.

If you know of another workaround

We’ve also had a report today of Photoshop CS3 file saving errors with Mac OS X 10.4.11 and an SMB file server.

Update, July 3, 2008

In the notes for the Mac OS X 10.5.4 update (see above), Apple said that the update fixes the Adobe/server problem.

Current news on the MacWindows home page.

Leopard 10.5.3 bug causes crashes with Firefox, other Mozilla apps | Top of Page |

Monday, June 9, 2008

Apple's recent Leopard 10.5.3 update contains a bug that conflicts with Mozilla-based applications, according to ArsTechnica, MacNN, and other sources around the Internet.

The bug causes the Mac OS X system to crash when Mozilla applications are installed or freeze when an attempt is made to shut down the Mac. The affected applications include Firefox and Thunderbird.

Today, we reported that Mac OS X 10.5.3 also contains a bug with AFP servers can corrupt Adobe CS3 files.

Apple has said that the 10.5.3 update fixed several hundred bugs. Apple listed a number of cross-platform bug fixes, including issues with Active Directory and connecting a Microsoft ISA proxy.

Current news on the MacWindows home page.


Leopard 10.5.3 kernel panics with SMB driver in AD, and a workaround

Tuesday, June 24, 2008

Peter Kloss is seeing kernel panics with the Leopard 10.5.3 update. He pinned it down to the SMB driver when logged into an Active Directory domain. Backgrading to the 10.5.2 driver fixed the problem:

Having previously said that 10.5.3 fixed AD binding problems, but some other things have come to light about 10.5.3 that are not so good!

If you log in as an AD authenticated user, the SMB driver manifests in slow connection times and the system crashing after about 2 hours of use or on logoff (when it is attempting to disconnect network shares) or on shutdown (when it is doing the same). The symptom is the "black screen of death" - you know, the pretty one with white writing in Japanese telling you to hold in the Power button. I've been using a network home directory, which guarantees heavy use of the smbfs driver.

In desperation I got the smbfs.kext out of the 10.5.2 disk image I saved before applying 10.5.3 and replaced the newer one with it -and after two days I've had not one black screen. I've not had any panics and it is really fast, but not fast enough for Entourage 2008 to run its message store (I've had to move that to a local drive).

Looking at the kernel panic log it is between smbfs.kext and mdworker (spotlight), I can see that even with the 10.5.2 driver, there are console messages about memory allocation errors every time a network drive is accessed.

If you've seen this

Reader's Leopard 10.5.3 kernel panics stop with Time Machine off

Monday, June 30, 2008

Peter Jones responded to our report about kernel panics that started with Leopard 10.5.3. Although the previous reader isolated the problem to the 10.5.3 SMB driver, Jones found that TimeMachine was a problem:

I have been having kernel panics on my PowerBook G4 (1.67GHz, 1.5GB RAM, 250GB HD) since installing 10.5.3. The symptoms are similar to Peter Kloss' except that I am not logged into an Active Directory server. However, I am (was) using the "unsupported drives" workaround to maintain Time Machine backups to a WD Netcenter 160GB network hard drive (via Verizon FIOS wireless router). I have been frustrated with 3-to-5 kernel panics per day (this is a production machine so I have to just grit my teeth and hit command-S a lot) but after seeing Peter Kloss' comment and thinking about it I simply turned off Time Machine. All KPs have stopped for 36+ hours.

The crash reports were all very similar in that the processes crashing were either "mds" or "update". These are both file system intensive and it is possible that this is an artifact similar to what Mr. Kloss is experiencing.

If you've seen this problem

Current news on the MacWindows home page.


Adobe SMB file saving errors with Leopard Server 10.5.3, and workaround

Tuesday, June 24, 2008

Carl Haynie responded to a report about Photoshop SMB file sharing errors. He has a similar-sounding problem with Adobe FrameMaker and Leopard Server. His workaround is to use AFP with strict file locking turned off:

Our company recently upgraded our Mac OS X Server to 10.5.3, turned on SMB on our file share, and turned off strict file locking to improve performance.

One of our client Macs, running 10.5.3, runs Adobe FrameMaker. This user now reports frequent problems saving to the file share using this application (similar to what Erik Zimmerman reported on June 9). In our case, FrameMaker's error message relates to problems writing imported graphics in the document being saved.

We've got a workaround in place where we've fallen back to using AFP with Op Locks enabled (strict locking is off) on the server. This seems to work best in terms of performance, and there doesn't seem to be any problems with file sharing. PCs still use the traditional SMB (SMB is also enabled on the server). Evidently, problems seemed to crop up when we tried to have Macs connect to the server via SMB.

If you've seen this problem

Current news on the MacWindows home page.


SMB problem seeing files in shares persists in Leopard 10.5.3

Monday, June 9, 2008

Thomas Hauber reports that the Mac OS X 10.5.3 update did not fix a problem he has with seeing files inside mounted shares:

The issue of displaying more than certain number of files in an SMB share still persists. Right now when connected to an SMB share we can only see 16 files max in that share. Apple's latest update did not fix this problem.

We have previously published reports of users not being able to see any files in mounted shares.

If you've seen Hauber's problem

Another reader with 10.5.3 problem seeing files inside of SMB

Tuesday, June 24, 2008

Christian Parmigiani responded to a previous report (above) about a file sharing problem that started with the Leopard 10.5.3 update:

We have the same problem [with seeing files inside mounted shares] in Leopard 10.5.3.

If you've seen this

Reader can't log on to SMB server after Leopard 10.5.3 update

Monday, June 30, 2008

Joel Aanerud can no longer log on to an SMB file server after updating Leopard to 10.5.3:

I'm running Leopard on my MacBook (2.4 GHz). When I updated to 10.5.3 I could no longer log on to our server at work. I log in pressing "Command" + "K" and then enter the name of the server. Our server is running Solaris 10 and I connect to it from my Mac using Samba. It's a non-encrypted server.

If you've seen this problem

Current news on the MacWindows home page.


Leopard 10.5.3 update causing file sharing login problems

Thursday, July 3, 2008

Jørgen Kold in Denmark reports that Leopard 10.5.3/10.5.4 can't log into a Solaris SMB file server:

My colleague is having problems logging in to a Solaris server from his newly updated MacBook running Leopard 10.5.3.

We are running a Sun Solaris server acting as samba server. We use samba version 3.0.11. On our samba server we use nonencrypted passwords, plaintext.

The problem occurs when our Macs update to 10.5.3. We do not get any error message, but it reacts like if the password is wrong. I think it checks the password as though it were encrypted even though it is not.

I found other people with similar problem at one of Apple's forums. We have tried the new 10.5.4 update but the problem is still there.

If you've seen this problem


Printing error ("access_denied") with Leopard 10.5.4 | Top of Page |

Tuesday, July 15, 2008

Xavier Hernandez reports seeing a printing problem the yields an error "NT_STATUS_ACCESS_DENIED" for printers attached to Windows PCs. We had a lot of reports about this for Tiger, as well as a number of suggested fixes. Hernandez is seeing this on Leopard, and has some ideas, but no fix:

From Leopard, I can see an HP Printer (Color LaserJet 2600N) hooked to a Windows XP computer on the company network (we are on the same subnet, workgroup,etc). I can see it and add to my printers.

But when I try to print, I see the job sent to the printer, but stays there and a message that says NT_STATUS_ACCESS_DENIED. When I look at the Windows XP PC, my Mac job is still in the printer queue but doesn't get printed.

I also took a look at the CUPS system on my MacBook Pro and there is the XP printer with a big message: "Tree connect failed (NT_STATUS_ACCESS_DENIED)"

I have checked if my XP user account and password on the XP Machine are right and it is the same one I am using to configure the printer on the Mac.

This reminds me of a similar problem years ago (Jaguar?) that had to do with SMB signing (password encryption) not supported by OS X.

I tried several workarounds but none worked including the ones at Apple Discussion Forums.

http://discussions.apple.com/thread.jspa?messageID=6871761

Basically either using the CUPS configuration, or the Printing & Fax panel with all the different URI possible combinations like the following smb://username:password@Workgroup/ServerName/PrinterID

However I noticed something strange. I went into Terminal and typed: smbclient -L danny -U guest

With no password, where danny is the name of the XP computer and I get no errors....and shows the printer as shared (LaserTmp). However if I use my XP account and password, I get an error:

XavierMBP:~ xavier$ smbclient -L danny -U xhernandez Password: session setup failed: NT_STATUS_LOGON_FAILURE

I thought: “maybe I got the wrong account or password,” went to the XP computer, and logged on the machine with no problem. And I do have access to the printer (after looking at the properties and the sharing tab for my XP account, cannot manage it but I am allowed to print).

And of course I tried using no password when configuring access to the printer, but get the same Logon failure message (in console). It seems that there is some problem when transmitting the XP password/account from the Mac to the XP computer.

Another case of "access_denied" printing error with Leopard 10.5.4

Friday, July 25, 2008

Michael Jalkut has the same printing problem reported on July 15 regarding an "access_denied" error when printing to a Windows printer. Oddly, Jalkut can print from Windows running a virtual machine, but cannot print from Mac applications:

I'm trying to print from Leopard 10.5.4 to Windows XP SP2, which is connected to a shared USB Canon MP470.

I've spent a week now trying every setting and every thing and program I could get hold of.

I can print with no problem from Fusion on the Mac. But from OS X, nothing much.

I get the same symptom exactly as you reported on July 15.

I did get it to print once using DAVE on the Mac. But even that was only after a day of trial and error. That must have been a fluke, because I can't do it again. I tried ExtremeZ-IP with no luck. I tried singleclick, and maybe a couple more. Only DAVE showed any sign of life.

If you've seen this problem

Workaround and Apple acknowledgement of "access_denied" printing error with Leopard 10.5.4"

Friday, August 15, 2008

Two readers commented on the problem with Leopard 10.5.4 which causes the error "NT_STATUS_ACCESS_DENIED" for printers attached to Windows PCs. One reader offers a workaround while another reports on comments by an Apple software engineer.

Scott Lerwill provided the workaround:

I was getting the exact problem while trying to connect the company's Macs onto a network printer requiring AD authentication. In the end I found that the solution is to add the following printer in advanced printer: smb://<adusername>:<adpassword>/<printerservername>:139/<printqueue>

Therefore by adding the port 139 into the queue finally allowed our Macs to connect to the printers.

If you've tried this suggestion

Dan Stranathan reports that Apple's author of the CUPS printing software in Mac OS X has commented on the problem, saying that Apple is planning to fix it:

The access_denied problem has been commented on by Michael Sweet, the creator of CUPS and now an Apple senior printing engineer.

I have mentioned this issue in the Apple list server: printing-request@lists.apple.com (Go to lists.apple.com and subscribe). I bring up the topic every couple months to get an update. I have ben testing this since October 2007 and its still "broken". Macs that are bound to AD can "see" the Windows IPP print queues in the Printer Setup/Add printer panes, but they cant actually print to them.

There are a few issues with CUPS, IPP, Kerberos regarding this topic. I think Michael mentioned to me at WWDC 2008 that it would be fixed in Leopard at some point in time.

Current news on the MacWindows home page.


Mixed reader results for "Access Denied" printer error workaround | Top of Page |

Friday, August 22, 2008

Two readers reported their results using a suggested fix for a problem with Leopard 10.5.4 which causes the error "NT_STATUS_ACCESS_DENIED" for printers attached to Windows PCs. One reader was successful, the other was not.

Rich Williams found that the tip worked:

I hadn't been able to connect to the local Windows network printer at work since I upgraded to OS X 10.5 despite having an already working print queue for that printer. I had given up trying, until I stumbled across this suggestion last Friday from your web page:

smb://<adusername>:<adpassword>/<printerservername>:139/<printqueue>

I deleted the already defined yet not working print queue I had been trying to get to work, and created a new one for that printer as outlined above. It works fine, now.

Xavier Hernandez was not so lucky:

I tried the workaround published on August 15 for the "Access Denied" printer error, however, it did not work for me. And I am on an Active Directory Network.

If you've tried this

TIP: Fix for printing error ("access_denied") with Leopard 10.5.4

Wednesday, September 10, 2008

Matt Pearson has a suggestion for fixing the "access_denied" printing error seen with Mac OS X 10.5.4.

Attaching to Windows Server 2003 print server in the past has been easy, but Leopard broke this with what appears to be the same problem as noted in the above article. I am running in a hybrid Mac/Windows network with over 200 mac clients and 200 XP clients on a primarily Windows network with AD running hybrid with 2000 and 2003 servers. I also have an old schema for AD.

Even at the UNIX command line I could not get the printer install to pass authentication to the Windows Server 2003 print server. I have had no problems with earlier versions of OSX (even 10.5.1).

The fix: Using the Directory Services app I created computer accounts in AD for the Mac computers. This changed the browsing behavior of the Mac from ten minutes to populate the domain and servers on it to less than one second. The domain controllers have guest access disabled (which is standard best practices in a hybrid environment). Once the computer is in AD I was able to browse the network for printers using the DEFAULT button in add a printer (not Windows button). Not only do they get installed quick, the location and drivers are automatically selected. Once done with the install the printer still does not have the correct credentials. Upon first print, credentials are requested and you can store them in the keychain. It seems in this way no credentials are ever stored with the printer and instead are passed via the keychain each time. Works great.

I have further discovered that the default protocol to search for printers has been indicated to be only Bonjour. This is confirmed in the \etc\cups\cupsd.conf file. By adding BrowseProtocols All under # Show shared printers on the local network you can get Unix based printers working.

If you've tried this

Another case of “access-denied” error when printing to Windows Domain

Minmin Qin is seing the printing problem the yields an error "NT_STATUS_ACCESS_DENIED" for printers attached to Windows PCs. We have several suggestioned workarounds and fixes (here and here), but they did not resolve Qin’s issue. He reports what didn’t work:

I would like to report that we tried the suggestion on your site but we still have a printing problem.

We had no problem for printing from Mac OS X 10.4 to a Windows domain printer by changing the /etc/smb.conf and connecting a printer via smb.

We could add the printers on Mac OS X 10.5 successfully without changing anything at smb.conf (10.5's smb.conf is different). When a print job was sent to a windows domain printer, an authentication dialog appears asking whether the user is registered or a guest. No matter which option was chosen (guest or domain user), the job pauses in the queue and waited for authentication as "On Hold (Authentication required).

We tried following but got the same situation:

1. Simply added printer from Advanced/Windows\

smb://<domainusername>:<domainpassword>@<printerserver>/<printer>

2. Changed Require user at /etc/cups:
# All administration operations require an administrator to authenticate...

<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>

Replace the “Require user” line with this one:
Require user @AUTHKEY(system.print.admin) @admin @lpadmin

We then changed settings of SMB:
---smb://<domainusername>:<domainpassword>@<printerservername>:139/<printer>
---smb://<domain>/<username>:<password>@<printerservername>/<printer>

I am thinking if I can use something as sudo lp to see if it works.

If you've seen this problem or have a suggestion

TIP: Another workaround for "Access Denied" printing error

Friday, March 20, 2009

John Ponsano sent us another workaround for the NT_STATUS_ACCESS_DENIED error seen with Macs accessing printers attached to Windows PCs:

I have what has turned out for me to be a sure fire workaround for all cases I've come across for this issue. Being a bad tech, I turned it from a software issue into a user training issue.

I add a Windows shared printer the default way. I have all our Mac workstations bound to Active Directory, and in the Default add printer tab I can select a Windows shared printer and add it.

After that, when attempting to print to it, the user gets a page requesting authentication. By default, OS X will present the authentication window with the user's long username. Delete that, and instead have the user authenticate using their short username. Do not check the "remember password" box. The document should print fine; or at least has for me in every case like this.

If the user submits a job using their long username, they get that access denied issue. If they authenticate with their short username but check the "remember password" box, it works once, but every time after that the jobs fail with an access denial (it's as if the Keychain is remembering their long username, but I've checked and confirmed that it is actually storing their short username, so I don't know what the deal is here).

Unfortunately, this solution requires the user to authenticate every time they print to a Windows shared printer, and resist the urge to check the "remember password" box.

If you've tried this

We also have several previously reported workarounds on our Leopard Tips and Reports page.

Current news on the MacWindows home page.


New CrossOver 7 Runs Outlook, Office 2007 on a Mac--without Windows
Give your Mac ActiveX in Internet Explorer, launched directly from the Finder.
Starts at only $40 (Windows not required!) Free trial from CodeWeavers
.
Click here for more.

chkdsk fixed Leopard AFP folder creation problem with Win Server, but created another

Tuesday, September 2, 2008

Craig Carr had a problem with Leopard and using AFP for accessing a Windows 2003 Server. When he created a folder, other users couldn't write to it. He fixed it, but the fix create a new problem:

I have Mac OS X 10.5.4 loaded on my Power Mac G5. When connected to Windows 2003 server via AFP, I could create a folder on the server but no one else had writing permissions to that folder but me. I told the server to give us Full Control but that didn't help. I modified my umask to 000 and that didn't help either. Tiger machines had no issues; Tiger can create folders that others can write to also. Leopard could connect via SMB and it worked fine. This was only with AFP, which I have to use for my RAMPAGE RIP that we use to send jobs to the press.

We restarted our Windows 2003 Server and had it perform a chkdsk. It found thousands of security issues with files and fixed them. After that finished we found that we can now create a folder with Leopard that others can read and write to. But now we have a brand new issue.

When we click on ANY file on an AFP mounted server and "Get Info" on that file, our Finder hangs, just with Leopard machines. This is almost a worse problem than the last one and sounds like a Windows 2003 Server issue with our Macs.

If you've seen either of these problems

Current news on the MacWindows home page.



Reader says 10.5.5 update broke the seeing of SMB shares

Thursday, October 30, 2008

Roger Brown reports that after updating to Mac OS X 10.5.5, his Mac can no longer see Windows and Linux shares. Loggin in via Connect to Server works - sometimes. Brown said:

I recently had two MacBooks upgraded to Leopard 10.5.5. After entirely satisfactory file sharing on a mixed XP - Vista - OS X - Ubuntu network, right up until 10.5.4, it has all gone to pieces. XP, Vista and Ubuntu can see and share files on the Leopard MacBooks without difficulty. But Leopard cannot see any of them.

If I use the Connect to Server function, I can sometimes connect. Sometimes "smb://study" will work, while at other times, for no apparent reason, "smb://192/168/0/2" is the only way. Sometimes neither will work. As the Ubuntu installation is a dual boot with Vista Home Premium, it cannot be a problem with the hardware (which worked with all former versions of OS X).

I have tried every fix on the MacWindows pages without a flicker of success in getting the shares to show up in Leopard. I am completely baffled.

If you've seen the Leopard 10.5.5 update cause these problems

We've posted a number of suggestions for fixing browsing of SMB shares with older versions of Leopard, which you can find on our Leopard Tips and Reports page. These tips include turning off IPv6 on the Mac and on AirPort routers, changing passwords, and many others. Some are here, but there are others as well.

More reports and workaround for not seeing Win/Linux SMB shares after 10.5.5 update

Friday, November 14, 2008

Several readers responded to our reader report of the Leopard 10.5.5 update causing the Finder to no longer see Windows and Linux shares. Rudi Huibregtse found that an older fix we had posted worked for this issue-enterning the workgroup name in System Preferences:

Same over here. I fixed it by using the WINS tab solution, filling in the workgroup, as described at MacWindows. I'm glad I checked the MacWindows pages!

If you've tried this fix

Paul Verkruissen reboots his server to get around the problem:

I am having this problem seeing Windows Shares in 10.5.5 more often than not now. I never used to have any issues, now I rare automatically see my Windows server, usually have to reboot the server to get Mac to see it.

Dustin Williams has to type the path (smb://) in the Connect to Server dialog to connect:

The latest update of Mac OS X 10.5.5 has kicked me off of my Windows 2003 network. The only way that I can connect is to open Safari and do the SMB work-around--every time I log out or shut down my computer. With version 10.5.4 the connection stayed strong no matter what.

Ian Hargest also has the problem seeing SMB shares on a Linux server after the 10.5.5 update:

I'm glad I came across your website in some Google results while researching this issue. About the same time that I started trying to setup a partition on my Ubuntu server to serve as a target for Time Machine (based on these instructions), I lost the ability to access the SMB shares from my Mac. I backed out the changes I had made to my Ubuntu server, thinking I'd dorked something up however, upon reflection, that was about the same time that I received the 10.5.5 OS X update.

In my troubleshooting, I have confirmed that my Win XP MCE machine has no trouble accessing the SMB shares, but my Mac is just plain lost. I can't even reach the server at the moment, so I'm off to explore the workarounds you have listed on your site.

Rebooting networking hardware fixed reader's 10.5.5 SMB problems

Thursday, November 20, 2008

Ian R. Hargest updated his Nov. 14 report about the Leopard update 10.5.5 update's problems with SMB file browsing. He fixed the problem by restarting all of his network hardware:

After much troubleshooting, and requisite swearing, turns out my problem was caused by my networking gear. After troubleshooting my Ubuntu server for a couple hours and coming up empty, I figured I'd reboot the network stack just to take it (cable modem, VoIP router and wireless router) out of the mix. Lo and behold, both my Mac and XP client machines were able to recontact the server.

I'd not changed anything on the server; I'd only been looking for something that was amiss. I hadn't changed anything on the Mac nor the XP clients. Strangest damned thing.

If you've seen this

TIP: WINS fix for Leopard OS X SMB browsing works for 10.5.5 bugs

Monday, December 1, 2008

Brian Wilson found a fix for the intermittent problems with Leopard 10.5.5 is having seeing Windows SMB shares. His fix was similar to one we reported a year ago for an earlier version of Leopard. Wilson said:

If you have intermittent problems connecting to a PC running Windows XP where your PC icon appears in your Mac finder but refuses to connect sometimes, then ensure you do the following:

On the Mac go to my System Preferences->Network and if you are connecting wirelessly select the Airport connection and hit 'Advanced'. Under the WINS tab select your workgroup. In my case, this is 'workgroup'. It doesn't seem to matter that this is in lower case whereas it was created as 'WORKGROUP' in Windows. Insert your PC's IP address into the WINS Servers box (e.g. 192.168.1.7) and hit OK.

This completely eradicated any intermittent problems I had.

If you've tried this

TIP: Readers says firewall settings at Leopard 10.5.5 file sharing issue

Monday, December 8, 2008

Adrian Li had the problem with the Leopard 10.5.5 upgrade not being able to see Windows shares. He fixed with firewall settings with a tip from Microsoft support:

Six months ago, my sister got a new 20" iMac. My home router was a WRT54G v2.0 and my sister requested file sharing. I think I took the easy way and allowed my Norton 360 to let most local port connections from a select IP through, this made cross platform sharing work flawlessly. However, I understand that I am but one case that did not have any difficulties.

It is now December and since then, the changes that have happened are: iMac 20" has been upgraded to 10.5.5 and the router firmware has been changed to dd-wrt 24 mega generic.

I tried to share using the old settings, but it wouldn't work. Changed the firewall settings to allow all ports. Tried accessing my Windows files from Mac, and it worked.

Then, I found this Microsoft support page and after I set my firewall to allow local ports 135-139 and 445, file sharing between Windows and Mac was working again.

If you've tried this

Current news on the MacWindows home page.


Connect to Server hangs user with Leopard 10.5.5 update

Monday, November 24, 2008

Many have reported that the Mac OS X 10.5.5 update caused the Leopard Finder to stop seeing network shares. Allen O'Loughlin now says the Connect to Server dialog doesn't work. He's tried some of the suggestions on our Leopard Tips and Reports page, with no success:

I can't use connect to server anymore. Network shares all working prior to 10.5.5 without fail. Now can't access shared folders or printers. Connect to Server hangs. Have tried recreating the Airport connection, tried turning off IPv6, tried entering workgroup name into WINS. Nothing helps.

If you've seen this problem

Current news on the MacWindows home page.


New CrossOver 7 Runs Outlook, Office 2007 on a Mac--without Windows
Give your Mac ActiveX in Internet Explorer, launched directly from the Finder.
Starts at only $40 (Windows not required!) Free trial from CodeWeavers
.
Click here for more.

LEOPARD 10.5.6 TIPS AND REPORTS

Reader says 10.5.6 update fixes file sharing issue | Top of Page |

Wednesday, December 17, 2008

Todd Kingham reported that Monday's Mac OS X 10.5.6 update fixed his problem with Windows shares appearing and disappearing, a problem that we've long reported on with leopard. It also fixed file sharing problems related to version 10.5.5. Kingham said:

This is obviously too soon to be sure, BUT, I just finished installing the latest update for both my MacBook Pro firmware and Mac OS X (10.5.6), and as soon as I rebooted, all my originally available shares have reappeared.

I was having similar issues to your "Windows Shares appear and disappear" report. I have several Windows machines and a Mac Book Pro running Leopard 10.5.5. My Shared devices randomly displayed then "lost" my Windows machines. Rebooting helped but doesn't seem to be a valid solution in my book. I was also having problems with Mounted Volumes suddenly loosing their connectivity. I could find a Windows Share and connect. Suddenly, it would still appear to be mounted but I could no longer get to the files.

If you've seen the Leopard 10.5.6 update fix or break any cross-platform network functions


Group Logic reports Leopard 10.5.6 problem with searches on AFP volumes | Top of Page |

Friday, December 19, 2008

Group Logic reports finding a problem with searching with the newly released Mac OS X 10.5.6 where clients will fail to find any files on AFP network file sharing volumes. This includes Group Logic's ExtremeZ-IP AFP server for Windows and Mac OS X Server.

Group Logic CEO T. Reid Lewis described the problem:

Clients issuing search requests against either a ExtremeZ-IP volume or Mac OS X 10.4.11 Server will fail to find any files or folders. This problem only affects clients running Mac OS X version 10.5.6. Earlier versions of 10.5 (including 10.5.5) and all versions of 10.4 get the proper results from a search request. We tested against 10.4.11 and 10.5.5 Server as well as the latest versions of ExtremeZ-IP.

Group Logic has a workaround for ExtremeZ-IP at its web site.

Group Logic finds workaround for Leopard AFP search bug

Friday, March 20, 2009

Group Logic has identified a workaround for the previously reported bug in Mac OS X 10.5.x that causes it to return no results when searching an AFP file server. The workaround is to use a free search utility called Find Any File instead of the Mac OS X client's Spotlight search tool. The servers that the bug affects include the company's ExtremeZ-IP server, as well as Windows servers using Services for Macintosh, and Mac OS X Server 10.3.x and 10.4.x. Leopard Server is not affected by the bug.

In December, Group Logic reported to us that it had identified the problem with Mac OS X 10.5.6. A MacWindows reader reported having a similar problem with Mac OS X 10.5.5.

If you've tried this workaround

Reader says Find Any File for AFP search is slow

Wednesday, March 25, 2009

Shawn Livingston responded to our report of using the Find Any File utility as a workaround to a Leopard 10.5.6 bug that prevents searches of non-Leopard AFP servers.

I have tried this work around and while it works, it is not a very viable option. It is unbelievably slow. Before the OS X 10.5.6 update ExtremeZ-IP used to return information on searches within seconds. Using Find Any File takes over 5-10 minutes to return results of a search. I am very anxious to see a fix on this.

If you've seen this problem

Group Logic tip on making Find Any File fast; search bug fix from Apple on the way

Monday, March 30, 2009

Group Logic CEO Reid Lewis sent us a tip regarding the workaround for a Leopard 10.5.6 bug that prevents it from searching non-Leopard AFP servers. Group Logic recommends using Find Any File instead, but a reader reported reported that it was slow. Lewis described how to make Find Any File fast:

Our tech support team has reached out to help your reader who's experiencing slow search times with our 10.5.6 search workaround. Your readers should expect search results just as fast as always with ExtremeZ-IP and we can help him achieve them again.

Check the following possible issues:

  • Search is set to "All Volumes" by default; only AFP searches are optimized so including an SMB share in the results will slow them down by 15 X (yes 15 times)
  • Performing a compound search
  • Searching must be done at the root; searching a "folder on the server" will bypass the optimization
  • There might be a problem on the server that resulted in a failure to index, or some other issue causing them to miss our search index.

Meanwhile, Bryan Schappel thinks Apple will fix the AFP bug soon: "This site says it's fixed in the upcoming 10.5.7."

A search utility for SMB and ADmitMac

Wednesday, March 25, 2009

Lars Berger from Germany recommends using a free utility to search SMB servers when Thursby Software's ADmitMac is running on the Mac:

I found out that the freeware tool Easy Find from Devon Technology is good to search our SMB fileserver, since ADmitMac isn't able to search within Spotlight. (We use ADmitMac.) I think this will do this for other resources [AFP servers], too.

Reader reports afp searching bug with Leopard Server 10.5.5

Monday, January 5, 2009

John Lockwood reports having a problem with searching Leopard Server 10.5.5 from Tiger clients. A similar problem was identified by the developer Group Logic with the 10.5.6 Server, but Lockwood sees it with 10.5.5:

We have (and are) currently having this same problem with Mac OS X 10.5.5 Server and Mac OS X 10.4.11 clients. That is doing a Finder search from the root (top) level of the Share point fails to find any results, doing it from any sub-folder works fine as long as the user has permission to access any sub-folders. This occurs with both the simple search i.e. just typing in the search box in the Finder window, and also when you first do Command-F to bring up a more fully-featured search option.

This is not a permissions problem (or at least should not be) since the users do have read access to the top-level in order to be able to browse to and access the sub-folders.

I have not yet upgraded to 10.5.6 and therefore not yet tested to see if this fixes it, based on the report by Group Logic I doubt it would be fixed.

Doing the search on the Mac OS X 10.5.5 Server itself (from the top- level of the same volume) does work. We did not use to have this problem before upgrading to Mac OS X 10.5.x Server, i.e. a 10.4.11 Server was OK with 10.4.11 clients.

If you've seen this problem

Current news on the MacWindows home page.



Leopard 10.5.6 update fixes MacBook Pro Blackberry issue | Top of Page |

Friday, December 19, 2008

Mark/Space said that the new Mac OS X 10.5.6 update fixes USB connectivity problems between the new MacBook Pro and Blackberry devices. The company recommends the update for all customers of The Missing Sync for BlackBerry.


10.5.6 update slows Mac to a halt; Paragon NTFS suspected | Top of Page |

Friday, December 19, 2008

After Val Hitchman installed the Mac OS X 10.5.6 update his MacBook Pro slows to a halt. He had third-party drivers for NTFS (the Windows file system), which may conflict with the update:

My MacBook Pro has all but ground to a halt since Monday and I'm now wondering if its anything to do with the update. I can open my apps and they work normally, but I cant use my folders. If I click on anything, eg Finder, folders, to open move or delete, nothing happens - NOTHING. Then 10 minutes later it will highlight or open. I can't click on them to move them or do anything. I'm pulling my hair out.

I did download Paragon recently so that I could use memory sticks in NTFS for PC and Mac - could it be anything to do with that?

If you've seen this problem

Current news on the MacWindows home page.



Reader's Mail.app no longer works after 10.5.6 update | Top of Page |

Friday, December 19, 2008

Ed Cirilo reports: "I cannot read any email after the 10.5.6 Leopard update--it crashes."

If you've seen this problem

TIP: Fix for Mail App Not Working on a 10.5.6 update

Thursday, May 21, 2009

Will shared a fix for a Mail problem with Mac OS X 10.5.6:

Per the note at MacWindows, we are letting you know our Mail app was no longer working after our upgrade from Tiger 10.4.11 to Leopard 10.5.6. I ran all the updates on all software, and still it didn't work. Then I found these instructions to see if this information works to fix it. Their instructions worked perfectly:

Close all running applications, then go into your ~User/Library/Mail/ directory and move everything with a white paper icon temporarily to your desktop, leaving all files with folder icons in the directory. Restart your computer and then open Mail and you should be at the Import Your Messages screen. Go through this section and when you're done Mail should open up and be working.

Update: Once you can confirm that Mail is working and you are able to send and receive messages, you can delete the white paper icons from your computer.

If you tried this fix

Reader verifies fix for Leopard Mail

Wednesday, June 23, 2010

Don Lehnhoff confirmed a fix with Mail in Mac OS X 10.5.x: "I had this exact problem; I followed the fix you had here -- problem solved."

Current news on the MacWindows home page.


NEW CrossOver 9.0 Runs Windows apps on a Mac--without Windows
Improved Outlook support, Quicken 2010, more Windows apps. Give your Mac ActiveX in Internet Explorer, launched directly from the Finder.
CrossOver Games runs Left4Dead, Warcraft, Steam, Spore, and others on your Mac.
Starts at $40 (and no need to buy Windows!) Free trial from CodeWeavers. Click here for more.

AirPort Express problem with Leopard 10.5.6 update | Top of Page |

Monday, February 16, 2009

Patti Nevins wrote with this issue with AirPort Express and the Mac OS X 10.5.6 update:

Since I've run the 10.5.6 Combo update on my MacBook (purchased September '08) this past weekend, my AirPort Express router is not recognized by my network. My Ethernet is disconnected when the MacBook sleeps, but from what I've read in forums, that is probably due to the new security in the update. I haven't found out how to resolve the problem in any of the forums so far.

If you've seen this problem


Moving from Win Server 2003-2008: Reader says ADmitMac fixed Leopard SMB file share issue | Top of Page |

Monday, May 18, 2009

Shane Hunter reports that upgrading Windows Server from 2003 to 2008 is preventing Macs from accessing shares using SMB. Thursby's ADmitMac fixes the problem:

We have been struggling with a problem when attempting to connect to a shared drive from a Mac. We can successfully connect to a share being hosted by Windows Server 2003 in Active Directory. The Mac is NOT bound to AD. We are trying to migrate to Windows Server 2008 and we are not able to connect to a share. We have tried with both Mac OS X 10.5.6 and 10.5.7. I just spent the last 3 hours on the phone with Microsoft and they say the connection appears to be failing at the SMB portion of the connection. MS upgraded to SMB2 for Windows Server 2008. We attempted to disable this in the server's registry and that had no effect. I installed ADmitMac and that did solve the problem.

ADmitMac includes an SMB client that replaces Mac OS X's built-in Samba client. It also includes Active Directory integration functionality. Another product, Thursby's DAVE, includes only the SMB client.

If you've seen this issue

Leopard SMB problem moving from Win Server 2008, ADmitMac works

Tuesday, June 23, 2009

Randall Araquistain verified a previous report that ADmitMac fixed a Leopard SMB file share issue caused by migrating from Windows Server 2003 to 2008:

We have been trying to get Mac computers with OS X to authenticate to a Windows 2008 server with no luck. I found this solution at MacWindows and it works great. Very easy solution and the SMB client included in ADminMac works great with Windows Server 2008. Shame on Apple for not fixing a simple and required function for any computer in a corporate environment with Leopard.

Current news on the MacWindows home page.



LEOPARD 10.5.7 TIPS AND REPORTS

Reader problem with Mac OS X 10.5.7 update and NAS storage | Top of Page |

Monday, May 18, 2009

After upgrading to Mac OS X 10.5.7, Tommie Carter can no longer connect to his WD My World Book network attached storage drive:

I have found that after the upgrade to MacOS 10.5.7 my Mac will no longer connect to my WD My World Book 1TB drive. Previously I was able to connect via the network but something appears to have changed in the networking daemons which prevents the password from being authenticated by the WD.

If you've seen this problem

Another OS X 10.5.7 problem with network drive

Thursday, May 21, 2009

Chris Duffy responded to Mondays report of the Leopard 10.5.7 disabling access to a network drive:

My MacBook (2007, 2.1 GHz , 4 GB RAM, 160 GB) won't recognize a Buffalo 1TB drive after upgrading to Mac OS X 10.5.7.

If you've seen this problem

More on the 10.5.7 update and NAS

Wednesday, May 27, 2009

Two readers responded to previous reports of the Mac OS X 10.5.7 update breaking communications with network attached storage (NAS). Patrick reports on one suggestion that does not work:

I have the problem with Mac 0S X 10.5.7 update and NAS storage. Someone told me to change something in the router:

  • Uncheck SPI (stateful packet inspection, or dynamic packet filtering)
  • Use "endpoint independent' with both UDP & TCP endpoint Filtering

However, it did not solve the problem.

Meanwhile, Chris Duffy got his Buffalo 1TB to work:

A quick update: I don't know why, but all is well. I can now see and access the TB now.

And reader verifies 10.5.7 problem with WorldBook NAS

Monday, June 1, 2009

Julian Darley is another reader seeing the problem with Mac OS X 10.5.7 update and NAS storage:

I am having major issues between my MacBook and a 1 TB WorldBook NAS. The connection has never been great, but now, on the rare occasions when the MacBook recognizes the drive, the chances are high that during a file transfer the connection will just be dropped. Mind you, I continually have to renew the DHCP lease on this Mac, and the problem might even be worse with 10.5.7.

If you know of a workaround

Reader ties Leopard NAS storage problem to AirPort

Monday, June 15, 2009

Patrick updates his previous report about a problem accessing network attached storage (NAS) with the Mac 0S X 10.5.7 update:

I just note that if I connect my Mac to the network with cat5 Ethernet cable, the NAS can be detected as usual. If I connect my Mac to the network by wireless, the NAS cannot be detected. And, when I check it with the "arp" command the NAS returns with the correct IP but shows the MAC address as incomplete.

If you've seen this issue

TIP: Workaround for Leopard 10.5.7 NAS bug

Thursday, June 25, 2009

Cory Siansky has the problem with the Mac OS X 10.5.7 update not being able to see network attached storage (NAS storage); But, Siansky can get it mounted using Connect to Server:

I have a WD World Book 1.5TB NAS. My Mac mini identifies this NAS as an SMB share and is configured to mount it as a login item on boot. Up until I upgraded to 10.5.7, this worked flawlessly. Since I upgraded to 10.5.7, I receive a message during the boot sequence indicating that the device could not be found. I have the chance to click "OK," and the alert returns once more. After I click "OK" a second time, the alert does not return.

The SMB does not mount on its own. However, it is available to the system (by browsing Go>Connect to Server) after about 90 seconds to two minutes. From that point on, the SMB appears on the desktop as usual and is accessible throughout the OS as expected.

One other related observation: during this same 90-129 second initial period, it seems that no service of the OS can talk to the network. One example: launching a browser window and attempting to navigate to an external site is fruitless. The browser will report during this first couple of minutes that the network (or the website) is unavailable.

As soon as the web comes online, so does the SMB. Seems related, don't you think?

If you've seen this

Richard Hockey also sees the problem:

Yes have the same problem connecting to my NAS (Maxtor Shared Storage II) with Mac OS X 10.5.7.

TIP: More Workarounds for Leopard 10.5.7 NAS bug

Tuesday, June 30, 2009

Two readers found two different methods of getting around the problem of Mac OS X 10.5.7 not recognizing network attached storage (NAS).

Michael FitzGibbon altered his login items list:

I have a LaCie NAS that has shown this behavior. I had added the share to my login items under the Accounts preference pane so that it would mount on boot. It worked for a while, then it stopped working. I deleted the share from the login items and re-added it, thereby placing the share at the end of the items that started up at boot time. This fixed the problem for me. The share now mounts on boot up.

Chris Lewis changed some file sharing settings:

I have both NAS and NDAS storage volumes and I had trouble connecting to them after the 10.5.7 update. Disabling file sharing and then reenabling it, and then clicking the SMB radio button via options, fixed the problem. No trouble since. Service discovery tools in OS X might need a kickstart. Also, it might pay to check the Mac's ID in WINS to make sure it is broadcasting the right info.

If either of these worked for you (Last week, we reported another workaround for this problem.)

Leopard 10.5.7 problem with Buffalo NAS

Wednesday, July 8, 2009

David F. reports another case of the Leopard 10.5.7 problems with network attached storage. He also has a permissions problem:

My NAS = Buffalo LinkStation 1GB. Yes, I experience a similar problem with the NAS not showing up at boot up or else going AWOL while running. I also have AFP running on the NAS in addition to SMB.

Moreover, I have an extra gremlin with file permissions selectively going fubar: some of my folders (perhaps created by psuedo running MTR) are not accessible - even by sudo - and they resist every attempt to have their permissions changed! (by super getinfo; file examiner; batchomd; etc). I don't think these two phenomena are related.

One never knows what is related to what. If you do,

Current news on the MacWindows home page.


SMB file sharing problems in Leopard 10.5.7 | Top of Page |

Wednesday, July 8, 2009

SMB file sharing issues have been widely reported with Leopard since Mac OS X 10.5.0. A couple of readers now report problems with 10.5.7. Polly Yen has the problem in both directions:

10.5.7 samba is not working. I have this issue, where I cannot connect from the Mac to my shard folder on my PC. I can ping the IP, I can remote log in, but I cannot connect to the shared folder. Also, from the PC (Vista ultimate) I cannot find the MacBook Pro.

Rogers Saxon tried an old suggestion from early Leopard builds:

I have the latest Mac 10.5.7 update. I tried turning off IPv6. The fix, I'm sorry to say, only lasted about 5 minutes. I can no longer reach the other computers in my network (PC's, one with Vista and one with XP). The IPv6 trick doesn't work anymore.

If you're having file sharing problems with Mac OS X 10.5.7

105.7 SMB file sharing problem reported with 10.5.8

Monday, July 13, 2009

Several more reports having SMB file sharing problems with Leopard 10.5.7. One reader reports that the Workgroup name keeps disappearing. Another reader says the problem is two-way.

Barbara Snyder sees it from the newest 10.5.8, in the Finder and Connect to Server:

I am switching from WIndows to Mac, (10.5.8 on a MacBook Pro) so all is new to me, although I'm a longtime geek and thus a fast learner. When I first turned on the Mac, I could access my desktop PC in Finder immediately and I was thrilled! Now I can't connect to any of the shared folders. When I try, I get an error "The operation cannot be completed because the original item for <foldername> cannot be found." I hunted around and some folks said turning off Mobile Me solved their problem, but it didn't for me. I can ping and can connect via RDC just fine. Frustrating! I also can't connect from the Finder via Go to server command.

Raj reports that the Windows Workgroup name keeps disappearing:

I have not been able to get SMB file sharing working in 10.5.7. I have "Preferences>Sharing>File Sharing" turned On and in the Advanced settings, "Share Files and Folders using SMB" is turned on. Under "Network>Advanced>WINS" I have entered the Workgroup name, but it doesn't seem to stick. When I close and re-open the window, the name disappears.

Johnny Kent has problems both ways, as did a previous reader:

I have the same problem, from a MacBook running 10.5.7 on a network with 3 other windows PCs: one Windows 2000, one XP and one Vista. The Windows machines can all see each other and share files but from all those I can't see the MacBook in the windows network folder and the MacBook can't see them. However from the MacBook I can ping all the other computers just fine.

Don't know what it was like before upgrade to 10.5.7 as I never tried to connect before in either direction.

If you've seen this issue

Workarounds for fixing SMB file sharing in Leopard 10.5.7

Thursday, July 16, 2009

Two readers sent in suggestions for fixing or working around Leopard 10.5.7 SMB file sharing problems with Windows. A third reader reports the problem and the issue with network attached storage.

Michael Millar uses Cisco Network Magic, a file transfer utility:

I run a small satellite office for my law firm. As a satellite office, we are lucky if we get one or two visits a year from the firm's IT guys. So, we make do on our own. We have three Win XP machines and my MacBook Pro running Mac OS X 10.5.7. We use one of the Win XP machines as our "server" and local file sharing. I experienced a lot of flaky problems connecting my Mac to the Windows machines including occasionally losing write privileges to the server. I installed a little utility from Cisco called Network Magic and it has solved all of my local file sharing problems between my Mac and PCs.

Readers have previously reported that Thursby's DAVE, an SMB (samba) client, also works.

Chris Lewis shared a procedure that works for him with Windows XP:

I stream files to two SMB client media players and share files with two XP laptops on my mainly Mac network. I might have a fix here for Windows XP users (not Vista, never Vista). Try this:

In the Network preference pane, create a new location. Call it WORKGROUP or whatever. Select Advanced, select the WINS tab, make sure the computer name (I use the MAC address of my machine) is set and note it. Type WORKGROUP or whatever in the workgroup window and OK. Click Apply in the main Network pref pane window and you should get your IP address via auto DHCP OR set the IPv4, Subnet Mask, Router addresses etc if connecting manually. WORKGROUP should stick in the WINS settings.

In the Accounts pane, under Guest Account, make sure "Allow guests to connect to share folders" is checked; Leopard does not like anonymous users.

NOW, go to the Sharing pane, go to Options, uncheck the user account to be shared, click Done, disable File Sharing, reenable File Sharing, choose Options, check the account to be shared, select SMB sharing, check the Mac's name, click Done. Make sure the folder(s) to be shared is/are on the list and that sharing permissions are set correctly. This step resets the sharing and SMB discovery protocols.

In the Security pane, choose "Allow all incoming connections" in the applications Firewall. You can experiment with the different settings after you've established file sharing.

The Windows XP PC should discover the shared folder(s) on the WORKGROUP Mac and vice versa if sharing has been set correctly on the Windows machine (and that is a different ball game).

(If the Internet firewall on the modem connection is left intact, the applications Firewall would apply to only LAN connections; a LAN user is very rarely a source of attacks. And sudo via Terminal can delve through the applications Firewall anyway.)

If you've tried this approach (Note: one reader reported that this procedure worked.)

Peter Bednarczyk has had file sharing problems with all the Leopard builds:

In reply to your report I have two Macs With Leopard 10.5.7, and one PC with Vista and another with XP. The problem started really since the first 10.5.x upgrade, all samba connections do work only for few minutes if at all. The NAS drive doesn't work for longer than two minutes, too. Network printers work when they want. It all makes me go back to sadly more reliable Windows, but then there is no proper IMAP client for it. Good thing is, that there is always pen and paper.

"Connect to Server" won't connect to SMB shares on OS X 10.5.7

Tuesday, July 21, 2009

Aaron Reynolds can no longer use the Finder's Connect to Server dialog to connect to SMB file shares:

We cannot access Windows Active Directory shares from Mac OS 10.5.7, we have been using "smb://servername" since 10.2, now with 10.5.7 no luck, just sits there saying "connecting" forever. Some say to log out of MobileMe and it fixed there problem (on the official Apple forums) but we don't use MobileMe and still have the problem.

If you've seen this

TIP: Use FQDN for SMB Connect to Server with 10.5.7

Monday, July 27, 2009

Jeff Sleeper sent a fix for the problem of the Mac OS X 10.5.7 update no longer connecting to SMB shares with the Connect to Server command:

I've experienced this issue and have found that using the Fully Qualified Domain Name for the server can fix the problem. For example: smb://server.domain.com/share

If you've tried this

OS X 10.5.7 SMB "Connect to Server" problem a firewall issue?

Monday, August 3, 2009

Norbert Schönbauer says that his problems with Mac OS X 10.5.7 connecting to SMB had to do with firewall ports:

I experienced similar problems after we had switched to a different software firewall on some Windows XP machines. I could no longer access the files on those PCs with my Mac (iBook with 10.5.7). Then I learned that the Mac used odd ports for the SMB connection. After I opened those ports that were blocked following the firewall log on the Windows XP machine, everything was working fine again. From the perspective of the firewall of the PC the affected ports were: Remote UDP ports (which usually are 137, 138 and 445).

If you seen this

Reader verifies fix for SMB file sharing problems in Leopard 10.5.7

Monday, August 3, 2009

Chris Cronbaugh verified a previously reported fix for Leopard 10.5.7 SMB file sharing problems:

After having problems with file sharing between my MacBook running Mac OS X 10.5.7 and my PC running Windows XP, I came across your website while looking for help from the internet community. I just wanted to let you know that Chris Lewis's procedure for fixing the problem worked for me.

If you tried the procedure


SMB permissions issue with Office files in Open Directory

Monday, July 13, 2009

Donald Clark is seeing user permissions change with PowerPoint and Excel files. He's using ACLs in Open Directory, and calls to Apple and Microsoft haven't helped:

I have been having problems with 10.5.5, 10.5.6, and 10.5.7. There is one easily reproducible problem: A PowerPoint file made on a Mac (10.5.7) with Office 2008 (both fully patched) and saved to the share point as a .ppt file will always open on a PC as Read Only. The only way around the issue is for the PC user to manually change the permissions using the Security Tab in the file preferences or for another Mac to access the file and save a change prior to the PC trying to access it.

The second, intermittent issue is with Excel file Read Only problems. When that happens, neither Mac nor PC can access the file and are required to make a copy of the file to work on.

I have spent the better part of two months troubleshooting this issue with Apple - regular tech support, XSAN tech support, and finally a paid support incident with Apple Enterprise Engineers. They have been unable to solve the issue. I am just now finishing up a paid service call with Microsoft and do not expect any better results from them, although they have been very responsive and are trying hard to help.

This problem occurs in my production setup, but I have duplicated this issue on a test setup of 10.5.6 and 10.5.7. The test setup is OS X Server software setup as a Open Directory Master and as a PDC, with DNS, AFP, and SMB all running. The clients are authenticated at OD clients and are logged on as such. ACL's propagate to the Mac and the PC, but the .ppt files will still only open as Read Only. I have two clients, one Mac and one PC (Win XP, fully patched).

I have patched the smb.conf file with nt acl support = no, but it did not work. I have tried everything Apple has suggested, as well. I have prowled the web and lots of forums looking for an answer, again without luck.

If you've seen this problem

Another case of Mac 10.5.7/Office file sharing permissions changing

Monday, August 10, 2009

Kristi Herzer responded to a report about permissions randomly changing with Microsoft Office files on an SMB file server:

I am a fill-in administrator for a network of Mac G5s running OS Leopard 10.5.7 and have had issues of late with permissions randomly changing to read-only while a coworker is actively working. When changing the permissions back to read-and-write I often have to reboot to have access as the administrator.

The files are not on the local hard drive, but the user in question is directly connected to the drive on which the files reside. I don't know if this makes a difference, and no one else has reported an issue when they connect to the drive and work off of it.

If you've seen this problem

Theory for problem of SMB file permissions changing

Thursday, August 27, 2009

Clay Murphy has a theory about the problem with SMB permissions randomly changing with Microsoft Office files, but sees it with Quark files:

I'm a Leopard user on a Windows 2003 Server and experienced this issue as well. Primarily with Quark docs that are saved across a network. We are troubleshooting this currently and it seems to be a switch overload issue. Not confirmed yet.

If you've seen this issue


LEOPARD 10.5.8 TIPS AND REPORTS

Reader says 10.5.8 update breaks Windows SMB file sharing

Thursday, August 27, 2009

Chris Simons reports that the Mac OS X 10.5.8 update cause a problem with access to an SMB Windows server:

I wanted to let you know about a problem I found with the 10.5.8 update. We connect our Macs to a Windows storage server and create an SMB connection to the server for the drives to allow access. The new update has caused an issue with this. We can see most folders and files but some folders don't show as a folder icon or if they do show and we open it up there are no files there. I have checked the server and the files are there. I have also checked from a Tiger OS based Mac and it works just fine.

If you've seen this problem

Current news on the MacWindows home page.


TIP: Microsoft security patch fixes Mac file browsing issue with Vista, Server

Monday, December 21, 2009

A Microsoft security update for Windows 7 and Vista and Windows Server 2008 enables Mac OS X to browse for file shares on those systems, according to a reader. Peter Goddard reports that the security patch turns off SMB 2.0, enabling Mac OS X from Tiger to Snow Leopard to browse. An ArsTechnica article describes the patch in terms of plugging a security hole, but Goddard said it fixed file sharing browser on all his Macs:

I have not been able to browse network shares in mixed Vista/OS X 10.4-through-10.6.2 networks. They are accessible by go->smb://[share_ip_or_name] no problem but they never show in the Finder sidebar until after I_ve used go->

I have been studying this problem for months with no success until today. Following the instructions in the linked article I was able to download a Windows quick-fix that disabled SMB 2.0 and bingo. All the shares on my Windows 7 machine are visible. As I applied the fix to each Vista machine on my VPN, they all appeared with all their shares when I click on "All", under Shares in the sidebar. This is a solid fix for me. I hope it helps someone.

If you've tried this approach


Leopard problem saving Word files to Windows Server

Tuesday, June 1, 2010

Andy Macdonald is seeing the problem saving .docx files to Windows Server from within Word. This widely reported problem in Snow Leopard was fixed with the Mac OS X 10.6.3 update. However, Macdonald sees the problem in Leopard, and cites a report of the issue from five years ago:

Just to add that our users are experiencing a similar problem on Macs running Leopard (10.5.8) bound to Active Directory and Open Directory, authenticating against AD.

When trying to save a new Word for Mac 2008 document in default .docx format to the home directory on a Windows Server 2008 share, gives the "Word can not save ..." error message and creates a zero byte file "Word Work File D_{number}.tmp" in the folder.

One workround we found in our environment is to save in .doc format (Office 97-2004) - no problem.

Interesting to see reports of a Microsoft guy working hard on very similar problems in 2005!

If you're seeing this problem in Leopard


Reader has printing problem with Leopard, Parallels | Top of Page |

This item has been moved to the MacWindows Parallels Desktop Tips and Reports page.


Boot Camp Leopard: Win display settings change to default when rebooting in XP | Top of Page |

Tips and reports for Boot Camp issues in Leopard have been moved to our Boot Camp in Leopard Tips and Reports page.


Some VPN clients incompatible with Leopard | Top of Page |

Tips and reports for Virtual Private Network issues in Leopard have been moved to our Leopard VPN Tips and Reports page.

MacWindows Leopard VPN reports:

http://rz


Leopard and Active Directory

Tips and reports for Active Directory issues in Leopard have been moved to our Active Directory and Leopard Tips and Reports page.

- Active Directory and Leopard Tips and Reports:


Other MacWindows Departments

| Tips and Problem Reports | Product Solutions | News Archives | Site Map |
|
MacWindows Home |

| Top of Page |

Serving the cross-platform community since November 15, 1997.

This site created and maintained by
Copyright 2007-2010 John Rizzo. All rights reserved.