<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Teamwork permission problem in cross-platform setup in Collaboration with other software</title>
    <link>https://community.graphisoft.com/t5/Collaboration-with-other/Teamwork-permission-problem-in-cross-platform-setup/m-p/98639#M9632</link>
    <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Have a client with 3 systems running Archicad 10, and using Teamwork for projects (2 Mac, 1 XP). Projects are stored on a server running Mac OSX Server 10.3. There are no problems with the Macs choosing save/update, but when the XP system chooses this item there are certain files that end up locked on the server with "read only" access for the group. As a result they are having to change the permissions manually to be able to access the project from a Mac. Then if XP opens and updates again, they are back to locked/read only. &lt;BR /&gt;
&lt;BR /&gt;
I have tried to make sure the XP user on the server has the right default permissions setup and he seems to. If he creates a Word file and saves to the server everything is 'ok. The problem seems to be in the update from Archicad. Anybody have any ideas?&lt;BR /&gt;
&lt;BR /&gt;
Thanks,&lt;BR /&gt;
Paul Houck&lt;BR /&gt;
Mac Solutions, Inc&lt;/T&gt;&lt;/DIV&gt;</description>
    <pubDate>Wed, 05 Dec 2007 16:27:55 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2007-12-05T16:27:55Z</dc:date>
    <item>
      <title>Teamwork permission problem in cross-platform setup</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Teamwork-permission-problem-in-cross-platform-setup/m-p/98639#M9632</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Have a client with 3 systems running Archicad 10, and using Teamwork for projects (2 Mac, 1 XP). Projects are stored on a server running Mac OSX Server 10.3. There are no problems with the Macs choosing save/update, but when the XP system chooses this item there are certain files that end up locked on the server with "read only" access for the group. As a result they are having to change the permissions manually to be able to access the project from a Mac. Then if XP opens and updates again, they are back to locked/read only. &lt;BR /&gt;
&lt;BR /&gt;
I have tried to make sure the XP user on the server has the right default permissions setup and he seems to. If he creates a Word file and saves to the server everything is 'ok. The problem seems to be in the update from Archicad. Anybody have any ideas?&lt;BR /&gt;
&lt;BR /&gt;
Thanks,&lt;BR /&gt;
Paul Houck&lt;BR /&gt;
Mac Solutions, Inc&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 05 Dec 2007 16:27:55 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Teamwork-permission-problem-in-cross-platform-setup/m-p/98639#M9632</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2007-12-05T16:27:55Z</dc:date>
    </item>
    <item>
      <title>Re: Teamwork permission problem in cross-platform setup</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Teamwork-permission-problem-in-cross-platform-setup/m-p/98640#M9633</link>
      <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
I'm just curious if the machines use the same protocol and IP-address when connecting to the server? We had issues when WIN team members connected with Samba (smb://192.168.x.x) and MACs with Apple File Protocol (afp://192.168.x.x).&lt;BR /&gt;
&lt;BR /&gt;
--&lt;BR /&gt;
Regards, Juha</description>
      <pubDate>Thu, 06 Dec 2007 22:45:56 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Teamwork-permission-problem-in-cross-platform-setup/m-p/98640#M9633</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2007-12-06T22:45:56Z</dc:date>
    </item>
  </channel>
</rss>

