Calendar mavericks client - snow leopard server

I am trying to connect calendar on a iMac running mavericks 10.9.5 to a Xserve running Snow Leopard 10.6.8
Where I have clients that I have upgraded from earlier versions of OSX to mavericks the calendar is still connected and is working correctly.
However this new system has been freshly installed with Mavericks and will not connect with errors such as:
Error Domain=CalSubscriptionErrorDomain Code=-1002 "The operation couldn’t be completed. (CalSubscriptionErrorDomain error -1002.)"]
Calendar[570]: [com.apple.calendar.iaplugin.log.CalInternetAccountsPlugin] [Autodiscovery error: [Error Domain=CoreDAVHTTPStatusErrorDomain Code=404 "The operation couldn’t be completed. (CoreDAVHTTPStatusErrorDomain error 404.)" UserInfo=0x6100004660c0 {CoreDAVHTTPHeaders=<CFBasicHash 0x610000466100 [0x7fff72d0cf00]>{type = immutable dict, count = 11,
The machine has been joined and bound to the "domain".
I have tried setting the calendar account to "Auto" - "Manual" and "Advanced"
I have configured it the same as other working systems - but still cannot connect
Can anyone advise of any workarounds or fixes for this issue please
Regards
Tony

The answer is to use the "advanced" setting for configuring the account - then enter the username in the format of
[email protected]
enter the server name in the server field
and I am now connected

Similar Messages

Lion client snow leopard server

I had 30 macbooks running 10.6 authenticating to a snow leopard server. All worked really great. 15 of the laptops were stolen and now I am in the process of replacing them. However, I am finding the macbook is no longer made and I will need to use a macbook pro. Macbook pros come with lion installed. Will Lion clients authenticate to a snow leopard server? Can I create home directories on the the server for lion clients as I have done with my snow leopard clients. Any suggestions would be appreciated. Thanks.

Hi
"Will Lion clients authenticate to a snow leopard server?"
Yes. Snow Leopard Server will support 10.5, 10.6 and 10.7 Client OS.
"Can I create home directories on the the server for lion clients as I have done with my snow leopard clients?"
Yes. AFAIK home folders are not dependent on the OS version in any appreciable way. Granted there are some very minor differences but as long as the Desktop and Library folders exist within the parent container and are read/writable for that user that's all there is to it.
HTH?
Tony

How to sync to Snow Leopard Server wiki group calendar

I'm running the Mac Mini Snow Leopard Server in our law office of 8 attorneys. We all use PC's with Outlook 2010. We don't have Microsoft Exchange Server, and we bought the Snow Leopard Server because of its advertisement that you could achieve the same results on it as on Exchange Server, but without the cost. SOUNDS LIKE-------OH WELL. We want to be able to see everyone's calendar events on 1 calendar if possible. I setup a Group Wiki for the group "Attorneys". When I open that wiki, I've set it to be accessible by all attorneys in the group. When the attorneys accounts were setup in Workgroup Manager, the Attorneys group was also setup, and they have access to the group. I've been trying to figure out how to do this, and the result that seems to come closest is the Wiki Attorneys Group Calendar. I have setup separate calendars in it for each attorney. And so you can see them all on one screen, or deselect and only see the calendars you want. Now the problem is how do I get the existing events off of Outlook 2010 on each machine and into the respective calendars in the Group Wiki, and also update that calendar as events change on each attorney's Outlook calendar? If there is some better way to do this I'm certainly open for suggestions. I don't believe that you can "sync" the iCal client calendar with the Wiki Calendar. If you can that might also be a solution. Thanks.

Not_So wrote:
I went to the AppStore and as I was running Snow Leopard Server it prompted me to purchase Lion Server which I didn't want.
Luckily, I wasn't asked to purchase the 'Server' when I upgraded from SLS to Mountain Lion via the AppStore. I think your particular problem was mentioned in some other posts where the upgrade path to Lion became an infinite loop (hmmm... ). But that's all in the past now. Glad it all worked.

Can I use Snow Leopard Server with Windows clients?

Mainly for e-mails and calendars. I have small office with 12 windows computers from XP to Win 7 and MS Office from 2003 to 2007. Will Snow Leopard Server work with that?

Can Mac OS X Server do this? Sure.
You're going to be learning a whole lot about running a server, regardless.
You really need to sort out what you have here and where you want to be, and how to upgrade or replace yor migrate your environment, and before you add the substantial increase in complexity of serving Windows from Mac. If you can't get off of Office circa 2003 or similarly old software, what are you going to do when you find, say, an incompatibility, or a need to migrate mail clients? Who are you going to call for help?
I'd guess that Small Business Server (SBS) is likely your best target here.
AFAIK, Exchange Server (which I'm guessing is what you're using) supports larger mailboxes in newer releases.
Look at the sustaining costs for what you're considering purchasing, too. How much it'll cost to configure, deploy and maintain the box and the network. Up-front costs are an obvious consideration, but maintaining many boxes and many versions itself introduces costs.
The arrival of Lion Server next month does not change my opinion. (And I'm not usually suggesting Windows and Windows Server boxes, either.) (And with the arrival of Lion and Lion Server, I'll follow my usual approach and not look to upgrade to the first release of that (or any other) new platform, if there are business-critical functions and services involved. You need time to debug and test the deployment.)

Snow Leopard Server iCal push not working on iMac clients

Hello,
I have a new installed mac mini snow leopard server and updated osx with all the latest updates.
I am running the iCal server and the Push service and everything seems to run OK.
I have 4 brand new iMac clients which share calendars between the different users,but the iCal Push function doesn't work at all. Even when I change the update method in the iCal client to interval of 1 minute, it doensn't update.
The only way the calendar updates is to choose "Refresh" from the Calendar menu in iCal client.
The push function for the mail clients do work which is strange.
I already tried the following actions:
1. I have stopped and restarted the Push-service on the server
2. I have removed the push server settings in the iCal server settings on the server and added them again
3. I followed the iCal log file to see if an action of a client is immediatly visible on the server = OK
4. I've updated all the clients to the newest software
5. I have restarted the server completely
Does anybody have tips or advise to help me looking to find the cause of the iCal Push problems?

FYI:
Installing Snow Leopard Server into Parallels for DUMMIES!
http://forums.macrumors.com/showpost.php?p=17285039&postcount=564

Mavericks won't connect to Snow Leopard server share points

I have 3 imacs, running mavericks which won't successfully log onto Snow Leopard server share points.
The server appears on the list on the left and i get to a login screen when i select the server.
I enter the username and password and the box just shakes.
However if I tick the "access as administrator" in the user prefs on the server, it can connect, however i don't want certain users to have admin rights.
The strange thing is, is that if i choose to login with a user name and password for one of the older macs (10.6), i can log in. But that defeats the object.
This is obviously an authentication issue between mavericks and SL.
Any one else had this?
Thanks in advance.

The "Trust, but verify" follows...
Launch the MS-DOS command box on Microsoft Windows XP.
Verify IP network connectivity with ping. Ping the Samba/CIFS server by IP, then by name. Ensure that the box you're connecting to is the one you think it is; that can be via telnet or web connections or otherwise; make sure your IP network is configured the way you believe it is, and you're getting to the host you think you're reaching.
If the IP address connection works but the domain name (host name) does not, then debug the DNS validity with dig or nslookup, and ensure the client can get DNS translations.
Verify that the [Windows registry settings|http://labs.hoffmanlabs.com/node/1590] allow access to Samba/CIFS shares.
If you're not running Microsoft Windows 7 and the x86 gear here supports it, definitely upgrade. Windows 7 is a vast improvement over earlier releases, including over Windows XP.

Will Windows Outlook clients be happy with Snow Leopard Server Mail Server?

Our network at work has a Windows SBS 2003 server - and 40+ XP PCs running office 2003 (and outlook 2003).
Can I set up Snow Leopard Server so that the Outlook 2003 clients will be able to use contacts, calendars and mail etc from the mac (mini) that we would purchase for this?
I'd love to get everyone on Mac here, but we can't cos our core application is windows only and we would still need the MSSQL server. I know - we could install parallels or virtualbox for the windows apps but that is extra expense, and tbh I don't think our users could cope.
Thanks

Hi
+"Can I set up Snow Leopard Server so that the Outlook 2003 clients will be able to use contacts, calendars and mail etc from the mac (mini) that we would purchase for this?"+
For mail yes. For calendars you will need 'assistance' using 3rd-party applications or helper utilities. The iCal Admin manual has more details of what is available:
http://manuals.info.apple.com/enUS/iCalServerv10.6.pdf
Page 12. For Addresses/Contacts consult the Address Book Server Admin Manual for more details:
http://manuals.info.apple.com/enUS/AddressBkServerv10.6.pdf
Page 12. I don't see anything specifically listed so you may have to search for these yourself unless someone else posts with something more specific that works?
If you're expecting Exchange-like functionality you will be disappointed. If you really must have the functionality you're used but also want to move to the mac platform a better prospect (IMO) would be Kerio Mail Server:
http://www.kerio.com/connect
Depending on what other services you may or may not want you may not necessarily need OSX Server? Then again you could as easily install KMS on a Windows or Linux box instead. In which case why swop from Exchange?
Tony

How do I upgrade Snow Leopard Server to Mountain Lion (client)?

I have a Mac Mini Server edition (2010) with Snow Leopard Server (10.6.8) pre-installed. I don't like the interface of Server edition because 1) I don't need the server functions and 2) I prefer client OS's easier (less powerful I know) interface to do sharing, logging in, configuring.... etc.
(I know I should've bought the non-server version with a DVD drive but I can't take it back now.)
My question is, what's the easiest way of changing it to a 'client OS', preferably to the latest Mountain Lion? From forum posts it seems downgrading from 'server' to 'client' will definitely require a fresh install. That's fine. I can move all my personal files to the second HDD in the Mini and do a fresh install of OS on the first HDD.
I can see 'Mountain Lion' upgrade in the App Store, but it doesn't say if it's server or client. I am assuming it's a server upgrade?? What will happen if I purchase it for £13.99 in App Store? Or is there an alternative way?
I have a USB Apple optical drive. I have a USB thumbdrive too for storing the OS image if required. Thank you. Any tips will be appreciated.

Not_So wrote:
I went to the AppStore and as I was running Snow Leopard Server it prompted me to purchase Lion Server which I didn't want.
Luckily, I wasn't asked to purchase the 'Server' when I upgraded from SLS to Mountain Lion via the AppStore. I think your particular problem was mentioned in some other posts where the upgrade path to Lion became an infinite loop (hmmm... ). But that's all in the past now. Glad it all worked.

Windows 7 (Client) map a network drive VPN Snow Leopard Server

Hi,
I have a Mac Mini Snow Leopard Server and are using a VPN service.
My services on the mac os x sls server are: AFP, DNS, Firewall, Open Directory, SMB and VPN.
I can connect the VPN from Mac clients and Windows 7 clients, but I can only map a network drive/share point on Mac´s.
On Windows 7 I get an error: path or name not found ( I am sure using the correct path, same from Mac client that works).
When I am using my internal network LAN I can map a network drive using Windows 7 and Mac but outside over a VPN not (only Mac works).
The only service, at this moment, that I need is File Sharing outside my network LAN using a VPN.
How can I map a network drive from a Windows 7 client using a VPN, is there any Firewall rules / SMB rules / File Sharing rules that I missed on the server side?
Thank You.

I really don't know what are going wrong with my settings. As you said/write it must be an easy setup.
I'm using a Time Capsule and used the Server app to add VPN to the port forwarding also.
When I am connected thru the VPN I tried to ping the Server IP and got no answer from it, from W7 client!?
My Mac's are just working fine with AFP and SMB share points thru the VPN.
I think I have missed some settings from the SMB or Firewall services for VPN with W7 client's or it is a Windows issue.....

Lion Clients 10.7.4 show network accounts are unavailable and server is not responding when binding to Snow Leopard server 10.6.8

Hello,
I am running Snow Leopard Server 10.6.8 and my clients are Lion 10.7.4. While testing I had no issues binding 10.7.4 to our 10.6.8 server's OD. I created a 10.7.4 image to push to all of our machines and in the beginning of last week I was able to push the image and get the machines to bind with OD and apply preferences on these machines through workgroup manager. Towards the end of the week though this stopped working. Now any time I bind a 10.7.4 client to OD it allows me to perform an authenticated bind and the machine shows up in workgroup manager but immediatley after binding the client the status jelly next to the OD server in the directory list is red and says "This server is not responding". If I reboot the client I get a notification that "Network accounts are unavailable" at the login screen. My preferences from workgroup manager are also not applying, which is my main concern because without workgroup manager my mac server is somewhat pointless as we use it for very little else.
I've since tried to bind a snow leopard machine (10.6.8) and this still is working with a green status jelly. I've also built a lion machine from scratch, updated to the 10.7.4 combined update and am still getting the same issue where it shows the server is not responding when binding to OD. I then applied the subsiquent OS update after the 10.7.4 combined update but the problem still persists.
Is anyone else having this issue? Any help would help me keep my sanity.
Thanks,
Dane

Have you had any luck finding a solution to this? The only thing I have found was to unbind and then bind without authentication. Any help with progress on your end would be appreciated!
Nick.

Are there any problems with Snow Leopard Server (Xserve) and PPC Clients

Hi,
are there any problems identified yet with Snow Leopard Server, installed on a Xserve and PPC Clients running Mac OS X Tiger and Leopard?
Currently I have a Xserve Intel running Leopard Server and about 12 Mac Minis PPC running Mac OS X Tiger and Mac OS X Leopard. The Xserve serves services like DNS, OpenDirectory, Software Update Server, NetBoot, etc. All users have Home Directories stored on the Xserve.
Now I want to install Snow Leoaprd Server on the Xserve, but I wonder if there are any problems using the PPC Clients? I have read something like this on a german website.
Thanks!

We've actually found that the Server 10.6.3 DVD does an amazingly smooth job of upgrading 10.5.8. We've been upgrading our production servers and nothing has gone wrong yet. Snow Leopard employs an archive and install method of upgrading which results in an install which is very close to a clean install. So it's been very convenient for us because our servers are used as Windows PDCs and it's a pain in the *** to have to re-join all PCs to the domain if we start from scratch.

Windows VNC clients cannot connect to Snow Leopard Server native VNC server

I am resurfacing the following related comment made in another post that discusses the same issue I am having with VNC on Snow Leopard. This is still an issue and I cannot connect to our Xserve's Snow Leopard Server with a VNC client on Windows.
I don't want to install another third party VNC server onto our SL Server, and am looking for a VNC client for windows that will connect to our SL Server.
Does anyone have any solutions?
== QUOTED TEXT BELOW ==
Re: Newbie: Connect Windows -> OSX Server
Posted: Nov 4, 2009 9:26 AM in response to: Antonio Rocco
I would politely disagree. Yes, definitely, the Mac 'Screen Sharing' app works a treat, and Apple Remote Desktop.app works as well, but I am coming from a Window's PeeCee.
For me, connecting to my 10.5(.8) Server via tightvnc gives 'Server did not offer supported security type!". Using RealVNC to this machine states "No matching security types Do you wish to reconnect to ... ?" a telnet to this AppleVNCServer service (port 5900), shows RFB 003.889 *, or Remote Frame Buffer Major 3, minor 889.
Also, connecting to multiple 10.6(.1) Clients with Tightvnc correctly asks for a password but then hangs at "Status: Security type requested". Using RealVNC opens, connects, asks for authentication, and exits. Telneting to this AppleVNCServer service (port 5900), also shows RFB 003.889 *.
The Current Version of the protocol is supposed to be 3.8, that is Major version 3, minor version 8. Not 80 or 800 but Eight). http://www.realvnc.com/docs/rfbproto.pdf and I believe that tightvnc only supports up to version 3.7.
On each station I have installed the 'old' OSXVnc.app as a service (to a unique port). OSXVnc utilizes protocol 3.3 and I can control them successfully, but that is of my own doing because of this issue.
Now JollysFastVNC works a treat to any machine I have EVER tried to connect to. I have not tried COTVNC or any of the others (too slow for me, when they wer e around)
Also, I just noticed that RealVNC states that their free and personal version will not connect to Mac OSX (x86 and PPC) but the Enterprise one will. I just Dl'ed the Enterprise Viewer and it gave essentially the same thing ('protocol is not valid' message, even after it asks for a password). Anyway, I am not here to hijack this thread, just trying to keep the info flowing and open.
Maybe I am the only one with these problems but the bottom line is I cannot use Real or Tight, or UltraVNC to administer my server or clients as long as AppleVNCServer gives out the 003.889 protocol version.
Peter
* The ProtocolVersion message consists of 12 bytes interpreted as a string of ASCII characters in the format "RFB xxx.yyy\n" where xxx and yyy are the major and
minor version numbers, padded with zeros.

Searching on the net brought me to the same solution that Mr. Hoffman found as well, I was a bit skeptical at first but since he recommended it, and all my other attempts failed, it was a last resort and I have some additional notes of my own for a successful solution. Read the two links below first before doing anything, as they contribute to the solution in tandem.
http://forums.macrumors.com/showpost.php?p=7221295&postcount=20
http://forums.macrumors.com/showpost.php?p=9081641&postcount=28
I should probably just create an entirely new post with all of the steps that worked for me, but it's rather straightforward nonetheless.

Snow Leopard server, Lion clients

Good day I am running a 10.6.8 server (Mac Pro 2010) with 300 user account on it. At this time because out client computers needing compatibility with multiple applications upgrades we need to upgrade all out clients to 10.7.3. The decision has been made and I need to go with it. The server only runs user accounts, shared folders, Wiki and DNS. I am hesitant to upgrade the server to 10.7. I have attempted some quick searches for any issue with running 10.6.8 Server and 10.7 clients but it has not resulted in much.
What is the biggest issue I am going to be running into?
Will AFP still work with 10.7 clients?
Should I upgrade the server to 10.7 also?
What will I loose at this point upgrading everything?
Looking forward to what I can learn.

What is the biggest issue I am going to be running into?
What issues will you run into if you upgrade your clients to Lion, but leave your server on Snow Leopard? none. That's entirely valid.
Will AFP still work with 10.7 clients?
Yes
Should I upgrade the server to 10.7 also?
Not unless you specifically need some of the features in Mac OS X Lion Server, and absolutely not if you only have one server.
What will I loose at this point upgrading everything?
Probably several nights' sleep. Upgrading a server, and maintaining all the services without any downtime is a significant process. Snow Leopard Server doesn't stop running just because Lion is available, and it won't stop when Mountain Lion comes along, either.
If your mandate is to upgrade the clients, then do that, and take your time planning your server upgrade/migration.

Lion clients with Snow leopard Server

Are there known issues with a Snow Leopard Server Mananging Lion Clients. I currently manage 40 IMacs in two labs
all running Snow Leopard, the only services I use on the Mac Server are Open Directiory, Print Services, AFP, and FireWall services
the Server is a Mac PRo with 2x3.2 Ghx quad-Core Intel Xeon Processor and 32. GB RAM

Snow Leopard can't serve AFP devices to Lion clients out of the box. There seems to be a workaround, but I haven't gotten it working myself yet.

Snow Leopard Client Dock Behavior & Binding to Snow Leopard Server

Hi,
I am at a loss on this issue. I am running a test server and client. I had bound my client to the server and was having difficulties with the dock settings on the client. I assumed it was a managed preferences issue on the server, so I checked all the ones I knew to check. It didn't appear that my client dock was being managed by my server. The problem was that the dock would switch from auto-hide to fixed and the preferences under dock could not be altered on the client.
I've found that the only way to resolve this problem is to unbind the client from the server. Can anyone tell me what I need to be looking for within the server? Could there be an inherited preference from somewhere within the server?
The other element to this is that this issue didn't arise until after I upgraded to 10.6.3. Prior the upgrade I was bound to the server, and the dock was fine. After the upgrade the dock preferences on the client were no longer able to be managed.
I am new to server and need some help.
Thanks

Thanks!
So, when I click Join..., type in the server, and then click on the Set Up Services button, I enter the username and password for the account I created on Snow Leopard Server. It switches the sheet to show that it's "Joining the server", and then fails with: "kGotAuthenticationFailure". The Password Service Server Log shows that is actually succeeded: "AUTH2: {0x4b5897f87cada0f20000001500000015, diana} DIGEST-MD5 authentication succeeded".
If I actually enter an incorrect password, it right away gives me an "Authentication failed" message right below the password dialog in red.
The console on the Snow Leopard client shows:
10-01-21 11:10:16 AM System Preferences[248] -[ODCOSXServerJoinController(XSServiceDiscoveryProtocol) gotServicesInfo:fromServer:error:]: got error kGotAuthenticationFailure
I don't see any other messages on the server that might explain this. Any ideas?
This server was upgraded from Leopard Server, if that matters...

Calendar mavericks client - snow leopard server

Similar Messages

Maybe you are looking for