Currently Being ModeratedJan 6, 2013 6:56 AM (in response to jfuller721)
As you say (indirectly) it is better not to have a server be also a client machine...
Anyway, when you say 'file sharing' are you talking on the level of server file sharing, or client machine file sharing?
There shouldn't be any issue with IP address compatibility (not quite sure what you mean by that actually) the question with file sharing is more one (scope) of authorisation. The OS X 'file server' uses the server open directory to authorise access (and that may be server local or network Open Directory scope) a 'client' machine only has its own (limited) local user account directory.
Again not full sure what the problem / issue / question is.
Currently Being ModeratedJan 6, 2013 7:21 AM (in response to FromOZ)
I am trying to use the server as a client and all the functions (calendar, contacts,etc.) work fine except for file sharing. When another client computer modifies a file it shows locked on my side. My side meaning server try to act as a client.
Currently Being ModeratedJan 6, 2013 7:30 AM (in response to jfuller721)
Yes that is working as designed. The file is sitting on your machine — when someone accesses & changes a file where you machine is acting as a server then they are changing it. The OS will then 'lock' the file, while the other user has it open, to protect the file. Multi-user does not mean simultaneous multiple users editing a file — usually. If some specific software has that functionality built in then it is managing that on top of the operating system. If you have a 'simple' app like, say, TextEdit, editing a file then it will grab it for itself 100%.
Also it likely will not 'release' the lock until the file is saved closed, and/or user closes application and/or user disconnects from the shared file folder.
Calendar & Contacts will/may have some rudimentary multi-user functionality built in, doesn't mean all apps will.