hi looks like i am struck here
tried to set rainlendar in ftp and http server both but failed.
Looks like there are no step by step guide for a noob like me
my steps:
1. copied the complete folder (.rainlendar) in the http shared folder.
2. from a client computer selected 'network shared calender' from calender -> options.
3. gave path to the 'default.ics' file and made changes to work offline mode and to update every 1 minute.
4. 'client computer' showed all tasks as in server. (GREAT)
5. But no update possible. It keeps showing data write failure in the host machine. If i update any task, after 1 minute the task is back to same as in host machine (server). (BAH)

Please tell me the solution. thanks in advance

Welcome to the forum.

The use of the Network Shared Calendar depends on which service/server you're using.
If you connect to a ftp/http site, I'm sure you can download all the events, but you can't update a copy of the calendar if the site doesn't allow it.
Is there any message/dialog when you say "data write failure"?

In the Help, User Guides/Examples section you have several ways to use NSC. The most common one is Google Calendar.

yes..
every time this comes..
but i can easily overwrite a file in the ftp server using my client..
is there a way to overcome this ??
do i have to make any changes in the ftp server ??

sorry but my network is standalone without any internet connection.

Have you configured Rainlendar to use the http or ftp server to access the events? The ftp server should be easier to set up since it doesn't require any additional components but unfortunately some ftp servers don't include all the functionality required by Rainlendar so they might not work properly.

Setting up a http server needs a bit more work. A standard http server does not allow updating of the files on the server so what you need to do is to install (or enable) the webdav extension to the server and configure it so that the folder where the Default.ics file is located has write permissions.

If you run Rainlendar in the debug mode the log will contain all the communication between the client and server which can help when googling for the errors.

well/..
thanks a lot..
looks like i sorted the problem by enabling webdav in http
thanks a lot...