Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Question:

Question: How do I restrict File Sharing to private networks only on High Sierra

Using Sierra Server, I was able to restrict File Sharing access to private networks only using the "Access" pane in MacOS Server. Since File Sharing was removed from Server 5.4 and is handled natively by Mac OS High Sierra, I'm having a hard time figuring out how to restrict file sharing to local network traffic only.


In High Sierra's File Sharing pane, it says "Other users can access shared folders on this computer at afp://my-reverse-dns-address or smb://my-reverse-dns-address" This kind of freaked me out because I thought that meant I was sharing to the world when I only wanted to share to local networks. Thankfully, that does not seem to be the case.


However, I don't see a way to toggle between private and all networks the way I could in the pervious version of Server. Anybody here know how that is handled now with High Sierra?

Posted on

Reply
Question marked as Solved
Answer:
Answer:

Generally this task is left to network firewalls.

If you want to use the most efficient management of privacy for network data a firewall is where to start.

I imagine you could create the access control.


Click on the server name in left side bar in Server.app there should be far tab called access.


I suspect it makes firewall rules but I haven't used it.


I user pfsense.org


Ben

Posted on

Page content loaded

Question marked as Solved

Nov 14, 2017 6:39 AM in response to Kabukiman In response to Kabukiman

Generally this task is left to network firewalls.

If you want to use the most efficient management of privacy for network data a firewall is where to start.

I imagine you could create the access control.


Click on the server name in left side bar in Server.app there should be far tab called access.


I suspect it makes firewall rules but I haven't used it.


I user pfsense.org


Ben

Nov 14, 2017 6:39 AM

Reply Helpful (1)

Nov 14, 2017 6:43 AM in response to detourdog In response to detourdog

Thanks for your response. You are correct, I was able to create a custom rule on the Access tab to restrict access on AFP and SMB ports.


In previous versions of MacOS Server, I'd just be able to add a service in the Access panel and not have to worry about ports. Seems like a step in the wrong direction as far as usability, but I suspect this is just another sign that MacOS Server isn't long for this world.


Thanks again for your help!

Nov 14, 2017 6:43 AM

Reply Helpful

Nov 14, 2017 6:53 AM in response to Kabukiman In response to Kabukiman

Glad it worked out.


Regarding the future of Server.app nothing seems to really change other then the organization of the features. My observation is that administrating a server is becoming simpler(fewer options in the gui) and becoming more the domain of actual administrators (the normal options are in the command line and available to those who know where to look).


Finally the heart of the Server products from Apple since Mac OS Server 1 was an integrated directory system. The directory system was set-up to allow single sign for all services running on the server. I think it started with NetInfo and switched to open directory probably when it switched to somewhere around Mac OS X 1.


I think Server.app will stick around for a while.

Nov 14, 2017 6:53 AM

Reply Helpful
User profile for user: Kabukiman

Question: How do I restrict File Sharing to private networks only on High Sierra