Benches macOS

15

address book sharing slow

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

hello, it is now two weeks we are running our new MACs . we are all 10.6.2 (3 clients + 1 mac mini server)

I was able to create a shared address book adding the same account on each clients.

What I see is that it is really slow, useless for business applications, you can wait for minutes after you click on one contact or jump from one group to a different one.

our database is made by 1000 contacts and approx 6Mb

any idea?

thanks.

15 replies

Sign in or join Beachball Help to reply.

  1. 0

    X9--__

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Join the club. This service prominently featured in SL Server sales literature is, to be charitable, not useable with many contacts. Our database is about 3400 so maybe it works with less than a thousand, Apple support could not tell me. To save you some trouble it is not your hardware as we are running a quad-core Xserve and have increase RAM to try to get this to work to no avail. We were told early on in the 10.6 life cycle that we should use a shared MobileMe account. Works better that Address book sever but not reliable - sometimes doubles contacts, sometimes we find differences between Address Books on different Macs, etc., etc.

    Also, I cannot recommend Daylight. Wrestled with it for 5 years and finally gave up to try Address Book Server when Apple released it on SL.

    Sure seems like this should not be so hard!

    Hg

  2. 0

    UV2008

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    This "solution" is so ridiculously slow that it is completely unfunctional. Come on Apple, please provide us with a way to share contacts across a business enterprise!!!

    Also, please allow those same contacts to be shared and synched with the iPhone. The left hand (server) finally recognizes that there is a need for shared contacts, and the right hand (iPhone) software doesn't support it?! Aarrrgghh! This is so terribly frustrating.

  3. 0

    reco

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    same here...

    crazy slowwwwwww

    please fix this for 10.6.3

    thanx

  4. 0

    jezzap

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Yes, us too.

    We have a Mac Mini server with Snow Leopard Server 10.6.2 and a shared address book of 4,500 cards and it's very painful to use!

  5. 0

    jezzap

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    It turns out, for us at least to be DNS issue. We have assigned a public IP address to the server and setup the A record for the domain name we want to use.

    We then used this domain name as the server address. However, as yet the PTR record is not correctly set so the reverse lookup is not resolving correctly.

    Changing the server address in the Address Book prefs to server-name.local appears to have fixed the issue and the shared address book is (for now at least) working as expected.

    4,500 entries, approx 46Mb

  6. 0

    jezzap

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    May have spoken too soon with that last answer.

    It didn't work. Still slow as ****.

    Have now had our revere DNS entry setup properly.

    Will see if that makes any difference!

  7. 0

    GM1977

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Does anybody tried the 10.6.3 ?

    Is it fixed?

    Thanks

  8. 0

    GM1977

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    well, I've done both mac and mac server 10.6.3 combo update, installations 100% OK

    SHARING THE ADDRESS BOOK IS STILL WAY SLOW !!!

    any comments?

  9. 0

    jezzap

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    We have also updated both server and client to 10.6.3

    No improvement!

    Surely this can't be right - it's a key service of the server.

  10. 0

    Make It Happen

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Just so you all know you're not alone, I, too, am in this situation. This is ridiculous that even a 30MB address book sharing across the network via the server should
    not cause the server to freeze up like it does and also effect all the client computers connected to that user calendar.

    It's down-right silly at this point that this can't be fixed. The idea is better than any other solution out there but still cannot be executed. I'd just as soon go back to SpanningSync and sync up to google.

    :-/

  11. 0

    GM1977

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    we are getting very disappointed by this problem.

    sharing contact over the server is a key factor for our company, I afraid to say that this was one good point of using Outlook with business contact manager in Windows ...

    Apple is promoting this feature and everybody can see it at
    http://www.apple.com/server/macosx/features/addressbook-server.html

    Is there any way Apple will fix this issue ??

  12. 0

    JonGoldman

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    What has Apple's response been when you call them for support?

  13. 0

    Make It Happen

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    "I couldn't tell you. It seems like you have everything set up correctly. Try setting up a new user on the server and see if that works."

    Literally it seems that everyone there is sitting with their hands in the air on this issue.

  14. 0

    GM1977

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    ah! I didn't expect this kind of NO service

    it is just amazing

    We don't want to use Bento and or FileMaker to share contacts, Address Book for us is fine and it has to work.

    I don't see the point to promote the server features if they don't work.

    Is it so hard to fix??

  15. 0

    GM1977

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    still no news??

    any good tip is welcome