VPN and File sharing

[cavi]

Hi Phill! thanks for your comment! =]

• The upload speed is 2 Mbps (the team is small and I assume that there will be no more than 2 team members who connect in the same time...).
• I own TP-link 9980 -- I don't know if it can handle VPN instead.
• Yes, I have static IP.
• the IP is connected to domain name that I purchased (what is sub-domain? =])/
• I'm planing to purchase the OWC thunderbay in order to store the files (I don't want to use third-party storage - medical files...).

what do you mean by "Ensure your Firewall will not respond to pings."? I enabled adaptive firewall and also turned on the OS firewall (I excluded the server app).

Again, thanks a lot for your comment!!

 

[Altemose]

• The upload speed is 2 Mbps (the team is small and I assume that there will be no more than 2 team members who connect in the same time...).

• I own TP-link 9980 -- I don't know if it can handle VPN instead.

That is a mighty slow upload speed for any client to connect. You may want to look at going with at least 5 Mbps. You can make do as is, but the speeds are going to be lackluster. That router cannot support VPN, so you need to use OS X Server to host VPN.

 

[kiwipeso1]

Easy... Make sure that the AFP and SMB ports are not open on the router. If you created a port forward allowing port 548 to be open, then the Mac can connect without VPN.

Which is the worst approach to security possible.

 

[LC Phil]

Hi Cavi,

As Altemose mentioned, 2Mbps is probably going to be too slow. In my opinion it could be almost unusable. So. Before you spend any money I think it's best you setup a test case. Port forward the L2TP ports to the Server's static LAN address, setup a basic file share AFP/SMB (doesn't matter which one) on the local HD, put a few documents/pictures or whatever you'll be accessing, and test the connection.

A subdomain is an easy way to remember different services. Say www or mail. So xxx.yourdomain.com.
You can point www.yourdomain.com to your webhosting provider, mail.yourdomain.com to your e-mail service, and vpn.yourdomain.com to your home server. Just means people don't have to remember a string of digits when setting up their VPN/other services.

Most firewalls don't respond to pings, so don't worry about it too much.

Okay, the OWC Thunderbay seems...intense. But on that topic, whilst I understand some countries and states have heavy regulations surrounding medical data storage I feel you should look into an online solution, if there's one available.

Good luck,

Phil

 

[Altemose]

Which is the worst approach to security possible.

Yes. I was stating to make sure that the ports for SMB and AFP ports were NOT open. I then stated that the reason why the clients could connect without VPN was because he had AFP open.

 

[cavi]

Hi Cavi,

As Altemose mentioned, 2Mbps is probably going to be too slow. In my opinion it could be almost unusable. So. Before you spend any money I think it's best you setup a test case. Port forward the L2TP ports to the Server's static LAN address, setup a basic file share AFP/SMB (doesn't matter which one) on the local HD, put a few documents/pictures or whatever you'll be accessing, and test the connection.

A subdomain is an easy way to remember different services. Say www or mail. So xxx.yourdomain.com.
You can point www.yourdomain.com to your webhosting provider, mail.yourdomain.com to your e-mail service, and vpn.yourdomain.com to your home server. Just means people don't have to remember a string of digits when setting up their VPN/other services.

Most firewalls don't respond to pings, so don't worry about it too much.

Okay, the OWC Thunderbay seems...intense. But on that topic, whilst I understand some countries and states have heavy regulations surrounding medical data storage I feel you should look into an online solution, if there's one available.

Good luck,

Phil

Hi Phill,
The main use of the system will be in the office (which the server also locate in). as I wrote, in the worst case 2 users will be connected at the same time (we use documents' not pictures or videos) so even if it too slow, it's ok for connecting to the office and get one or more documents in case of urgent need (I tested it now, it's working fine =]).
with regard to the regulations on medical files — I'm aware to the regulations (HIPPA etc'). to be more exact, I don't store medical files, but "medical related" files (which also need to be strictly secured...).

the 1M$ question is how I can allow users on the server network to access file sharing without problems, but if them on remote location they will be required to use VPN in order to see the files (maybe I need to choose in the permissions "private network")?

Thanks! =]

 

[Altemose]

the 1M$ question is how I can allow users on the server network to access file sharing without problems, but if them on remote location they will be required to use VPN in order to see the files (maybe I need to choose in the permissions "private network")?

You can leave the setting on all networks and you must use VPN. I can give you a hand over TeamViewer or Skype or something if you need help one day.

 

[cavi]

Thanks! When I'll setup the system with thunderbay I'll send you a message =]]