configure- sharing - Map Mac volumes to Windows On. I convinced the office to revise thier workflow rather than to keep looking for workarounds and trying to get Revit to submit to something it wasnt designed to do apparently.Īs to how Worksharing / Save to Central came to work in Parallels, not 100% which of the dozen or so things I tried was the fix. I am sorry I can’t give you more direction but we simply do not test in a Mac environment." Because we don’t test in a Mac environment we can’t give any specific advice on getting Revit to save files over a Mac network. Still then files are saved local and then the sync process is used to transmit changes back to the central file. File servers come into play once worksharing is enabled on a file. Revit files even in a Windows environment is really intended to to save to the local machine only. That is really about running Revit at the “local” level. I can tell you Revit is not supported in any way in a Mac environment beyond running Windows in bootcamp or parallels. "I do not have experience with Mac files servers. Did have a follow up with an Autodesk person after his response to a crash report. Have settled with only hosting Central files on the server. Īnyone have an answer that doesn't involve buying a PC server to hold the central file? (We could do that, but hope not to have to.) Thank you. This thread seemed promising, but I'm wondering if it's the only solution. (Anyone in Connecticut?)Īutodesk Revit support and Parallels support so far have not been able to help. I'm not even entirely sure who/what kind of tech person to call to fix the situation. The workshared central file will allow a local copy to be made, but the anyone who is not the original creator of the file cannot change it or save it. The last item is well beyond my skillset, but I tried to set static IPs for my two Virtual Machines, and did not get good results. Revit 2011, Windows 7, Parallels 6, and very fast IMacs machines.ġ - setting permissions on the files to be the most accessible possible. In my tiny office, we are trying to use worksharing on a file and we are not getting anywhere. However, SMB is proprietary to Microsoft and was designed specifically for Windows clients whereas AFP was designed by Apple for Mac clients.Seems that some people here have been using Revit through Parallels on Mac machines. OS X supports SMB largely because there are many environments in which only Microsoft and other SMB servers are available on a network. AFP is common for faster networks where large files need to be transferred – the norm in graphics/print/video environments where Macs are commonly used. Mac OS X clients can connect to network file servers using both the Apple Filing Protocol (AFP) and the Microsoft Server Message Block (SMB). SMB is a fabric protocol that is used by Software-defined Data Center (SDDC) computing technologies, such as Storage Spaces Direct, Storage Replica.ĪFP is a network file control protocol system specifically designed for Mac-based platforms. SMB can also communicate with any server program that is set up to receive an SMB client request. This allows applications to read, create, and update files on the remote server. Using the SMB protocol, an application (or the user of an application) can access files or other resources at a remote server. The SMB protocol can be used on top of its TCP/IP protocol or other network protocols. SMB is a Microsoft network file sharing protocol that allows applications on a computer to read and write files and to request services from server programs in a computer network. Let our team design a custom solution for your network and start sharing files easier than ever. Share Easier Increase file production and productivity.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |