![]() ![]() Could OpenVPN support 10 clients all connected to my network at once, for the sole purpose of accessing the SMB shares? Is this user friendly? Can clients set it up and forget about it, as the openVPN program will automatically reconnect them to my network, and SMB will work out? Or will openVPN take a bit to connect, and windows network drive throw a bunch of errors since the drive isn't reachable immediately whenever the client restarts their computer or temporarily disconnects from the network? This VPN session would have to be active, and running on my omv box. Supposedly I can setup a VPN so that others can VPN into my box. ![]() Reading more, I have heard of 3 alternative options for getting SMB to work over the internet: The main advantage of NFS is that its ports wont be blocked by my ISP, so this could be a reasonable alternative to SMB.Īs it stands, I cannot figure out how to set up NFS shares with a username/password that can easily be mounted by clients, any help would be appreciated. Any tips of setting up NFS would be appreciated. I keep reading something about UID/GUID for NFS, but see no options for this anywhere in the UI, nor how this could translate to a reasonable user/password for clients to use. On windows 10 pro with the NFS services installed, the mount command has a flag for username/password (-u:username -p:password).īut nothing seems to work. Which brings me to this post, has anyone been able to figure out how to map a network drive and specify the port in windows?!Īssuming this isn't possible, I tried to set up NFS but cannot for the life of me figure out how to set up proper username/password configurations for NFS shares, which worked on samba out of the box in OMV. This removes my ability to set up samba such that other windows clients on another net can connect. Windows has no feature to map a network drive over a different port, 445 is essentially "hard coded in". So, I configured Samba to use port 2111 and forwarded it on my router, and sure enough, samba works over the internet, but only for mac/linux! When a client on mac/linux tries to connect, they specify the port with a colon, such as \\65.55.55.55:2111\samba\share. I'm aware of Samba's security issues, but if a modern samba share is configured properly, my understanding is that it is reasonably secure. Unfortunately, my ISP blocks any incoming/(and supposedly outgoing) port 445 connections, and all incoming port 137-139 connections. I have samba all up and running on my local network, works like a charm. ![]() I want users to be able to map some shares as network drives on another network, to be in use 24/7. I've got OMV all set up and configured with various shares/file permissions/users. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |