New answers tagged server.app
It does need opening if you are trying to access your Caching server outside of your network. If you are only attempting to access it within the network, this port doesn't need unblocking externally.
Essentially you have to make your server accessible behind a router with a frequently changing IP-adress with a fixed fqdn for the router and forward all http/https requests from the WAN to the OS X VM in the LAN. Set up dynamic DNS: Get an arbitrary name from a dynamic DNS service provider (like Dyn (not free) or NO-IP (free)) or depending on your ...
serveradmin command smb:command = getConnectedUsers serveradmin command afp:command = getConnectedUsers
Check the DNS to make sure the server's DNS entry is set correctly. Also check whether you are using NAT, i.e., whether you connect to the Internet via NAT (check whether your router is configured to use NAT). If you are, you will either need to configure port forwarding in the router, or find hosting for your website that is externally accessible from the ...
I add to the correct answer from grgarside that documentation from Apple can be found here http://help.apple.com/advancedserveradmin/mac/4.0/ I have to say the documentation is good but not excellent so here is a little "recipe" for the most common setup. A common practice is to create users, to create groups, to assign users to groups. (one user can ...
Generally, the shared folders for a group should go in /Groups/groupname/. /Users/Shared/ is more designed for local users to share, though there's nothing stopping you from using this too other than it is non-standard.
I use the GUI, it easier... When I migrate a server, I: Add the shares to the 'File Sharing' section of the server app. Configure the permissions as I would like them to be. Navigate to your server under the 'Server' section on the left of the server app, select 'Storage' from the tabs and then navigate to where your share is located and select it. ...
We originally filed a bug report regarding this problem with Apple (at the time we weren't deterministically certain it was a bug, but considering the efforts we made to resolve this with Apple Enterprise support, it seemed probabilistically to be a bug). Recently Apple engineering responded to us stating they have attempted to fix this bug in Server app ...
I believe the proper commands for this are: ACL sudo chmod -RN /Path/to/your/share POSIX (assuming the short name for your local admin account is 'admin' and you want everyone to have read-access, if not change 744 to 740) sudo chown -R admin:wheel /Path/to/your/share sudo chmod -R 744 /Path/to/your/share
Top 50 recent answers are included