Strange... Such thing shouldn't happens. Would be normal if Dropbox folder sits on client side mounted network drive (such thing could happen even on server machine - in same time server and network client). So, changes in the disk FS don't always propagate correctly to all client mounts (including on server machine) resulting in an application which rely to detect such changes (like Dropbox) can't work properly. In this context, are you sure that you placed the Dropbox directory on real ("raw") disk space? You can make a simple test to see, if your machine is configured properly. Open a simple text editor on your server, write something inside (doesn't matter what) and save the file inside Dropbox directory (keep the editor open). File should be visible on the other workplaces. On some other machine (network client, workplace) open the same file and make some change inside (doesn't matter what) and save. Now, is the last change detected on server side - on both/some of the text editor (still open there) and Dropbox application? (Present day almost all text editors are able to detect concurrent change, but not all. Select a suitable!) If text editor, running on server, successfuly automaticaly detect file change (and signal about somehow without any user intervention) and Dropbox application can't, then you can report a bug in the particular build. If the text editor can't detect change, check more carefully your settings. Hope this gives some direction.
... View more