uncleflo
Registered since September 28th, 2017
Has a total of 4246 bookmarks.
Showing top Tags within 2 bookmarks
howto information development guide reference administration design website software solution service product online business uk tool company linux code server system application web list video marine create data experience description tutorial explanation technology build blog article learn world project boat download windows security lookup free performance javascript technical network control beautiful support london tools course file research purchase library programming image youtube example php construction html opensource quality install community computer profile feature power browser music platform mobile work user process database share manage hardware professional buy industry internet dance advice installation developer 3d camera search access customer travel material test standard review documentation css money engineering engine develop webdesign device photography digital api speed source management program phone discussion question event client story simple water marketing yacht app content setup package fast idea interface account communication cheap compare script study market live easy google resource operation startup monitor training
Tag selected: reply.
Looking up reply tag. Showing 2 results. Clear
NFS - which ports to open? - Storage - Discussions
Saved by uncleflo on December 23rd, 2018.
No problem connecting to NFS with firewalls disabled,but even with TCPView it's not obvious which ports require opening.
We've opened port 2049 for both UDP and TCP and all seems well, but there's a selection of ports mentioned across the web for NFS. So with XenServer just 2049? Sharing filesystems by NFS: Regardless of which choice is made for ID mapping you will need to adjust any firewall the system is using so that NFS clients can communicate with the server. You will need to ensure that the following ports are open before sharing any filesystem: UDP: 111, 1039, 1047, 1048 and 2049. TCP: 111, 1039, 1047, 1048 and 2049. See _this article_ Tobias
firewall helpful reply answer server accept client fix topic check procedure administration port suggestion solution open connect nfs require tcp map system article discussion administrator
Setting a FQDN for the NAS - Synology Forum
Saved by uncleflo on December 23rd, 2018.
When setting up the NAS, you need to enter in a server name. This becomes the hostname. How can I set a FQDN (i.e. NAS-Store.example.com) without it being wiped out all the time? You can just setup a ddns name and use it to get access (I'm guessing you wanna use that name to gain outside access to your NAS). There is a DDNS tab in Control Panel > External Access. Register your name there. I don't need to worry about DDNS. That is not an issue. As I run an internal DNS on my network, I can type in the FQDN of the NAS and get to it OK. That's all fine. I would just like to be able to give the NAS an FQDN and an SSL certificate to match it, so I do not get any warnings that the cert is incorrect for the NAS when I have external clients use the Cloud Station. I don´t you buy a domain name, setup it up by using DynDns client and give the domain name to your clients to connect to, and then set your internal DNS with that same domain name to point to the internal IP, and also set the name of the NAS with that domain name.
setup cloud clarify configure resolve domain server reply question answer suggestion administrator administration nas synology file share topic dns name ip access external
No further bookmarks found.