Mac OS X 10.5 Leopard Cross-platform Issues

Reports and Tips regarding working with Leopard and Windows

Updated January 14, 2008


On This Page:

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


Deals from Amazon

Mac OS X 10.5 Leopard for $109

Check out Amazon for a copy of Windows XP or Windows Vista for Boot Camp


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.

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

Version History

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

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.

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

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

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.

Current news on the MacWindows home page.

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!

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.

Current news on the MacWindows home page.

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.

Current news on the MacWindows home page.

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

More Leopard file sharing problems seeing or accessing content

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:

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.

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.

Read current MacWindows news here.

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.

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.

Read current MacWindows news here.

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.

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.


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

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's Leopard can log onto Win server but can't copy files

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 win2k 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

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 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."

Read current MacWindows news here.


Users can no longer bind to Active Directory after Leopard update | Top of Page |

Monday, October 29, 2007

Dave McCristall's lost the ability to bind to Active Directory after a Leopard update:

I updated one of our Macs to 10.5 from 10.4 (as a test). Users were authenticating through Active Directory, but on this Mac, we've got nothing. I can't seem to get Leopard to bind to the Active Directory server.

Many more reports of Leopard Active Directory binding problems

Wednesday, October 31, 2007

Many readers are reporting the inability to bind to Active Directory after upgrading to Leopard that we first reported on Monday. Some are seeing dialogs that report an "unknown error." Others report an error message that says "Invalid user name and password combination." One reader said that his Macs freeze when they attempt binding.

Ryan Gilbert described his experience:

I am having issues with Leopard and Active Directory as well. After upgrading a system that uses AD auth I am no longer able to login with AD user accounts. Logging in with a local account and removing/re-adding to AD does not solve the problem.

I have also tried an erase and install of Leopard. In my case the computers 'seem' to bind to AD, but will not let any users log on using AD user credentials.

Bob DeSilets was able to get a Kereberos ticket:

I'm having the same problems authenticating to the AD domain after upgrading. Here are all the details I can think of:

    • I did an Upgrade rather than an Archive and install from a fully patched Tiger installation
    • When I first attempted to log in with my mobile account, I got an error message that said that there was a problem creating the mobile account (even though the local directory already existed)
    • I logged in to a local admin account, unbound the machine from the AD domain in Directory Utility, and re-bound the machine to the domain. No luck accessing the mobile account.
    • I am able to get Kerberos tickets from both the AD domain and our central campus Ticket Granting server
Rob Groome is getting the "unexpected error" messages on multiple Macs:
I have the same issue with binding AD to Leopard. I have an Intel Mac and when I try to bind to the domain, which worked flawlessly on Tiger, I get an error message.

From the Directory Servers Tab under Directory Utility, it says:

Unable to add the domain. An unexpected error of type -14090 (eDSAuthFailed) occurred.

Or, from the Services tab and clicking on Active Directory, I get the following:

Unable to access domain controller. This computer is unable to access the domain controller for an unknown reason.

I love the unknown reason - it's really helpful in troubleshooting! This also happened on two other systems with fresh installs and one with an upgraded install. Same error on all 3 systems.

David Marcus's Macs freeze when they try to bind, and found a workaround, of sorts:

I can relate to your post "Reader can no long bind to AD after Leopard update." As far as we're concerned the bind on the AD literally froze the MacBook Pros concerned (2 different machines) to the point where we had to make a hard reboot. Removing the domain in the Directory Utility removed the issue immediately. The downside is that the users cannot benefit from full AD integration.

We noticed the origin of the problem as the Macs didn't freeze if connected outside the AD's LAN.

Stephane Rossan gets the user name error message:

I upgraded my Mac Pro to Mac OS X 10.5 this morning, and I can not bind to AD. I unbinded it and try to bind it again, but I cannot anymore. I have an error message: Invalid user name and password combination. You provided a user name and password combination that is invalid. You should check the user name and password and try again.

Obviously, I tried multiple times with no success. This morning, the error message was about a time difference between the client and the server.

Jay Rozgonyi found that he could not unbind after the update:

I'm clearly seeing problems with AD binding here at my University. We have our Macs bound to AD for authentication (laptops use mobile accounts), as well as to an Open Directory server for preferences. I left on Friday with my Tiger bound machine, booted into my mobile account at home, and did an Archive and Install of Leopard. I brought over the Network and User Account info, and I was running quite well over the weekend.

When I plugged in back at the office this morning, however, everything went wrong. Authentication was not being passed to AD correctly, and when our Windows guys recommended that I unbind the computer and then bind it again, I found that I was not allowed to unbind! Even a forced unbind (i.e., one not based on my authentication to AD) did not work. I'm now in the process of doing a fresh install of Leopard, bringing nothing over from the previous build or from Tiger, but I'm very reluctant to even attempt to bind to AD. The machine, by the way, is a two week old MacBook.

Fred Steputis:

I've tested 2 clean installs and 1 upgrade so far. Leopard seems to not allow network login when bound to AD. I spent several hours yesterday trying to figure this out. The binding works fine as in 10.4, all settings are the same except the listing of BSD/local as an authentication path on 10.5. I cannot get rid of the BSD listing under Directory Services.

I don't think we will be upgrading anytime soon.

Kenny Red:

I am have a massive amount of difficulty getting my new Leopard upgrade to bind to Active Directory. Every time I try it goes past validating my credentials and then give error "An unknown error occurred".

if you have these issues with Leopard.

Current news on the MacWindows home page.

Some Leopard users can connect to AD, but not without issues | Top of Page |

Wednesday, October 31, 2007

A few readers did report being able to connect to Active Directory with Leopard.

Alan Auman said that his logins are "horrendously slow:"

While I've been able to bind my Leopard upgrades to AD, the login for an AD user account takes up to 3 minutes to complete. Disengaging screensavers when using an the AD account credentials also suffers from this delay.

Derrick Rashidi was able to bind after multiple attempts:

I'm having the same issue with some differences. I did manage to get the laptop to bind, however I didn't do anything different. It just decided to bind. I can see the pc in AD when I do a seach, but when I logon to the PC locally (because I cannot logon to the domain) and check the Directory Utility, My AD Domain show the "server is not responding" message. At times this will show Green and the server is responding but still unable to logon to the domain.

Ben Zvan was able to bind as well:

I thought I'd let you know that I'm experiencing a similar problem to that listed on your site. Under 10.4, I was able to grab a Kerberos ticket from our AD server and then connect to AD SMB shares on our network using that ticket. Now, I'm prompted for a password when I try to mount the shares. One of our other tech areas is working on it, but they don't have 10.5 yet.

Suggestion for Leopard AD issue, and more reports of binding problems | Top of Page |

Friday, November 2, 2007

Readers continue to report problems with Leopard binding to Active Directory networks. One reader got it to work after multiple binding/unbindings. Another reports seeing it with Micrsoft's Services for Unix. One reader saw the same problem with the Leopard betas.

But first, Erik Ableson has a suggestion:

I've had no problems joining an AD domain after the Leopard update. I did have to delete the original AD Directory Services entry after upgrading and rejoin later since it really didn't like not being able to resolve the domain since I did the upgrade from home. General recommendation would be to leave the domain before upgrading and rejoin after the update.

if this worked for you.

Rick Shields had it working until he moved it to a mobile user account. Then he got it to work after multiple binds and unbinds:

Everything at first was perfect. I did a clean install and within minutes had the machine logged into AD 2 days. (I hadn't set it up to be a mobile user yet either.) Today, I decided that it looked good enough and moveed it to a mobile user account. I went to the directory utility and unbind. No issue. Made the change to allow the mobile account when connecting. Rebind. All lookd well, but I couldn't log in.

The window showed that the AD server was responding correctly and everything looked normal. But it didn't work. I could unbind/rebind with no issues, but no user could log in, not even my domain admin account.

Now, after multiple bind/unbinds and restarts it has started working again. I get my AD users to log in. Suggests to me that there is something holding onto something or something on the Mac when you unbind/bind.

Josh Warren blames the new Active Directory plugin:

I am just writing to confirm that I, too, have run into the problem of trying to get a 10.5 OSX (Leopard) iMac and Mac Book Pro to bind to AD. I don't think it matters whether it is a clean install or an upgrade. I want to say it is just an issue with the new AD plug-in Apple has issued with the new OS.

Carl sees the problem with the Macs accessing Services for Unix on the Windows server:

I'm also experiencing this. I however, am using MS Services for Unix and so have Directory Access in Mac OS X treating AD as regular LDAPv3 server. It worked great with Tiger, but after the upgrade to Leopard I can no longer find any AD users. It has something to do with its search path (I think) since the Directory Access program says the server is responding fine.

An anonymous reader saw this problem with the Leopard Beta. He also describes the symptoms:

I submitted a bug report on Leopard beta regarding AD binding and account creation months ago. This was for Leopard 9A559 and before, and it looks like it still exists in 9A581, the Golden Master shipping version. Apple knew knew full well that AD binding is not working.

Go back to Tiger 10.4.10. This is the very reason we are not on Leopard and won't be until Apple fixes this.

Here's the bug: you can indeed bind to AD via the Directory Utility. It reports as "AD Server Responding Normally." Log out or restart, it does not matter. You get the "Red Ball" at the OS X Login Window (meaning you have no connected directory servers, AD or OD, it should be a green ball).

You go to login with your AD user name / password and the Window just shakes, no dice, no login, never creates your AD network account (which is really local).

Reader says Leopard AD binding fails during step 5

Wednesday, January 9, 2008

Mark Staben is another reader whose Leopard Macs can't bind to Active Directory. He sees the same error message as another reader did:

I can't believe this isn't fixed yet. With regard to Rob Groome's "unexpected error," "Unable to access domain controller. This computer is unable to access the domain controller for an unknown reason."

This is exactly what I get when I attempt to bind. It happens at Step 5 during the binding process. It worked perfectly in Tiger.

I have about 100 machines waiting for Leopard and I bought the licenses the day it was released. Unfortunately, those machines will be sticking with Tiger until this is fixed.

More bugs with Leopard on Active Directory and a workaround (turn off Bonjour) | Top of Page |

Wednesday, November 7, 2007

Readers are reporting more buggy behavior with Mac OS X 10.5.0 Leopard on Active Directory networks. Many readers have previously reported problems with binding to Leopard to Active Directory. Today, we have readers reporting some other strange behavior surrounding AD binding.

Leslie Wong verified a previous report of very slow AD connections, but offered an odd workaround. She also reports a problem waking from sleep:

I have two Macs in a Windows Server 2003 environment (a ".local" domain) and was able to bind to the AD after a clean install of Leopard. But logins, like Alan Auman's, were "horrendously slow." Also, any operation that required administrator authentication were similarly slow.

I found, in the Apple discussions, that turning off Bonjour immediately stopped the problem. Logins were as fast as they were in Tiger. But turning off Bonjour caused other problems, such as not being able to start Aperture.

I also noticed a problem that when the Leopard machine wakes from Sleep, it was not always able to communicate with the domain. The Directory Utility would indicate that the ADD was not responding normally and a reboot was required for it to be "responding normally" again.

Justin Rummel found a way to log in using a mobile account:

My AD experience with Leopard has been interesting. After a clean install on my MacBook Pro, I was able to bind to AD but forgot to select "mobile account" check box, thus not being able to use the MBP at home. I returned to the office the following day, checked the box and was working fine until I restarted. My username and password (both as entry fields) never authenticated. It wasn't until I used my local admin user (that was established on install) and used "Switch Users" that I was able to login successfully. The difference, the username was preselected for me. I switched the login form to be a list of users so I only have to type in a password. Everything is working as expected.

Eric Lukens said that Leopard does not authenticate accounts that are in sub-domains, which he suspects is a bug:

We've identified that Leopard does not authenticate accounts that are in sub-domains. We have a main domain forest with several sub-domains. The computer can be bound to any of the sub-domains or the main forest, but only accounts in the main forest will successfully log in. We've looked at the Directory Service debug logs, and the Leopard machine seems to find the account in the sub-domain, but doesn't not complete authentication. Also, Directory.app will only show names from the main forest, not the sub-domains.

So far we've been successful with accounts that are part of the top-level forest. Since the option exists in Directory Utility to "Allow authentication from any domain in the forest," I'd say this is a bug that should/will be fixed.

David Troup's discovered an odd bug:

I've just installed Mac OS 10.5 for the second time on the same machine, I can't get it to log onto the AD, even though it creates the computer account.

I've have found a nice little bug though, if you have the Mac connected to the AD and logged into the Mac as a local admin you can't create user accounts, it creates the home directory but not the user; as soon as you disable the AD then you can create as many accounts as you like.

Corwin Ip can't log in with his Windows account info:

On one machine, I did a Leopard upgrade, and could not login with my Windows account info. I logged in as a local admin and had to force unbind. There were no problems binding it back to AD, but still cannot login with my Windows account even though I had to use it to add the machine to the Windows domain.

The second machine was a clean install, same thing as first, except without the unbinding problem because it was never on the domain to begin with.

MGM, a Leopard beta tester, said that Active Directory was broken in the pre-release versions of Leopard:

In Leopard build 9A559, binding to Active Directory 2003 was not totally working. You could bind to AD, in Directory Utility, but it was then useless. Upon logout and when attempting to login/authenticate to AD for the first time and thus create your local profile, no go, the OS X login window just shakes, no login. The bug was filed, let's hope it is fixed in a shipping Leopard.

Jason Sheridan:

I am having this same issue with upgrading and with a clean install.

Current news on the MacWindows home page.

Reader says 10.5.1 doesn't help AD problems, nor does turning off Bonjour | Top of Page |

Monday, November 19, 2007

Brad Ong reported that the Mac OS X 10.5.1 updated did not fix Leopard's Active Directory binding problems. Turning off Bonjour, as another reader recommended, also did not help. In his report, Ong describes the procedure he used:

I did update the MBP to 10.5.1. It doesn't help. Brand new MacBook Pro, 2 weeks old. I've been administering Windows since NT4.

When I didn't bind the MacBook Pro to the directory, I was able to use Keychain to see my Windows server shares. Was able to get the MacBook Pro to use my Windows 2003 print server, and I was able to get Entourage to use Exchange to download my mail.

Started binding to AD and set it up according to the common procedures in the forums: Set up Directory Utility services with Create mobile account at login, Require confirmation. Use UNC path, all checked under "User Experience", set the preferred server to my main domain controller under "Administration". Clicked on Bind and the MacBook Pro was added to the domain.

The MacBook Pro showed up in the Active Directory Users and Computers. Showed up in DNS. I had to create a reverse pointer record.

So, the Active Directory plugin is enabled, "domain.local" shows up in the Directory Servers tab, all my computers show up in Finder "Shared." Printers still work well. Windows shares still work. Directory now shows all the users in my Active Directory listings. When using Accounts in System Preferences, the "Allow remote users to login" is checked and the Active Directory user names show up for "Allow these users to login".

Then I log off, click on login and the "Other." The login name shows up as expected.

Here's the problem: I enter all variations of domain\username, username@domain.local, etc. but all I get is the login screen shaking at me.

I tried the disabling of Bonjour as recommended at MacWindows, but that didn't help.

I tried restarting the laptop but that only makes the "Other" login name listing disappear. Then when I try to logon with my local admin account it takes forever. Sometimes I have to hold the power button down to shut off the MBP then power back up. This may allow me to login with the local admin account in a reasonable amount of time.

If I unbind the MBP from the domain, everything gets back to being really quick and snappy.

A suggestion for 10.5.1

Toni Weurlander of Finland avoided problems with Leopard 10.5.1 by NOT connecting in 10.5.0:

I just installed a new MacBook Pro freshly with Leopard, updated it to 10.5.1 and bind it to our AD. Everything just worked like it did on Tiger. Never tried to bind it with 10.5.0. All SMB shares seem to work as expected.

Reader verifies Leopard 10.5.1 binding to AD: avoid binding in 10.5.0

Thursday, November 29, 2007

Benn Kovco verified a suggestion from another reader for getting Leopard 10.5.1 to bind to Active Directory:

I've managed to get solid, functional AD connectivity after experiencing all of the issues describe in various forums. I finally got it to work by following Toni Weurlander's suggestion at MacWindows.

This worked for me, taking care NOT to even attempt to bind AD while still on 10.5.0. I posted more at the Apple Discussion forums.

Leopard Active Directory problems continue with 10.5.1 update

Wednesday, December 12, 2007

Stephanie Renken reported that Leopard's Active Directory problems were not fixed with Apple's 10.5.1 update:

I upgraded my AD bound Tiger laptop to Leopard, and could not log in after the upgrade unless I unplugged my network cable. I unbound the machine to get past this issue, and have never been able to rebind it using my credentials. I get the "Invalid user name and password combination” error. However, another admin user can bind my computer with no error. I'm now running 10.5.1 and still cannot bind this computer using my credentials.

TIP: Suggestion for Leopard binding to AD points to LDAP, Kerberos issues, in hosts file

Wednesday, December 12, 2007

Hugh Burt did some troubleshooting of Leopard's problems binding to Active Directory that many readers have been reporting. He found that Leopard was selecting different servers for LDAP and Kerberos. He discovered a way to get around it:

With Leopard, the Mac seems to ignore the priority settings for LDAP and Kerberos Services in the DNS, hence it kept selecting the DC that was behind the firewall, rather than a local server. The firewall allows LDAP access, but no RPC, Kerberos, etc. so the process would fall over with the unknown error.

As a work around, we added the name of the firewalled server to the machine's hosts file but with an invalid IP number. This then forced the machine to go off and try another server BUT then the binding would fall over right at the end with an "invalid username" message. A console message also said a password could not be changed.

Using wireshark again, we found out that the machine was selecting different servers for LDAP and Kerberos. It was using LDAP to create the account with one server and then using another server and Kerberos to set the machine's password. This second DC would then fail the process because it was not aware of the account that had been created milliseconds previously on the other server. (AD servers take about 15 minutes to replicate) so hence the slightly ambiguous but correct console message.

As a work around, we added all the local DCs to the host file but all with the IP of a single server. This made the machine use the same server for both LDAP and Kerberos and at last we got the machine to bind. Another workaround would be to manually create the account, wait 15 mins for the DCs to replicate so they are all aware of it, and then bind the Mac.

The sys admin also commented that the binding process "really hammers the DNSs" and that PCs do it much more simply. Also 10.5 does not seem to do reverse lookups which 10.3 and 10.4 did.

Hope this might help some people struggling with AD binding and perhaps someone from Apple may read it as well because the AD plug-in really does need some re-writing.

If you've tried this

Another report on editing hosts file for Leopard/AD issues

Monday, December 17, 2007

Jason Bennett sent us report on his progress with editing host files to get around the Active Directory problems in Leopard:

I saw your post on macwindows.com regarding the 10.5 binding and editing the hosts file. I edited /etc/hosts to force all nine of our domain controllers to a single IP. Then I tried to bind and got the invalid username/password deal. Then I pinged the different domain controllers and they were pointing back to their real IPs.

I restarted the computer and pinged again and everything went to the IP I had in hosts. I thought maybe I was in the clear so I tried binding again and I got the same error. I pinged the servers again and they were back to the real IPs.

So I restarted again and pinged the DCs and they were all going off my hosts file again. Opened a terminal and pinged a server as I was trying to bind and it stayed with the hosts file but the computer didn't bind. Stopping and restarting the ping changed it back to the real IP after the bind failure. I then tried this with all of the domain controllers pinging at once as I tried binding and still no luck.

So that's where I'm at now, trying to figure out why binding to AD breaks free from the shackles of /etc/hosts.

Current news on the MacWindows home page.

Apple rep recommends lobbying Apple to fix AD-Leopard incompatibilities

Monday, December 17, 2007

Jem Dowse in London was given some advice about getting Apple to fix Leopard's Active Directory bugs:

I asked someone I know at Apple today about the various Active Directory issues that persist with Leopard. His advice is to escalate the problems with AppleCare, especially if you have one of their premium accounts. Chances are everything you say will be a known issue, but escalating it will be another prompt for Apple to prioritize some fixes. I actually got an apology of sorts from him. He said that this is completely new code and problems should be fixed in the next dot-release or two, but couldn't comment on time scale.

Me, I'm waiting for the day when I can bind just one machine to our domain even once. Till then we have 350 machines here that are definitely sticking with Tiger!

The Mac OS X 10.5.1 update did not fix these problems.

TIP: Use full domain name for Leopard AD bug; A reader hears from Apple

Wednesday, January 2, 2008

Michael Anderson provide another suggestion for working around problems with Mac OS X 10.5 Leopard binding to Active Directory:

I've seen this in several iterations and with several different symptoms. But it's been easy to fix. The problem is that the Leopard implementation is picky.

  1. Make sure your time zone is set correctly.
  2. Make sure your Date/Time are auto set by the system. Or that it is VERY close to what the AD server is set to (if it's off by just a little it won't work).
  3. Make sure your using your full domain, as in "domain.company.ext." Not just the short name for it.
  4. Make sure the checkbox to allow domain administrators to administer the box is checked.

That's it. I have had a few different error messages. And if I double-check all four of these things, it has works every time: 18 and counting.

If you've tried Anderson's suggestion if it worked for you.

Keith Cox reports that Apple told him that the problem is with large networks:

We have the same issues with computers not being able to join the domain. I have talked to Apple and we have been told the issue is related to large domain of more than 64 DC's.

Readers verify " full domain name" tip for Leopard AD bug

Friday, January 4, 2008

Two readers report success with a tip from Wednesday (directly above) on enabling Leopard to bind with Active Directory.

Tom Stovall:

Yes, AD sign-in does work for me if I use a fully-qualified active directory name eg... jrizzo@division.company.ad

Adrian Stancescu focused on Step 4 of Wednesday's tip

With regards to the Michael Anderson's tip, it seems to have worked for me. The only thing I did differently when trying to bind my Mac was Anderson's Step 4, to check the box that allows domain admins to administer the computer.

Everything works now, including accessing the GAL through AdressBook or through the Directory application. I am amazed. I have even managed to log in with my AD account and it worked fine.

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 filee, 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 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

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 on our Leopard Tips and Reports page.


Boot Camp Leopard: Win display settings change to default when rebooting in XP | Top of Page |


Some VPN clients incompatible with Leopard | Top of Page |

Monday, November 5, 2007

Equinux said that VPN Tracker 4, its universal virtual private network client, is not compatible with Mac OS 10.5. The company said it was entering a beta testing phase for a Leopard-compatible VPN Tracker 5 because it would not be able to patch version 4. Equinux is now accepting applications for beta testers at it's web site.

Reader Jean-Pierre Isbendjian reports that Check Point Software's VPN client for Mac is not compatible with Leopard:

As I was suspecting, Check Point Secureclient is not working with Leopard. Secureclient gets disabled once Leopard is installed and if you try to reinstall it, the installer will not install. I hope we won't have to wait 10 months or so as was the case when Tiger was issued.

Juniper Networks SSL VPN client not working with Leopard | Top of Page |

Wednesday, November 7, 2007

Aaron Weis reports of another VPN client that is incompatible with Leopard. A workaround that was available for Tiger doesn't work with Leopard:

We use the Juniper SSL VPN at work. The small client applet ("Network Connect") is no longer compatible with Leopard. Worked perfectly under Tiger. There are hacks, which sometimes work, but these only work for a Tiger working install which has been upgraded to Leopard. There is no way to install and run Network Connect on a clean Leopard install. Evidently libssl.0.9.dylib and libcrypt.0.9.dylb libraries included in Leopard are PPC only versions, rather than Universal (as in Tiger)... whoops.

On Monday, we reported that Leopard is not compatible with two other VPN clients, Equinux' VPN Tracker and Check Point SecureClient.

Note that another reader noted this same .dylib error below.

If you've seen a VPN problem with Leopard

Juniper VPN client update fixes Leopard problem | Top of Page |

Monday, November 19, 2007

Brandon Edling reported that an update to the Juniper virtual private network Mac Client, Network Connect, fixes an incompatibility with Leopard:

This problem is only for Network Connect 5.5. As of 6.0r2, this problem has been fixed. Your VPN Administrator can get an update from Juniper, which will download automatically to the client when it connects and all will be well.

If you used Network Connect 6.0r2 with Leopard

Juniper VPN 6.0r2 may work in Leopard but is not the Leopard release

Wednesday, November 21, 2007

Phil Benware verified a previous reader report about the Juniper virtual private network client in Leopard, but with a caveat:

We've been testing Juniper Release 6.0r2 for about 2 weeks now. It does work with Leopard (10.5 and 10.5.1), and seems to work well, so far. The only problem is that supposedly this not Juniper's official Leopard supported version. What this means, as I've been told by our network admin, is that a later client/firmware patch could break Leopard connectivity.

TIP: Getting the Juniper VPN client to work with Leopard

Wednesday, December 5, 2007

Jaume Llardén Prieto commented on previous reports that the Juniper VPN client update (Network Connect 6.0r2) works with Leopard. It did work, but only after some manipulation:

I'm using NC 6.0r2 on a PowerBook G4 without any problems, but I had to install the DMG manually, as the automatic installation didn't work properly (either as administrator or with my user without admin rights). After that, double click the Network Connect icon in your Applications folder, type the complete URL of your secure gateway, log in and you're done.

Mac OS X 10.5.1 update fixes Cisco VPN problem | Top of Page |

Monday, November 19, 2007

Although we've had several reports of VPN clients not working with Leopard, Christopher Pearce is the first to report that the Cisco VPN Client for Mac OS X doesn't work with the first Leopard release. It does work, however, with the 10.5.1 update:

I could not get the Cisco VPN Client to recognize that my Leopard 10.5.0 Mac Book 2.2 GHz has a network connection. Hence it fails immediately with the message 'Cannot connect to VPN Subsystem'. Tiger has no problem with the VPN Client plus Remote Desktop connection to the Windows server at work.

With 10.5.1, it works!

If you've seen a problem with Leopard and the Cisco VPN Client for Mac OS X

TIP: Suggestion for Cisco VPN Client in Leopard

Wednesday, November 21, 2007

Steve Humiston offered a fix for Cisco VPN client problems in Leopard:

My suggestion for anyone with a Cisco issue is to reinstall the client (making sure it's the latest version AND Intel).

I have had both working since the beginning. After the upgrade to Leopard I did have to reinstall the VPN client as I got the same message but after the reinstall I was fine. At work I must use VPN to connect to various school systems. 10.5.1 did not break it at work or at home.

MacBook Pro and Mac Pro both confirmed working.

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

Reader verifies Leopard/Cisco VPN tip; new Cisco VPN client helps

Thursday, November 29, 2007

Ted August verified a previously reported fix for Cisco VPN client problems in Leopard:

I upgraded from 10.4.10 to 10.5, and, I had issues with both the Cisco VPN and Shimo after upgrading. However, re-installing both applications resolved all issues. In addition, Cisco has released a newer version of its VPN software. I've found this new version speeds up the connection process in Leopard.

Workaround for Leopard VPN bug: .dylb libraries | Top of Page |

Wednesday, November 14, 2007

John Holley reports a bug with Leopard's virtual private network software, and a workaround. He refers to a finding that another reader reported regarding the Juniper VPN client, that certain files installed on Intel Macs are actually PowerPC files:

For those running into problems with Leopard, on Intel machines, only installing the PowerPC versions of libssl.0.9.dylib and libcrypt.0.9.dylb libraries and hence causes apps that rely on them to fail. You just need to grab the libraries off a 10.4.x [Intel] system e.g. a backup or a 10.4.x install disk, from /usr/lib and replace them on your 10.5.

This had been bugged to Apple during the betas of Leopard but they still shipped it with the PPC only version of the libraries.

If you've tried this workaround

TIP: How to replace the libssl.0.9.dylib and libcrypt.0.9.dylb files to fix the Leopard VPN bug

Monday, November 26, 2007

Readers have previously reported (here and here) that Leopard erroneously installs PowerPC versions of two files on Intel Macs. Andreas Gast reports having the Leopard's virtual private network problem with Mac OS X 10.5.1. We also answered Gasts question about how to replace the files. Gast said:

I have a new MBP that was running 10.4.11 and my PPTP VPN worked fine. I cloned my Tiger config to a backup drive, then completed a clean install of Leopard (Erase & Install) and applied the 10.5.1 update, ran repair permissions (got the slew of "ACL found but not expected" errors and the SUID ARDAgent error), but no VPN. I need PPTP VPN access for my corporate network.

How do I apply the replacement of the Intel 10.4 libssl.0.9.dylib and libcrypt.0.9.dylb libraries)? I can't seem to navigate to the needed /usr/lib directory on my HD or my Tiger Install Disk.

You can get to the normally invisible /usr/lib directory from the Finder using the Go to Folder command in the Go menu. In the field, type /usr/lib. This will open the Directory as a folder, showing you all of the files.

On the Tiger installation DVD, you can get to /usr/lib directly. Insert the DVD (don't reboot) and double-click to open. Scroll down to the usr folder and double-click to open. Then double click the lib folder. Switch the folder window to list view to find the libssl.0.9.dylib and libcrypt.0.9.dylb files. You can then copy them to the hard drive /usr/lib directory with a simple drag and drop.

Does this work for you?

More details on replacing .dylib files to fix Leopard VPN

Thursday, November 29, 2007

Andreas Gast took our advice on how to replace the libssl.0.9.dylib and libcrypt.0.9.dylb files to fix the Leopard VPN bug, and it fixed VPN for him. He sent us some additional information on the procedure.

Thanks for the details needed for me to successfully correct Leopard's VPN ills. In addition to replacing the two files with their Tiger (Intel) versions I needed a few additional steps to get it to work. I am now successfully reconnected into my corporate VPN network.

Here is what I did:

1. Copied and replaced libssl.0.9.dylib and libcrypt.0.9.dylb libraries on Leopard from my working Tiger 10.4.11 /usr/lib

2. Ran Leopard Disk Utility from Install Disk and repaired permissions twice to see that the replaced files were corrected

3. Launched Leopard, created a new location in Network Settings

4. Created LAN config and checked connection to the Internet without VPN

5. Created a new PPTP VPN connection and specified the needed corporate DNS servers and search domains

6. Set the Service Order (via command toggle next to add service) so that the VPN is first in the Service Order list. Note: VPN didn't work without this.

I have tested this with both my wired 100 Mbps Ethernet interface, as well as my 802.11N Airport connection, via my D-Link DIR-655 Gateway (with latest Firmware Update 1.10, 9/4/2007). As noted above in #6, the VPN didn't work until I changed it to be first in the Service Order list in Network settings. Now it works as it used to in Tiger.

I have noticed some other oddities in Leopards Network connectivity that appear to be a throwback to some of the early Tiger maintenance releases (or even earlier) in that I am now having DNS resolution issues bringing up popular internet locations (e.g. Google or Google/ IG) when I switch from wired to wireless configs until I ping the address using Network Utility, then DNS works fine and the site comes up in Safari 3.0 or FireFox 2.0.0.9. Also, my saved WPA2 Login settings aren't being pulled from my Keychain to access my home WiFi network, and my SSL certificates from my personal domain and POP email ISP aren't being saved in the system even though I have accepted them. Those are the next few things to tackle once I finish transferring the rest of my data and apps from my Tiger image clone.

If you've tried this

Leopard problem with Banana VPN

Monday, December 31, 2007

Peter van Rijn reports a problem with Leopard and the Banana virtual private network system:

I was reading your articles on Leopard not being compatible with some VPNs. I just signed up with Banana VPN and it works perfectly on PC. I loaded it on my new Mac with Leopard 10.5.1 and it worked for about 2 hours and now I can't get I to connect. It says something about not being able to negotiate with PPP.

If you've seen this problem

IPSecuritas a replacement for CheckPoint VPN client in Leopard

Friday, January 4, 2008

Michael Landewe recommends the Lobomoto's IPSecuritas virtual private network client for Mac for CheckPoint VPN users who want to upgrade to Leopard:

There are a lot of frustrated CheckPoint VPN users that cannot upgrade to Leopard because CheckPoint won't run. I recommend IPSecuritas to them. It has worked for me: 100 percent CheckPoint and Leopard compatible.

Leopard VPN malfunction inside of virtual machines

Monday, November 19, 2007

Maksym Kortunov's Leopard virtual private network problems occur not in Mac OS X, but in Windows running in a virtual machine:

I've seen your note about VPN problems in Leopard at the MacWindows Leopard Tips and Reports page. I have a problem with VPN inside VMWare Fusion and Parallels. When I connect VPN in Windows on these virtual machines, it connects and stuck during user name and password checking. After some pause it says that the machine did not respond and do not establish the VPN. The same is in both Fusion and Parallels.

If you've seen this problem

TIP: Workaround for Leopard VPN malfunction inside of virtual machines

Wednesday, November 21, 2007

Alin Pilkington offered a workaround for Leopard problems with virtual private network connections in Windows in a virtual machine:

I've seen this problem also in Parallels. I believe this problem arises only after I try to connect from Leopard to the same VPN network that I connect to from XP while running Parallels.

I got around it by changing the Parallel Security Preferences (not Leopard; the Parallels application) to have the minimum security between Windows (I'm running XP by the way) and OS X.

Robin Jackson doesn't have the problem with the SonicWALL Windows VPN client:

SonicWALL seems to be working fine on my version of Parallels (latest Leopard compatible beta) and 10.5.1.

if this tip worked for you.

Reader fixes VPN-in-VM problem

Thursday, November 29, 2007

Maksym Kortunov solved his problem with getting a virtual private network connection within Parallels Desktop and VMware Fusion:

I just installed the most recent build version of Parallels [Build 5160] and it works now! I haven't tried reinstalling Fusion.

Last week, another reader suggested changing a security setting in Parallels.

Checkpoint VPN malfunction inside of a virtual machine in Leopard

Wednesday, December 19, 2007

Alejandro Lagar Salas is another reader reporting problems making a virtual private network client within a virtual machine in Leopard. This time, it's the CheckPoint SecureClient:

I have the same problem trying to connect in VMware Fusion with CheckPoint's SecureClient, it either gets stuck in the user name and password or it wont start running at all. I'm using Leopard on a MacBook Pro and Windows XP Professional in Fusion all installed in their latest versions.

Other readers have reported this problem with Leopard with both VMware and Parallels, and with other VPN clients. Our Leopard Reports page lists some workarounds to the problem.

If you've seen this problem

Another case of Leopard VPN malfunction within VM

Monday, December 31, 2007

Bruce Johnson is another user having problem getting a virtual private network connection from Windows running in a virtual machine in Leopard:

I'm having the same issue with a newly installed Leopard 10.5 on a MacBook. I had to apply the libssl and libcrypto fixes to get it working with our Windows PPTP server.

I get the long pause on "Verifying username and password" followed by an error 721 "The remote computer did not respond" using the shared Ethernet.

I get an immediate error 800 "Unable to establish a VPN connection" using the bridged Ethernet.

I'm not connected via VPN in OS X when I do this, and I installed Parallels via their download this morning, Build 5582.0.

Other readers have reported that the problem also occurs with VMware Fusion, only with Leopard, with different VPN clients.

If you know of a workaround

Current news on the MacWindows home page.


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 connecting 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.


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.

Current news on the MacWindows home page.


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-2008 John Rizzo. All rights reserved.