I have to say, after watching youtube 'how to do tech stuff' for over 10 years your series on how to set up a Synology NAS is the by a LONG margin the most concise, easily understood, well delivered, comprehensive and detailed tutorials I've EVER watched. I've seen the first 4 videos and look forward to the next 17! I'm learning an amazing amount of stuff in such a short period. Kudos to you, you really should be a teacher... :)
TOTALLLLLLLY agree Keith, this guy is buy FAR the best instructions I've ever seen. Everything I was thinking, you took the words right out of my mouth. I'm saving this for future reference.
Cannot thank you enough for your help. I thought buying a synology router & NAS would be a great idea for ease of use, but unfortunately Synology has lacked tutorials for customers who are not networking gurus. Searching through Synology forums, subreddits, and TH-cam forever it seems to be able to get clear concise answers to the questions I have. Wish I found this video weeks ago! Thanks again!
Oh WOW, have you done a great job here, so difficult to find such a comprehensive tutorial, written or video. You explain everything so clearly. Why don't Synology just put just put a link to you. Thank you very much.
Static ip and dhcp has never made sense to me. Port forwarding always made me tear my hair out. I finally understand this stuff thanks to this video! Thank you
@mydoodads I have to say sir, that you DEF hit it outta the park with your videos. Your verbal pitch speed is superb !!!!! It's just the right speed to catch what you're saying and allow it to sink in, know what I mean ? How you navigate through your onscreen graphics is like nothing I've ever seen man ! ! ! ! Many other presenters race through their demos like a race car driver. So the viewers end up having to watch it over and over to get anything out of it. But YOU ?!?!?!?! Like I said man, your instructional speed is perfect. . . you never speed up, and you always seem to pause at just the right time to allow the viewers time to digest and catch up if, anyone else was like me, following along doing the tweaks as he was speaking. Seriously though man, you REALLY are THAT good. Great video and can't wait to see the whole series on the Synology NAS. I just bought the Synology DS1019+ last week, so I'm just setting it up, moving files and media over, and I needed help setting up the ports and stuff on the router and NAS side. Wish I could stay up longer to do this but I gotta hit the rack. Until next time mate !! Mike
@@mydoodads ; My pleasure, I always give credit where it's due. I do have a question/ISSUE that has popped up since I've assigned static ips to my new Nas. I can't "MAP" a network drive to it now. I had one mapped to it before I assigned a static ip to the nas. I unknowingly tried to use the "OLD" link and obviously it didn't work. So I deleted that link. But when I tried to remap it, it would not work. 1. I opened up my windows 10 explorer window 2. Highlighted the "THIS PC" in the left column 3. went to top to select "MAP NETWORK DRIVE" 4. A window pops up to allow you to select where you want to map from 5. I select/highlight my DS1019+ . . . . . then the blue circle revolves around and around. . . keeps going 6. Then I get this error message; WINDOWS CANNOT ACCESS \\THEKINGDOM [may nas device name] . Check the spelling of the name. Otherwise there might be a problem with your network. To try to identify and resolve network problems, click Diagnose. 'ERROR CODE 0x80070035 the network path was not found 7. When I click on Diagnose, I get this message; PROBLEMS FOUND; Your computer appears to be correctly configured, but the device or resource (THEKINGDOM) is not responding" Do you have a video already out that identifies and fixes this issue ? Any ideas what it could be and how I can repair this ? Thanks man, I'll wait for your reply
@@proudcanadian9816 The obvious fix might be to reboot your computer and allow Windows 10 to try and remap your home network. If I remember correctly, Windows 10 will use NetBIOS over TCP/IP, and Windows Workgroups to find the host name of a device on a network. So because Windows will have cached the address of your NAS. A reboot might force the computer to update that cached data, which is pointing at an IP address that your NAS is no longer using. However, I would personally recommend that you move to using a more universal method (ie one that works in Windows, macOS, iPadOS and Linux) for connecting to devices on your home network. So try using your new IP address instead. For example setup your mapped drives using something like \\192.168.1.2\Public If you are interested, I did make a video on how to connect to network shares via Windows 10 - th-cam.com/video/dlUeUDqSLXI/w-d-xo.html In the coming months I plan to make a video on creating a script that will auto mapping network drives. So please look out for that video. If you want to be able to use a host name when connecting to a device. For example \\kingdom.synology.me then this video looks at how you setup DNS server - th-cam.com/video/iqgp2L1K6RQ/w-d-xo.html By using DNS server, you will be able to more easily connect to other devices that use static IP addresses. For example your Router, a Printer and your other NAS boxes. Hope this helps.
@@mydoodads Hey man, ok I'll give the restart a try first. I was at it for a while this morning, then I put it aside and moved on. I didn't want it to occupy my whole day. . . know what I mean ? lol I'll let you know how it turns out. And I do understand that this channel is a HOW TO, and not a forum. I was just at wits end and didn't know what else to do is all 🙄 Thanks for the reply and I appreciate your other suggestions. I'll try rebooting all the devices and let you know how I made out. I did reboot/restart throughout the video as you mentioned. But there may be something I just overlooked. Mike
@@mydoodads Hi doodads, Well you were right on the "reboot" option. I can't really explain it except to say that the problem was probably with the "reboot order" that I had done the first time around. . . if that makes any sense. In an effort to maybe help anyone else that ever encounters a similar problem as mine, I'll post what I did. As you know all too well, EVERYONE'S computer and networks are so infinitely different that it's impossible to have a "one size fits all" type of scenario. And I knew that when I encountered that problem. The only thing I needed was a bit of guidance, and you did just that.. Thanks for replying man. I believe this is what I did to make it happen: -- I shut down, and unplugged all 3 of my NAS devices from my switches[ DS1019+, the DS214play, and my old dinosaur but still runs well, the Dlink DSN123 ] -- I unplugged my cable modem, let it sit for a minute or 2 while the router did it's thing shutting down -- I went into my ASUS RT AC5300 router and did a reboot from the option screen, rather that pressing the power button on the back to shut it down. -- when the router had done it's thing, I started the modem back up again and waited for all the necessary lights to come up before I proceeded -- while that was happening, I started up the 3 NAS devices and plugged them back into the switches -- I did not reboot my pc because I wanted to watch the router reboot screen recycle [ don't ask me why. . . I just did ] -- once the router was up and running, I checked the device map to make sure the static IP's that doodads showed us in ep04 in his synology series were still showing. BINGO they still kept their respective IP statics -- I then checked that the ips ALSO were present in each NAS -- the FINAL test was going back into my PC win explorer and try to map the drives. . . . . . annnnnnnnnnd B O O M Bob's your uncle IT WORKED !!!!! :D Once again, big props to @mydoodads for his excellent instructions and tutelage for how to set up static ips. For whatever reason, my solution was in the reboot sequence. And there you have it !
I wish I'd found this series before setting up my DS218 as it would have made it quicker & easier. Luckily I found this when I had to make changes to the storage pool & volumes. I had to change it up as I rushed through initial setup and accepted all the default options, forgetting that the default for multiple drives would have been a RAID setup for backups when I wanted to have the full amount of storage available. Your series should be linked by Synology replacing their included setup guide as Jill and Glenn mentioned below, and pay you for hits accordingly. You've made it easier for people to get the most out of their Synology NAS in simple, easy to follow descriptions and examples, which in turn allows people to see what great little units they are. Thanks for your work :).
Just wanted to say a big thank you for these series of videos you have put together. They are a fantastic teaching aid and have expanded my NAS knowledge immeasurably! THANK YOU!
The Best video on this topic. Please make a video for using Synology NAS as 1. Storage server for home or small office. 2. Map NAS as network drive in all Windows computers in network. 3. Set scheduled, automatic, incremental, and encrypted back up *FROM* NAS *TO* Google Drive. To protect my data from *Ramsomware, fire at my home etc* (while making sure that Google can't read my data). 4. Restore Data. Thanks in advance.
Thank you for such a great series. It helped me so much when setting up my new DS918 NAS about a month ago. Then again yesterday, I had to upgrade my Virgin Media modem to one of their Hub3's and once again these videos helped to get my NAS settings sorted again to work with the new modem.
Thank you so much, your video helped me out a lot! I had been searching the interwebs for an hour and almost gave up, but you gave me the answer! I cannot thank you enough for this video!
Thanks for all your help. Very concise in your comments and you make everything very easy to understand (especially for someone with very little network experience). Will recommend anyone with a new Synology to Subscribe
Thank you so much. This video made it really easy for someone that doesn't know that much about networking to figure out how to get my Synology NAS working with my new ASUS router.
As so many others have already said......EXCELLENT video! Your instructions are easy to follow and you explain everything you do as you are doing it. Thanks so much for taking the time to do these videos! A++++++++++
I have a client asking me about cloud storage and file sharing solutions. Your videos have been really helpful in gathering information to present them in regards to using a NAS. Excellent work and very thorough explanations. Thanks!
I noticed you used a Synology router. Will you be doing a tutorial series on these routers, namely how to use the Synology Router Manager (SRM) operating system? Your videos are so clear and concise. Presumably, any videos on the SRM will be the same.
Great series so far. I'm running 5 synology nas boxes at my job. Really good boxes and the packages allow one to use the nas to the max. One note tho', you have been masking your MAC address throughout the series, but when you displayed your ipv6 address the link local address (prefix fe80) includes your Mac address as the last part of your ipv6 address. You may want to mask that too! ;)
decommissioned. Then from all the great feed back I have received (both positive and negative) I think I have a better idea as to what worked, what needs improving and a couple of ideas about topics I want to try in the future. So I'm really looking forward to starting a new series for DSM7 some time this year. Which I hope will be better and more comprehensive than what I have done so far. Thanks for the advice
@@mydoodads DSM7 is going to really interesting. I found your series while searching for some video that a friend of mine could use to learn from as he is waiting for a ds218 to arrive. He was looking for something to keep from spending $$$ on Dropbox. If you share files over 2gb Dropbox requires both sides to have a paid Dropbox acct, plus as his file distribution goes it will save him from having to purchase more Dropbox space. So, be sure to include how to share files over the internet with your new series - its really neat. Later!
I live in a country outside the US that has many levels of monitoring and access restrictions. I have my Synology NAS setup in the US. There is nothing even remotely "secret" in a strategic sense about the data I store (music, family video and some personal correspondence). I have tried the DDNS solution but find that I still cannot directly access the NAS. This makes backing up my and my kids Mac across the internet to the NAS directly impossible. My question is this: If instead of doing Time Machine backups for my Macs, I simply periodically copy over the backups using FileStation, can I later backup from those backups by copying them back onto a local hard disk where I live? I appreciate that you may not be able to answer this question, but would appreciate any ideas you might have. I have 5 macs that I need to have backed up using this less than perfect process. My original idea was to use TimeStation to backup to the NAS but I cannot get the finder to recognize the DNS of the NAS through the VPN layers for some reason.
Your videos have been absolutely fantastic and so very helpful so far. Is the setup of a static IP address process the same when using a BT smart hub 6 router?
Yes. The same basic process will apply to any home wifi router. However, to avoid confusion. This video only deals with assigning a static IP address to your NAS from within your home Local Area Network (LAN). If you are looking to be able to remotely connect to your NAS from the internet (Wide Area Network). You also need to have a static public IP address. As BT do not offer public static IP addresses to their domestic broadband customers. You will also need to setup DDNS. This is a topic we cover when we look at setting up Direct Access on a Synology NAS - th-cam.com/video/STlKmQE5luM/w-d-xo.html Sorry for the long answer, but I thought it might be useful to clarify this point, to anyone else reading this comment.
Great video, thank you very much for your effort, the only question I have is what is the need of configuring DHCP pool 04:30, every IP within the subnet can be configured as a static IP and it will excluded from the DHCP pool, I really can not find any reason to configure the DHCP in the router. Thanks again.
HI Adam I like to structure my DHCP as it gives me a number of benefits. By structuring my DHCP I know that a specific range of IP addresses have been ear marked as static. So I know that any devices which use an IP address within that specific range, I have deemed as being of functional importance to my network. By structuring my DHCP, these important devices are then all listed sequentially. ie router - 192.168.1.1, NAS - 192.168.1.2, Printer - 192.168.1.3 etc. This in turn gives me a simple to remember mental map of my home network. For me personally when configuring a network, if the static IP addresses used by devices on my network run in sequential order. Tasks like wireless network bridging, printer setup, switch configuration, VLAN, DNS, port forwarding, and configuring a DNS server are a lot easier to remember, which for me tend to minimise my mistakes and help with troubleshooting. However, perhaps the most important reason why I have structured my DHCP is because I constantly fiddle with or add things to my home network. So I need to ensure that what ever project that I am working on, does not adversley effect the rest of my network. While I do document which devices have been issued with static IP addresses. If there is an instance were I want to do a quick and dirty config on say, a QNAP NAS. I know from my mental map that I can assign the QNAP NAS with the IP address of 192.168.1.19 and it will not create a IP conflict on another device in my network. I hope this response gives you a clue to my thinking, and thanks for the question.
great and easily too understand tutorial but how do you think about using an dns service like google 8.8.8.8 or 8.8.4.4 when assigning a static ip adress?
That is a good question. Ultimately, I'm not sure that its all that important which DNS service you use, as there is nothing stopping you from using any service that you would like. In fact if you were to look at all the devices I have on my network, the DNS servers that they use vary from my ISP's, to Googles, and Cloudflare's. While this is not an issue for my network. I think that it demonstrates a certain level of inconsistency on my part as to how I have been setting up devices. So I would suggest trying out a couple of different DNS servers on say your main PC, see how they perform and unlike me, stick with that DNS service when configuring devices. However, if privacy is a concern maybe don't use Googles DNS service and try something like Cloudflare's DNS instead (1.1.1.1). Right... now I'm off to spend the morning changing the DNS addressing to my network ;)
I am trying to perform this did you have to buy a static ip for your router? and if so do you have hardware firewall as well mainly just trying ot understand will I be able to do this with a dynamic ip? Thank You in advance great video
I have long suspected I may not have explained myself very well on this video. Sorry. Basically, you can assign static IP addresses to local (LAN) devices or to your public (WAN) internet connection. In the video I am assigning a static IP address to my NAS, so that its easier to find on my local network (LAN). You would also perform the same action when configuring a network printer. However, if you were looking to have your NAS accessible over the internet, then you would need a static IP address which you would purchase from your Internet Service Provider. Unfortunately, as most domestic ISP's do not offer the option for using a static ip address, unless you pay business rates. We can get around this issue by use something called DDNS which its free (depends on which DDNS service you use). Dynamic Domain Name System, is basically a service that monitors your internet connection, to make it appear as if you have a static public IP address. As to your query about the firewall. Your routers built in firewall should offer enough protection. By default a router's firewall will be enabled and it should already be blocking all incoming traffic. To check your routers firewall try using shields up its free - www.grc.com/ When you get to the stage were you want to make your NAS accessible via the internet. You would use port forwarding rules setup on your router to forward specific types of network traffic to your NAS. Hopefully as you work through the videos, this should all start to make more sense, but specifically look out for the video on Direct Access. Hope this helps
@@mydoodads this helped me understand quite a bit better for certain. I am using this in a business which wouldn't have mattered so much had I not started looking at static ip's right away. So now every time that term is mentioned I question weather it's a purchased one or an internally assigned one. Your video was a tremendous help it was as well as your explanation here and greatly appreciated. I do plan to watch the entire series as Time permits. Thanks again
Man I wish I had found your your tutorials a week ago, instead of being gung ho & trying to wing it. I have a Asus RT-AC88U has so much information it's easy to get lost in the translation. I have never configured it to be as a static IP set up. And for the life of me struggles to know how to do it. Is it essential for my NAS to have a static IP address Thank you for your time and patience that you have invested into making sure us mere mortals can understand how to configure our Synology NAS devices Any help greatly appreciated
It’s not essential, but if you intend to use your NAS for anything other than just file sharing. You might be better served assigning your NAS with a static IP. Ultimately, it will just make life a little easier later on, particularly if you intend to run your NAS as a media server. Flicking through the ASUS RT-AC88U manual - dlcdnets.asus.com/pub/ASUS/wireless/RT-AC88U/E10302_RT_AC88U_Manual.pdf Have a look at page 66 - 68 which covers configuring DHCP Server. You should find the DHCP settings under Advanced Settings - LAN - DHCP Server. The way DHCP is setup is very similar to the settings seen in the video. Just adjust the IP Pool Starting Address field and select Apply. Hope this answers you query.
I prefer to use DHCP reservation from the router. This way, I have centralized management of IP addresses assigned to all of the hosts in the LAN. Assigning static IPs to hosts device by device basis requires me to remember what device has what IP. However, there are cases what warrants static IPs. This includes when VLANs are used and other attributes that the DHCP server might not support. Not all DHCP servers are the same. Some offer more advanced features than others. Most router-based DHCP servers are fairly basic, necessitates the need for assigning static IPs to the hosts. By the way, you can use a Raspberry Pi as an DHCP server with advanced features. It's a pretty interesting project if you have the time.
I followed your instructions and completed the setup. I am now thinking about changing the wifi router. Can I just swap it for a new one or do I have to redo everything?
As long as you change the IP address and DHCP settings on your new WiFi router, so that the settings match the IP address and DHCP of your old router. It should be OK to just swap out routers. However, if you have configured your NAS for External Access you will also need to set your port forwarding rules. It’s worth noting that if you have configured your NAS to use UPnP to create Port Forwarding rules. In order for that feature to work, your new WiFi router has to be compatible with your Synology NAS. If your new WiFi router is not compatible, then you will also need to manually configure Port Forwarding on your new router. Hope that helps answer your query.
If my ISP does not allow static IP addressing on my plan how can I set this up? Do I just use "find.synology.com" everytime to redirct to the current IP address the NAS drive has been assigned?
You can add and pin a comment, that this is resolving any issues when your internet is beeing chocked/freeze for a moment every few minutes or a few times per hour. Very important step! :) Thank you :)
Connecting a NAS to my cable provider does NOT seem plug-n-play. So, as a typical cable customer (Spectrum, Brighthouse, Verizon), I cannot just buy a Synology or Qnap NAS, plug it into my cable provider's equipment and access my NAS on either my home network or through the Internet WITHOUT buying, for example, a Synology Router (which will grant me access to advanced setup features that my cable company may not)? Has any Spectrum or Brighthouse or Verizon customer successfully added a NAS--Synology or Qnap--to their network?
Hi Charbel If like me, you are using both a Synology router and a Synology NAS as your home network. Just to confirm, only the Synology router manager (SRM) will have a Network Centre icon. Your Synology NAS (DSM - Disk Station manager) should be displaying Package Centre, Control Panel and DSM help on its desktop. If when you log into your Synology router, you don't see a Network Centre icon, more than likely you have logged into the SRM with a user account and not your administrators account. You can tell that you have logged into a user account, if you select the Main Menu icon from the desktop on the SRM, and it only displays SRM help and FileStation. I hope that helps.
@@mydoodads thank you for your kind reply. just another question, i am always changing my disks as i am getting bad sectors. each 6 mnth, any suggestions please. thank you in advance.
Hi Charbel For my NAS devices, I prefer to use hard drives designed specifically for a NAS device. I tend to fit 8Tb drives as they more often than not will spin at faster speeds. However, for most home users I doubt that they will notice the difference between 5900 RPM and 7200 RPM. Especially if they are accessing network shares via WiFi. So a 2, 3, 4 or 6Tb WD Red drive would be fine. Currently, I mostly use the WD Red NAS Hard drives. This is because so far, I just have not had any problems or issues with them. - amzn.to/2HCYeTp A good alternative might be the Seagate IronWolf NAS drives - amzn.to/2F0fA7r I just fitted one to a new NAS that I am currently playing with. So far the Seagate drive has been as reliable and performed as well as the WD Red drives. Checking the warranty for both the IronWolf and WD Red drives. Seagate offer a 2 year warranty on an IronWolf drive, while WD offer a 5 year limited warranty on the Red drives. The Seagate might have the better warranty.
Interesting, on the router just set the static IPaddress & on the NAS just change the LAN IPaddressing from DHCP to manual & that static IPaddress. Thks again
Network Center is not part of Disk Station Manager (DSM). Instead its part of Synology Router Manager (RSM). Sorry, if it's a little confusing, at the time I thought it was a good idea to use a router that has a similar user interface to that of a Synology NAS. However, if you own either a Synology RT1900ac or RT2600ac wireless router then you should be able to find Network Center either on the Desktop of the SRM or from the main menu of the SRM. Please note that Synology updated the Network Center icon sometime last year. The newer icon is blue and Hexagonal. Hope that helps
@mydoodads Thank you for these great, informative video tutorials. On the static IP address, having a slight issue - I have set it up exactly as you indicate in the video however the only issue I experienced was that after assigning the static IP address to the NAS and re-setting all devices, the search function on find.synology.com/ could not then find the NAS device (on macOS which is what I am using). I am able to navigate directly to the login page by using the newly assigned static IP address, but not not sure whether operating in this manner brings up any issues down the line and why the device can't be located via the online webpage tool. Perhaps a mis-step on my side (I re-did the process outlined in your video 3-4 times however just to be sure with the same result), but wanted to check if there is anything I may be missing here that you could kindly point out? Any recommendation on solving this issue would be greatly appreciated! Thanks in advance.
The NAS used in my TH-cam videos is not my production NAS, but a secondary NAS that is only used purely for filming. I actually have a production Synology NAS which sits on a separate network which I have already fully configured. To confirm, my production NAS exhibits the exact same behaviour as your NAS. So if I try and use find.synology.com on my production network I receive the message "DiskStation not found on LAN". However, my production NAS is in a totally different state of configuration to the NAS as seen in episode 4 of my videos. When we assign a static IP address to any Synology device (I also use Synology Routers) find.synology.com should still be able to find those Synology devices within the LAN. The reason my production NAS can not be found by find.synology.com is because I have enabled the NAS's Firewall. Which is preventing my production NAS from being discoverable via find.synology.com If I turn off the NAS firewall, my production NAS is once again discoverable via find.synology.com. So to put your mind at ease, making your NAS non-discoverable via find.synology.com should not impact the running of your NAS, and if you happen to be a little paranoid about network security possible a good idea. However, having said all this, you may still want to find out why your NAS is not discoverable purely for your own piece of mind. So if the issue is not resolved after you check your Firewall. It might be worth checking the following: 1. Just confirm in network settings the Subnet mask settings are exactly the same as the ones being use by the rest of your home network. Check that the NAS Subnet mask settings against those being used by your Mac 2. Check that find.synology.com has not some how automagically disabled itself. Take a looking in Control Panel - Info Center - Device Analytics - Share Network Location 3. As find.synology.com is a web browser utility. It might be worth clearing your browser cache to see if that make a difference. Sorry, I can’t think of any other places to check but please do let us know if any of this helps.
mydoodads I have the same issue using a Surface Pro with Windows 10. After configuring the manual IP, it appears the find.synology.com setting is subsequently disabled (unless it was already disabled in here). I’ve re-enabled it, checked the subnet masks match and also cleared the browser cache. I also didn’t have any firewall activated on the NAS at the time but the issue persists. Is there any further updates on how to resolve this? Thanks - great videos by the way. Update: Strangely, while the find Synology web assistant no longer works on the device I configured the static IP from, it does appear to work whenI search from another device on my network. Strange??
By having a quick look at the html code for Synology Web Assistant. It would appear that the code works with a number of web technologies, primarily javascript and . So to double check that Windows 10 does not have some sort of fundamental issue with Web Assistant. I just pulled out a Surface 3 with Windows 10 10.0.18362 Build 18362 and can confirm that Web Assistant works within Microsoft Edge on my network. As you did note that other devices can load Web Assistant. I would suspect an issue in your Surface Pro rather than a setting on your network or Synology NAS. A way to test this might be, to create a second dummy user account on your Surface Pro, and then see if from within that profile you can access Web Assistant. If you can, then you will know that the issue relates to something in your main user profile, rather than the whole computer. If you can’t then the issue might be something in the instance of Windows or the web browser you are using. By installing a second browser such as FireFox, and then re-testing if Web Assistant works within that second browser. You might be able to further narrow down where the issue is. Sorry I can’t offer some sort of magic fix to your problem, but I hope that at least this response will point you in the right direction.
Excellent work! I just bought my first NAS, a Synology 918+ with 2 Seagate 10TB Ironwolf drives, and I'm setting it up using your instructional videos, and so far they have been very helpful. My question is, when I set up the static IP like you show in this video, the first available number is 192.168.1.3, and it said the 2 is already in use. Any idea why it said that, or is it anything to worry about? Thanks again for all the information. ps, my status light is constantly flashing. Is that normal?
Its nothing to be worried about. Your router's DHCP will be set to lease an IP address for a specific amount of time for example 24 hours. When a device requests an IP address from DHCP, DHCP also informs that device about how long it can use that specific IP address for. Its sounds like a device on your network was assigned 192.168.1.2, but has not yet relinquished that IP address. When the lease time for 192.18.1.2 has expired, the device using that address will automatically ask DHCP for a new address. However, your probably don't want to wait to assign your NAS with 192.168.1.2 So you will need to find the device using that IP address and reboot it. That should clear and free the address 192.168.1.2 In the first instance try using a ping command. You want to ping 192.168.1.2 on your network. If you receive a reply to your Pings, that will confirm that a device on your network is using 192.168.1.2. How to Ping: On MS Windows: open search, type CMD and press enter. At the command prompt, type PING 192.168.1.2 and press enter. To cancel the Ping press Ctrl + C On macOS: open Spotlight, type network utility and press enter. In network utility select ping. Enter 192.168.1.2 and press the Ping button. Once you have confirmed that a device is using 192.168.1.2, you need to hunt it down. You can do this in one of three ways. Your router might list the ip addresses that it has assigned to devices on your network. If you check that list it might tell you which device is using 192.168.1.2 Alternatively, you could manually check all the devices in your home network to see which device is using 192.168.1.2. Finally, you could download a piece of network scanning software that will help you identify which device is using 192.168.1.2 To answer your last query, I have two Synology NAS units, the one I use in the videos, and one which I use as my production NAS. Neither of their status lights constantly flash, so I would say thats not normal. A green flashing light might be an indicator that no hard drives are installed. If you are in the process of initialising your Hard drives and they are creating Volumes(it will take hours depending on the size of the drives you fitted), that might explain why your status light is flashing. However, this Synology article might help you identify why the status light is flashing. www.synology.com/en-uk/knowledgebase/DSM/tutorial/General/What_can_I_do_if_the_STATUS_LED_keeps_flashing_in_orange Hope this all makes sense and thank you for your support.
I've said it before, and will say it again: I LOVE your video series! (And thank you for it). My question is what if I cannot find/determine assigning a static IP address to my NAS? My network provider issues the hardware routers (which does both 5ghz and 2,4 ghz) and even when I open the admin settings of my router, I cannot find where to tamper with the DHCP server settings, and it doesn’t show me a start and end IP address range. Is there another way to find/determine the static IP address? Please let me know.
Hi Erich If you can’t make any adjustments to the DHCP settings on your router, there are a couple of alternative methods that might be worth considering. For example if your router has a DHCP Reservation option. With this option you could use the setting to assign a static IP address to your NAS. However you will have no control over which IP address is assigned to the NAS. So for example, rather than 192.168.1.2 you might have to use 192.168.1.236. If you can turn off the DHCP server on your router, a second alternative might be to use the DHCP server built into your NAS. If you look in the DSM under Control Panel - System - DHCP Server - Network Interface. You will find an option to enable DHCP server to a LAN port on the back of your NAS. While this is how I have my NAS configured to my personal network. You do need to be careful to assign a static IP address to your NAS, have the computer you are working from connected via a network cable (to your router) and also assign a static IP address to your computer. This is all so your NAS and computer can communicate with each other, while you disable DHCP on your router and setup DHCP on your NAS. Finally, if you can place your router into modem mode, and then buy a new Wireless Router for example a Synology RT2600ac or Google WiFi. By using your older router just as a modem to connect to the internet. You will have full control over your new Wireless router including DHCP. This will also give you all of the advantages of a modern Wireless router along with better control over your home network. Hope this helps
You would do this by installing DNS server on your NAS - th-cam.com/video/iqgp2L1K6RQ/w-d-xo.html However, because of a trend with modern browsers, in that they will only open web pages that have a valid SSL certificate. You will also need to install a valid SSL certificate on your NAS. Sorry I don't have a video on how you just install an SSL certificate because one was automatically when we configured Direct Access.
These are excellent videos! Thank you. I, too, am a NON TECH person and I'm setting up my first NAS (ds918+). I'm primarily planning to use it as a media server with Plex. I would love to be able to use Plex away from home by remotely accessing my NAS. This video I think sets up an important first step by assigning the NAS a static IP address. When I get home later today I plan to follow your tutorial to set my static IP address on my Synology NAS (I have a Linksys EA9500 router so it might look slightly different, but fingers crossed). But I am having trouble finding any tutorial on how to set up the remote access through Plex so that I would be able to access my videos and photos on my NAS through Plex while I'm away from home. Do you have a tutorial on this, or instructions on this, or could you please make a video tutorial on this? I'm sure these videos require a lot of work but they are wonderful and I would really appreciate any help. Even if it is just pointing me in the right direction. I feel like the other instructions I've found for enabling remotes access to the Plex are written for folks who are more tech savvy than I am. Thanks in advance.
Hi Jeffery, Thank you for your kind comments. You are correct, these videos do take a great deal time to plan and produce. So I am always glad to hear from anyone that finds them useful. At the moment, Im about a third of the way through the basic setup process for a Synology NAS. My hope is to start looking at remote access in the spring of 2019. So, to answer your question. No, I don't have any tutorials or instructions on remote access or Plex yet. However, the following might help you in the meantime. Synology's support notes for Quick Connect offers a simple method for gaining remote access to your NAS. www.synology.com/en-uk/knowledgebase/DSM/help/DSM/Tutorial/cloud_set_up_quickconnect Then once you have remote access this video might help you to setup Plex. th-cam.com/video/t4VvwjJQ2as/w-d-xo.html
HI, How do i setup a static address for the External Address. I use the DS File App on my mobile but the IP address within the External Address keeps changing and doesnt allow me to connect after a day or so. Is there a way I can manually set the External IP, please send me the instructions if possible
There is no way for you to set your own External IP address. That has to be done by your Internet Service Provider (ISP). However, as most ISP’s (certainly in the UK) will not offer a service to give your domestic broadband connection a static IP address. They will instead offer to upgrade you to business connection, which usually is very expensive. Luckily, In the UK there are a couple of small ISP that will offer static IP addresses to domestic customers for a small fee. Both, Plusnet and John Lewis Broadband do offer static IP addresses which are activated once you make a single £5.00 one off payment. While I have not used John Lewis Broadband, I do use Plusnet and have found my broadband connection to be very solid and reliable. If you are not based in the UK or you don’t want to change supplier. An alternative option to having a Static IP address, is to setup DDNS or Dynamic Domain Name System on your Synology NAS. While this service will not assign you with a static IP address. It will monitor the changes to your broadband address to make sure that a domain name can always connect back to your NAS. I cover setting up DDNS in my video How to setup a Synology NAS Part 34: Configuring a NAS for External Access - th-cam.com/video/STlKmQE5luM/w-d-xo.html Hope this helps.
I set the static address at home/in network running a wireless hotspot to hopefully simulate being away from the same network instead of actually leaving every time I made a change. Then when I actually left and tried to access the drive using the same hotspot I can’t connect to it. What am I missing? Also I run a Mac. When I’m home I can mount the shares as if I have physical hard drives attached to the USB ports. How can I mount the shares as drives outside of the network? This crap is driving me up the wall
If I have understood your question correctly, it would appear that you are trying to test that you can access your NAS remotely. Unfortunatly, setting a 'local' static IP address is only the first step in getting "Direct Access" on a Synology NAS working. While the local static IP address you have assigned is important. It will only allow the devices on your home network to know that your NAS can always be found on the local IP address you gave it. Basically, you have to do the same thing but with your public IP address (the one your router is using to connect your home network to the internet) However, I would recommend that you do the following first: 1. Make your NAS secure 2. Enable Firewalls 3. Get a public static IP address from your Internet Service Provider, or plan to use DDNS 4. Setup your router so that it port forwards specific internet traffic to your NAS 5. Configure Direct Access So I would suggest taking a look at the rest of my series on setting up a synology NAS, if you have not already done so. While you could just jump to the part about External Access, I did try and produce a series that works in a systematic fashion. The link will take you to the series playlist - th-cam.com/video/Yua6dGpg4qo/w-d-xo.html As to being able to access your network shares when working remotely from a Mac. The best option is to setup a VPN server. Once again there is a full video on the topic along with a separate video on configuring the VPN clients for macOS, iOS, Windows and ChromeOS. Hope this helps to clear up any confusion.
it fails to me when checking at the very end through findsynology web address. i restarted and followed step by step and this stopped working, i can access with the fix ip though. will it generate any issue ?
As the find.synology.com webpage is really just a convenience to help you find out which dynamic IP address you are using. Not having it working will not generate any issues. For me, when I installed DNS server onto my NAS, was the point when the code that runs in the find.synology.com webpage broke for me. As I have always felt that the find.synology.com webpage was a bit of a security risk. You will see that in the newer videos to this series I no longer reference find.synology but instead just use the fixed IP address. Eventually I will be making a quick tip video to show people how to turn the feature off but if you find that it no longer works, I would argue that that was a good thing.
If you have a Synology NAS with 2 ethernet ports, you can create something called a Bond. The aim of a Bond is to create additional bandwidth by merging two network ports into one. So for example, if you have x2 1Gigabit network ports, you can Bond them and create 2Gb of bandwidth for your NAS. When you create a Bond, it will use a single static IP address. However, while, I do use a NAS that has two network ports, currently I do not Bond those ports. Instead, I have left the second port unused, then if I make a mistake with the configuration of my NAS. For example if I were to accidentally set my firewall to lock myself out of the DSM, by simply plugging my computer into the second network port. I can regain control of my NAS. Hope this help clear up you query.
Hi James, I can't think of a reason why your NAS should be giving you that behaviour. So I would suspect the DHCP on your BT Smart Hub is not correctly issuing IP addresses. A quick google did highlight a few people experiencing issues with BT HomeHub 6's DHCP. community.bt.com/t5/Home-setup-Wi-Fi-network/BT-HomeHub-6-DHCP-IP-address-allocation-not-working/td-p/1930852 Sorry I cant be of more help
Hi, I have a Synology NAS DS213j and a Router ZTE H368N. This router has two DNS servers 1 and 2 with the IP adresses 192.121.1.34 and 192.121.1.66. The DHCP IP adress is 192.168.2.1 to 192.168.2.252 what is different from the IP adress of the DNS servers. How do I know what static IP address I can use? Can I sent you a prtscrn of this configuration? thanks
Hi, While Im not familiar with a ZTE H368N router, I did find a couple of screenshots online, so I think I understand its layout and default settings. However, please double check that what Im trying to explain does match your routers settings. First, we can (sort of) ignore the two DNS server addresses as there is no need to touch them. The reason your router has two, but the NAS only allows entry for one. Is that the router needs to have redundancy so if one DNS server address fails to resolve a domain name request, the router can fall back on a second or third DNS server. When assigning your NAS with a static IP address, you are isolating a few IP addresses in your DHCP address pool. This is so that those IP addresses cant be automatically assigned (via DHCP) to a device on your network. Looking at the manual for the ZTE H368N router, it appears that your router has by default already isolated three IP addresses within its address pool: 192.168.2.253, 192.168.2.254, and 192.168.2.255. If you check the Network settings on your ZTE H368N router, you will see in the LAN IP address field, one of those IP addresses. I think your router IP address will default to using 192.168.2.254. If this is the IP address that has been assigned to your router, we should never try and assign this IP address to another device on your network. At the moment DHCP can assign any device connected to your network with any number in its address pool between 192.168.2.1 and 192.168.2.252. You should be able to see a table called Allocated Addresses. In that table are the ip addresses that DHCP has currently assigned to devices on your home network. Note down the following information about your router: The routers LAN IP address The routers Subnet Mask The routers default gateway [which should be the same as the routers LAN IP address] The routers first DNS server address So armed with the above information we can do one of two things. As the router has already isolated three IP addresses, we could assign one of the unused static IP addresses to your NAS, i.e. 192.168.2.253 or 192.168.2.255. However, as you are new to assigning static IP addresses, lets play safe and use the second method. *** Instructions *** Lets remove a series of number from the beginning of your DHCP address pool. This is similar to what I was demonstrating in the video. 1. Working on your router, locate the option Network - DHCP start IP address 2. Change the DHCP start IP address from 192.168.2.1 to 192.168.2.10 3. Select Submit This will give you 10 static IP addresses to use with specific devices for example your NAS, a Printer, network Switches etc. 4. Now reboot all devices connected to your home network (accept your router). This will force DHCP to assign new IP addresses, and stop any devices from using the 10 IP addresses you just turned into static IP addresses. 5. When your computer reboots, log back into your NAS and Select Control Panel - Network - Network Interface 6. Just like In the video select your LAN and click on Edit 7. Under the IPv4 tab, change the following settings Address: 192.168.2.1 Subnet Mask: 255.255.255.0 Gateway: [is the IP address of your router so I would guess ] DNS server: 192.121.1.34 6. Select OK to save the changes... DNS tip. In the DNS server setting field you don't need to use the DNS server address that you were given by your Internet Service Provider. On my server I actually use a DNS of 8.8.8.8 (while my ISP DNS is 212.159.6.9) which is a DNS server provided by Google. As 8.8.8.8 is easy to remember, its very handy for troubleshooting network problems. Really sorry for the long winded answer, but I hope it helps.
Because of the way DHCP works, all of the devices on your network have the potential to change IP addresses. For example if you were to reboot your router there is no guarantee that all of your devices would receive the same IP address they were previously using. This is why devices like servers, printers or NAS devices need to use static IP addresses. Using a static IP address will help to ensure that you always know what IP address your NAS is using. This in turn helps to keep any network shares reliable as they will always be accessible from the same IP address. So, if you were to follow the procedure shown in the video. As you would exclude 19 IP addresses from your Routers DHCP address pool. If a device was using one of the 18 IP addresses you removed. That device would receive a new IP address from the DHCP address pool. So to answer your question... sort of.
@@Thefisk101Gaming Check if your router has a DHCP reservation option. DHCP reservation will allow you to lock the IP address that DHCP has assigned to a device. So it will achieve the same goal. The only reason I personally don't use DHCP reservation, is that if you replace your Router. You will no longer know the IP address your NAS has been assigned by the new routers DHCP. So getting your network back up and running again takes longer.
Unfortunately not. You actually need two static addresses. One for the NAS on your Local Area Network and a second static IP address for your broadband connection. What you can see in the video only addresses assigning a static IP address to the NAS on your LAN. Basically, the IP address on your broadband connection needs to remain static. This is so that when you use your domain name (example.com) to remotely connect to your home network. The domain name is always pointing at your network and not some strangers home network. Your router will then route your request to access your NAS, via something called port forwarding. However, in order for port forwarding to work. Your NAS also needs to have its own static IP address from within your local network. As most domestic ISP’s don’t tend to offer static IP addresses, unless you purchase a business broadband connection. You will need to use a service called Dynamic Domain Name System (DDNS) to make it appear as if your broadband connection has a static IP address. Unlucky, your NAS can be setup to support DDNS. There are loads of DDNS services that are free and will work with your Synology NAS. However, if you use QuickConnect, DDNS can be automatically setup as one of the steps in the setup wizard.
can't figure out how to share (video) file as video stream instead of download. I wan't to give link of video file, so user can directly connect and watch it.
Hi Yusuf One method is via Video Station. First you need to log into video station as a user with Administrators credentials. Then place the mouse pointer over the video you wish to share ie a movie. This will place three icons over the the poster art. If you select the Options icon a quick menu will be displayed. Select Public Sharing. When the Public Sharing Window opens, if you tick the tick box to make the video public, the URL to stream the file will be displayed. When someone tries to load the URL, Video Station will automatically start to stream that film. Hope this helps
Instantly made the connection fail and unable to connect. Great. Guessing because I am using LA when I changed to a static IP it's showing 2 clients using 1 IP and now I can't get on my NAS....I have never been able to find my NAS with that site. I have to use the assistant for windows. *Update. After a router reboot, I had to go unplug the Ethernet cables from the back of the NAS (twice) and eventually SA was able to find the active connection. Now if you could (if you haven't already) go about finding the NAS external IP or just doing one of these on wordpress/website hosting that would be great. I own a domain from godaddy.. but I can't get my wordpress and that domain linked... i also can't just see a wordpress site from outside my network.
Hi Alex. Regardless of your router, the same basic principles for assigning a static IP address to your NAS should apply. So from the administrators interface on your router. You should be able to find the DHCP settings. Then just like in the video, you remove a block of ip addresses from your DHCP address pool. After saving the changes to your router. You will have a block of ip addresses that are not part of DHCP. Any address in this block can now be assigned to your NAS to give it a static address. A couple of tips that might help. 1. Really get to know where all the settings on your router are. When I play with a new router, after I have configured it, I like to screen print all the settings/options for that router. That way I will always know what a setting should be, if I decide to change something. It also helps me to plan what I need to do and were I need to go from within the routers interface. 2. Make sure you know how to factory reset your router. If things go really badly wrong, you can factory reset and start again. 3. Make a file which contains all the basic information about your router and broadband connection. So if you ever have to factory reset your router you have the basic information for setting up your router again. For example note down all the details your ISP may have sent you. This will include all account names, passwords, and telephone numbers (as you might have to call your ISP's Helpdesk). In the same document note down the default factory settings for your router ie routers default IP address, its default admin user name and password. 4. If you are planning to make your NAS remotely accessible via the internet. You will have to make more changes to your router. So you will need to study your routers user manual and make sure you understand concepts such as a firewall and how to set port forwarding. Sorry, I can't be more specific to your router but I hope this helps a little.
What is the source of the webpage that is "find.synology.com/"? NSLOOKUP shows that it is an Internet resource. That is, the DNS is resolved by the ISP DNS server. If so, how can that DNS server resolve and find something that is inside the LAN? Below is a forum thread that addresses this concern, namely how can an Internet DNS server able to resolve a DNS query for a LAN resource that is behind a router/firewall? With that said, you should do a series of videos that explores the security of exposing the NAS to the Internet. www.reddit.com/r/synology/comments/8ls0cs/findsynologycom_scared_me/
Brilliant tutorial... i get frustrated by synology for the lack of clear and concise instructions and tutorials but this was a pleasure to behold.
I have to say, after watching youtube 'how to do tech stuff' for over 10 years your series on how to set up a Synology NAS is the by a LONG margin the most concise, easily understood, well delivered, comprehensive and detailed tutorials I've EVER watched. I've seen the first 4 videos and look forward to the next 17! I'm learning an amazing amount of stuff in such a short period. Kudos to you, you really should be a teacher... :)
I second this. This is easily one of the best tutorials I've ever seen on TH-cam. Thank you!
Couldn't agree more. It's refreshing to find a video explain a topic as clearly as this one does. Bravo :)
Same.
If any teacher ever talked this slowly and laboriously, the whole class would fall asleep, and I'm watching this at 1.5x playback speed!
TOTALLLLLLLY agree Keith, this guy is buy FAR the best instructions I've ever seen. Everything I was thinking, you took the words right out of my mouth. I'm saving this for future reference.
Cannot thank you enough for your help. I thought buying a synology router & NAS would be a great idea for ease of use, but unfortunately Synology has lacked tutorials for customers who are not networking gurus. Searching through Synology forums, subreddits, and TH-cam forever it seems to be able to get clear concise answers to the questions I have. Wish I found this video weeks ago! Thanks again!
Is Tracking, you check Tracking
You are an absolute star ! Spent my whole Sunday trying to make sense of this. You succeeded where others failed miserably !THANK YOU
Oh WOW, have you done a great job here, so difficult to find such a comprehensive tutorial, written or video. You explain everything so clearly. Why don't Synology just put just put a link to you. Thank you very much.
Thank you. Probably the clearest, conscience, well structured and especially delivered tutorials I have ever seen. Well done.
Static ip and dhcp has never made sense to me. Port forwarding always made me tear my hair out. I finally understand this stuff thanks to this video! Thank you
Thanks. I used to do this stuff all the time, years past. This was just the right level of detail as refresher.
@mydoodads
I have to say sir, that you DEF hit it outta the park with your videos. Your verbal pitch speed is superb !!!!! It's just the right speed to catch what you're saying and allow it to sink in, know what I mean ? How you navigate through your onscreen graphics is like nothing I've ever seen man ! ! ! ! Many other presenters race through their demos like a race car driver. So the viewers end up having to watch it over and over to get anything out of it. But YOU ?!?!?!?! Like I said man, your instructional speed is perfect. . . you never speed up, and you always seem to pause at just the right time to allow the viewers time to digest and catch up if, anyone else was like me, following along doing the tweaks as he was speaking.
Seriously though man, you REALLY are THAT good. Great video and can't wait to see the whole series on the Synology NAS. I just bought the Synology DS1019+ last week, so I'm just setting it up, moving files and media over, and I needed help setting up the ports and stuff on the router and NAS side.
Wish I could stay up longer to do this but I gotta hit the rack. Until next time mate !!
Mike
Thank you for your support. It's so pleasing to know that the style I decided to use in my videos is appreciated by others.
@@mydoodads ; My pleasure, I always give credit where it's due. I do have a question/ISSUE that has popped up since I've assigned static ips to my new Nas. I can't "MAP" a network drive to it now. I had one mapped to it before I assigned a static ip to the nas.
I unknowingly tried to use the "OLD" link and obviously it didn't work. So I deleted that link. But when I tried to remap it, it would not work.
1. I opened up my windows 10 explorer window
2. Highlighted the "THIS PC" in the left column
3. went to top to select "MAP NETWORK DRIVE"
4. A window pops up to allow you to select where you want to map from
5. I select/highlight my DS1019+ . . . . . then the blue circle revolves around and around. . . keeps going
6. Then I get this error message; WINDOWS CANNOT ACCESS \\THEKINGDOM [may nas device name] . Check the spelling of the name. Otherwise there might be a problem with your network. To try to identify and resolve network problems, click Diagnose. 'ERROR CODE 0x80070035 the network path was not found
7. When I click on Diagnose, I get this message; PROBLEMS FOUND; Your computer appears to be correctly configured, but the device or resource (THEKINGDOM) is not responding"
Do you have a video already out that identifies and fixes this issue ? Any ideas what it could be and how I can repair this ?
Thanks man, I'll wait for your reply
@@proudcanadian9816
The obvious fix might be to reboot your computer and allow Windows 10 to try and remap your home network.
If I remember correctly, Windows 10 will use NetBIOS over TCP/IP, and Windows Workgroups to find the host name of a device on a network.
So because Windows will have cached the address of your NAS. A reboot might force the computer to update that cached data, which is pointing at an IP address that your NAS is no longer using.
However, I would personally recommend that you move to using a more universal method (ie one that works in Windows, macOS, iPadOS and Linux) for connecting to devices on your home network.
So try using your new IP address instead. For example setup your mapped drives using something like \\192.168.1.2\Public
If you are interested, I did make a video on how to connect to network shares via Windows 10 - th-cam.com/video/dlUeUDqSLXI/w-d-xo.html
In the coming months I plan to make a video on creating a script that will auto mapping network drives. So please look out for that video.
If you want to be able to use a host name when connecting to a device. For example \\kingdom.synology.me then this video looks at how you setup DNS server - th-cam.com/video/iqgp2L1K6RQ/w-d-xo.html
By using DNS server, you will be able to more easily connect to other devices that use static IP addresses. For example your Router, a Printer and your other NAS boxes.
Hope this helps.
@@mydoodads Hey man, ok I'll give the restart a try first. I was at it for a while this morning, then I put it aside and moved on. I didn't want it to occupy my whole day. . . know what I mean ? lol
I'll let you know how it turns out. And I do understand that this channel is a HOW TO, and not a forum. I was just at wits end and didn't know what else to do is all 🙄
Thanks for the reply and I appreciate your other suggestions. I'll try rebooting all the devices and let you know how I made out. I did reboot/restart throughout the video as you mentioned. But there may be something I just overlooked.
Mike
@@mydoodads Hi doodads,
Well you were right on the "reboot" option. I can't really explain it except to say that the problem was probably with the "reboot order" that I had done the first time around. . . if that makes any sense. In an effort to maybe help anyone else that ever encounters a similar problem as mine, I'll post what I did.
As you know all too well, EVERYONE'S computer and networks are so infinitely different that it's impossible to have a "one size fits all" type of scenario. And I knew that when I encountered that problem. The only thing I needed was a bit of guidance, and you did just that.. Thanks for replying man.
I believe this is what I did to make it happen:
-- I shut down, and unplugged all 3 of my NAS devices from my switches[ DS1019+, the DS214play, and my old dinosaur but still runs well, the Dlink DSN123 ]
-- I unplugged my cable modem, let it sit for a minute or 2 while the router did it's thing shutting down
-- I went into my ASUS RT AC5300 router and did a reboot from the option screen, rather that pressing the power button on the back to shut it down.
-- when the router had done it's thing, I started the modem back up again and waited for all the necessary lights to come up before I proceeded
-- while that was happening, I started up the 3 NAS devices and plugged them back into the switches
-- I did not reboot my pc because I wanted to watch the router reboot screen recycle [ don't ask me why. . . I just did ]
-- once the router was up and running, I checked the device map to make sure the static IP's that doodads showed us in ep04 in his synology series were still showing. BINGO they still kept their respective IP statics
-- I then checked that the ips ALSO were present in each NAS
-- the FINAL test was going back into my PC win explorer and try to map the drives. . . . . . annnnnnnnnnd B O O M Bob's your uncle IT WORKED !!!!! :D
Once again, big props to @mydoodads for his excellent instructions and tutelage for how to set up static ips. For whatever reason, my solution was in the reboot sequence.
And there you have it !
I wish I'd found this series before setting up my DS218 as it would have made it quicker & easier. Luckily I found this when I had to make changes to the storage pool & volumes. I had to change it up as I rushed through initial setup and accepted all the default options, forgetting that the default for multiple drives would have been a RAID setup for backups when I wanted to have the full amount of storage available. Your series should be linked by Synology replacing their included setup guide as Jill and Glenn mentioned below, and pay you for hits accordingly. You've made it easier for people to get the most out of their Synology NAS in simple, easy to follow descriptions and examples, which in turn allows people to see what great little units they are. Thanks for your work :).
That was hands-down the best explanation I’ve ever heard on the subject. Thank you thank you thank you!!
Just wanted to say a big thank you for these series of videos you have put together. They are a fantastic teaching aid and have expanded my NAS knowledge immeasurably! THANK YOU!
The Best video on this topic.
Please make a video for using Synology NAS as
1. Storage server for home or small office.
2. Map NAS as network drive in all Windows computers in network.
3. Set scheduled, automatic, incremental, and encrypted back up *FROM* NAS *TO* Google Drive. To protect my data from *Ramsomware, fire at my home etc* (while making sure that Google can't read my data).
4. Restore Data.
Thanks in advance.
Thank you for such a great series. It helped me so much when setting up my new DS918 NAS about a month ago. Then again yesterday, I had to upgrade my Virgin Media modem to one of their Hub3's and once again these videos helped to get my NAS settings sorted again to work with the new modem.
Thank you for putting the tutorial together!
It’s simple and yo the point
Thank you again
Thanks for the support. However, the DSM7 version of this video will be coming at the end of the month, which might be more useful.
Thank you so much, your video helped me out a lot! I had been searching the interwebs for an hour and almost gave up, but you gave me the answer! I cannot thank you enough for this video!
Thanks for all your help. Very concise in your comments and you make everything very easy to understand (especially for someone with very little network experience). Will recommend anyone with a new Synology to Subscribe
Unbelievable excellent tutorial ! I'm in 4th chapter and can't wait for the rest. Tnx !
Thank you so much for your clear instructions. Much appreciated! 😊
Thank you so much. This video made it really easy for someone that doesn't know that much about networking to figure out how to get my Synology NAS working with my new ASUS router.
you are very good. I don't even feel overwhelmed, Thanks
Fantastic work - saved me a huge amount of effort after I configured a new (Synology) router for my Synology NAS. Thank You
love this, so clear, understandable and a great voice. well done !!!
Very helpful, very clear - thank you! If only I had found your video an hour earlier ...
This was very nicely explained, thank you.
As so many others have already said......EXCELLENT video! Your instructions are easy to follow and you explain everything you do as you are doing it. Thanks so much for taking the time to do these videos! A++++++++++
I have a client asking me about cloud storage and file sharing solutions. Your videos have been really helpful in gathering information to present them in regards to using a NAS. Excellent work and very thorough explanations. Thanks!
Very clear instructions. Thank you sir...worked like a charm.
Amazing ! You make this look so easy, I actually understand what I am doing now. Appreciate all the work you put into this.
Fantastic video guide. Thank you for taking the time to make such a clear tutorial!
I noticed you used a Synology router. Will you be doing a tutorial series on these routers, namely how to use the Synology Router Manager (SRM) operating system? Your videos are so clear and concise. Presumably, any videos on the SRM will be the same.
Thank you so much! This made it an easy process.
Great series so far. I'm running 5 synology nas boxes at my job. Really good boxes and the packages allow one to use the nas to the max. One note tho', you have been masking your MAC address throughout the series, but when you displayed your ipv6 address the link local address (prefix fe80) includes your Mac address as the last part of your ipv6 address. You may want to mask that too! ;)
decommissioned.
Then from all the great feed back I have received (both positive and negative) I think I have a better idea as to what worked, what needs improving and a couple of ideas about topics I want to try in the future.
So I'm really looking forward to starting a new series for DSM7 some time this year. Which I hope will be better and more comprehensive than what I have done so far.
Thanks for the advice
@@mydoodads DSM7 is going to really interesting. I found your series while searching for some video that a friend of mine could use to learn from as he is waiting for a ds218 to arrive. He was looking for something to keep from spending $$$ on Dropbox. If you share files over 2gb Dropbox requires both sides to have a paid Dropbox acct, plus as his file distribution goes it will save him from having to purchase more Dropbox space. So, be sure to include how to share files over the internet with your new series - its really neat. Later!
bloody awesome mate nice and clear with time for me to work along as you instructed to get it done !
Here you will find the gold you were always looking for Part 4
This is a fantastic video, thank you so much for the detailed explanations.
I live in a country outside the US that has many levels of monitoring and access restrictions. I have my Synology NAS setup in the US. There is nothing even remotely "secret" in a strategic sense about the data I store (music, family video and some personal correspondence). I have tried the DDNS solution but find that I still cannot directly access the NAS. This makes backing up my and my kids Mac across the internet to the NAS directly impossible. My question is this: If instead of doing Time Machine backups for my Macs, I simply periodically copy over the backups using FileStation, can I later backup from those backups by copying them back onto a local hard disk where I live?
I appreciate that you may not be able to answer this question, but would appreciate any ideas you might have. I have 5 macs that I need to have backed up using this less than perfect process. My original idea was to use TimeStation to backup to the NAS but I cannot get the finder to recognize the DNS of the NAS through the VPN layers for some reason.
Your videos have been absolutely fantastic and so very helpful so far. Is the setup of a static IP address process the same when using a BT smart hub 6 router?
Yes. The same basic process will apply to any home wifi router.
However, to avoid confusion. This video only deals with assigning a static IP address to your NAS from within your home Local Area Network (LAN).
If you are looking to be able to remotely connect to your NAS from the internet (Wide Area Network). You also need to have a static public IP address.
As BT do not offer public static IP addresses to their domestic broadband customers. You will also need to setup DDNS. This is a topic we cover when we look at setting up Direct Access on a Synology NAS - th-cam.com/video/STlKmQE5luM/w-d-xo.html
Sorry for the long answer, but I thought it might be useful to clarify this point, to anyone else reading this comment.
Incredible work! Thank you!
Great video, thank you very much for your effort, the only question I have is what is the need of configuring DHCP pool 04:30, every IP within the subnet can be configured as a static IP and it will excluded from the DHCP pool, I really can not find any reason to configure the DHCP in the router. Thanks again.
HI Adam
I like to structure my DHCP as it gives me a number of benefits. By structuring my DHCP I know that a specific range of IP addresses have been ear marked as static. So I know that any devices which use an IP address within that specific range, I have deemed as being of functional importance to my network. By structuring my DHCP, these important devices are then all listed sequentially. ie router - 192.168.1.1, NAS - 192.168.1.2, Printer - 192.168.1.3 etc. This in turn gives me a simple to remember mental map of my home network.
For me personally when configuring a network, if the static IP addresses used by devices on my network run in sequential order. Tasks like wireless network bridging, printer setup, switch configuration, VLAN, DNS, port forwarding, and configuring a DNS server are a lot easier to remember, which for me tend to minimise my mistakes and help with troubleshooting.
However, perhaps the most important reason why I have structured my DHCP is because I constantly fiddle with or add things to my home network. So I need to ensure that what ever project that I am working on, does not adversley effect the rest of my network.
While I do document which devices have been issued with static IP addresses. If there is an instance were I want to do a quick and dirty config on say, a QNAP NAS. I know from my mental map that I can assign the QNAP NAS with the IP address of 192.168.1.19 and it will not create a IP conflict on another device in my network.
I hope this response gives you a clue to my thinking, and thanks for the question.
Wow! That was clear! Thank you!
Excellent tutorial. Very clear and detailed.
Brilliant tutorial. Thank you.
great and easily too understand tutorial but how do you think about using an dns service like google 8.8.8.8 or 8.8.4.4 when assigning a static ip adress?
That is a good question.
Ultimately, I'm not sure that its all that important which DNS service you use, as there is nothing stopping you from using any service that you would like. In fact if you were to look at all the devices I have on my network, the DNS servers that they use vary from my ISP's, to Googles, and Cloudflare's. While this is not an issue for my network. I think that it demonstrates a certain level of inconsistency on my part as to how I have been setting up devices.
So I would suggest trying out a couple of different DNS servers on say your main PC, see how they perform and unlike me, stick with that DNS service when configuring devices. However, if privacy is a concern maybe don't use Googles DNS service and try something like Cloudflare's DNS instead (1.1.1.1).
Right... now I'm off to spend the morning changing the DNS addressing to my network ;)
This helped me, though I'm using it with Unraid. Thanks!
Excellent tutorial! Very useful!
I am trying to perform this did you have to buy a static ip for your router? and if so do you have hardware firewall as well mainly just trying ot understand will I be able to do this with a dynamic ip? Thank You in advance great video
I have long suspected I may not have explained myself very well on this video. Sorry.
Basically, you can assign static IP addresses to local (LAN) devices or to your public (WAN) internet connection.
In the video I am assigning a static IP address to my NAS, so that its easier to find on my local network (LAN). You would also perform the same action when configuring a network printer.
However, if you were looking to have your NAS accessible over the internet, then you would need a static IP address which you would purchase from your Internet Service Provider.
Unfortunately, as most domestic ISP's do not offer the option for using a static ip address, unless you pay business rates. We can get around this issue by use something called DDNS which its free (depends on which DDNS service you use).
Dynamic Domain Name System, is basically a service that monitors your internet connection, to make it appear as if you have a static public IP address.
As to your query about the firewall. Your routers built in firewall should offer enough protection. By default a router's firewall will be enabled and it should already be blocking all incoming traffic.
To check your routers firewall try using shields up its free - www.grc.com/
When you get to the stage were you want to make your NAS accessible via the internet. You would use port forwarding rules setup on your router to forward specific types of network traffic to your NAS.
Hopefully as you work through the videos, this should all start to make more sense, but specifically look out for the video on Direct Access.
Hope this helps
@@mydoodads this helped me understand quite a bit better for certain. I am using this in a business which wouldn't have mattered so much had I not started looking at static ip's right away. So now every time that term is mentioned I question weather it's a purchased one or an internally assigned one. Your video was a tremendous help it was as well as your explanation here and greatly appreciated. I do plan to watch the entire series as Time permits. Thanks again
Man I wish I had found your your tutorials a week ago, instead of being gung ho & trying to wing it. I have a Asus RT-AC88U has so much information it's easy to get lost in the translation.
I have never configured it to be as a static IP set up. And for the life of me struggles to know how to do it. Is it essential for my NAS to have a static IP address
Thank you for your time and patience that you have invested into making sure us mere mortals can understand how to configure our Synology NAS devices
Any help greatly appreciated
It’s not essential, but if you intend to use your NAS for anything other than just file sharing. You might be better served assigning your NAS with a static IP. Ultimately, it will just make life a little easier later on, particularly if you intend to run your NAS as a media server.
Flicking through the ASUS RT-AC88U manual - dlcdnets.asus.com/pub/ASUS/wireless/RT-AC88U/E10302_RT_AC88U_Manual.pdf
Have a look at page 66 - 68 which covers configuring DHCP Server. You should find the DHCP settings under Advanced Settings - LAN - DHCP Server. The way DHCP is setup is very similar to the settings seen in the video. Just adjust the IP Pool Starting Address field and select Apply.
Hope this answers you query.
Splendid, clear advice. Thank you
I prefer to use DHCP reservation from the router. This way, I have centralized management of IP addresses assigned to all of the hosts in the LAN. Assigning static IPs to hosts device by device basis requires me to remember what device has what IP. However, there are cases what warrants static IPs. This includes when VLANs are used and other attributes that the DHCP server might not support. Not all DHCP servers are the same. Some offer more advanced features than others. Most router-based DHCP servers are fairly basic, necessitates the need for assigning static IPs to the hosts. By the way, you can use a Raspberry Pi as an DHCP server with advanced features. It's a pretty interesting project if you have the time.
Really excellent education on my NAS setup!
I followed your instructions and completed the setup. I am now thinking about changing the wifi router. Can I just swap it for a new one or do I have to redo everything?
As long as you change the IP address and DHCP settings on your new WiFi router, so that the settings match the IP address and DHCP of your old router. It should be OK to just swap out routers.
However, if you have configured your NAS for External Access you will also need to set your port forwarding rules. It’s worth noting that if you have configured your NAS to use UPnP to create Port Forwarding rules. In order for that feature to work, your new WiFi router has to be compatible with your Synology NAS.
If your new WiFi router is not compatible, then you will also need to manually configure Port Forwarding on your new router.
Hope that helps answer your query.
If I have a IPV6 default gateway (not blank), do I need to assign a static IP on my Synology NAS?
Great video, thank you! Liked and Subscribed!
Absolutely outstanding, thank you!
You are my hero!
Thanks a lot, worked just great!!!
YOU ARE AMAZING!
Can you do a supplemental video to set up IPv6? Thank you in advance either way
If my ISP does not allow static IP addressing on my plan how can I set this up? Do I just use "find.synology.com" everytime to redirct to the current IP address the NAS drive has been assigned?
You can add and pin a comment, that this is resolving any issues when your internet is beeing chocked/freeze for a moment every few minutes or a few times per hour. Very important step! :)
Thank you :)
Hi Andy, that's good news as it sounds like you worked out how to fix the freezing problem you mentioned in another post. 👍
@@mydoodads indeed. Nobody else, except you in your video, advised to set a static IP. That is really important info,
Connecting a NAS to my cable provider does NOT seem plug-n-play. So, as a typical cable customer (Spectrum, Brighthouse, Verizon), I cannot just buy a Synology or Qnap NAS, plug it into my cable provider's equipment and access my NAS on either my home network or through the Internet WITHOUT buying, for example, a Synology Router (which will grant me access to advanced setup features that my cable company may not)? Has any Spectrum or Brighthouse or Verizon customer successfully added a NAS--Synology or Qnap--to their network?
Thank you.
Great vid. Thanks for helping a non tech guy out
thank you, amazing video, but how u access the network from synology ? i dont have a menu (network center)
Hi Charbel
If like me, you are using both a Synology router and a Synology NAS as your home network. Just to confirm, only the Synology router manager (SRM) will have a Network Centre icon. Your Synology NAS (DSM - Disk Station manager) should be displaying Package Centre, Control Panel and DSM help on its desktop.
If when you log into your Synology router, you don't see a Network Centre icon, more than likely you have logged into the SRM with a user account and not your administrators account.
You can tell that you have logged into a user account, if you select the Main Menu icon from the desktop on the SRM, and it only displays SRM help and FileStation.
I hope that helps.
@@mydoodads thank you for your kind reply. just another question, i am always changing my disks as i am getting bad sectors. each 6 mnth, any suggestions please. thank you in advance.
Hi Charbel
For my NAS devices, I prefer to use hard drives designed specifically for a NAS device. I tend to fit 8Tb drives as they more often than not will spin at faster speeds. However, for most home users I doubt that they will notice the difference between 5900 RPM and 7200 RPM. Especially if they are accessing network shares via WiFi. So a 2, 3, 4 or 6Tb WD Red drive would be fine.
Currently, I mostly use the WD Red NAS Hard drives. This is because so far, I just have not had any problems or issues with them. - amzn.to/2HCYeTp
A good alternative might be the Seagate IronWolf NAS drives - amzn.to/2F0fA7r I just fitted one to a new NAS that I am currently playing with. So far the Seagate drive has been as reliable and performed as well as the WD Red drives.
Checking the warranty for both the IronWolf and WD Red drives. Seagate offer a 2 year warranty on an IronWolf drive, while WD offer a 5 year limited warranty on the Red drives. The Seagate might have the better warranty.
Thank you for your videos, very informational. I use it
very useful video !!!!!!!!!!
Interesting, on the router just set the static IPaddress & on the NAS just change the LAN IPaddressing from DHCP to manual & that static IPaddress. Thks again
After I assigned it a static IP address, the synology username and password do not work any more. Please help!
I can't find the app NETWORK CENTER, how do you get that?? Thank you very much for your videos.
Network Center is not part of Disk Station Manager (DSM). Instead its part of Synology Router Manager (RSM).
Sorry, if it's a little confusing, at the time I thought it was a good idea to use a router that has a similar user interface to that of a Synology NAS.
However, if you own either a Synology RT1900ac or RT2600ac wireless router then you should be able to find Network Center either on the Desktop of the SRM or from the main menu of the SRM.
Please note that Synology updated the Network Center icon sometime last year. The newer icon is blue and Hexagonal.
Hope that helps
@mydoodads Thank you for these great, informative video tutorials. On the static IP address, having a slight issue - I have set it up exactly as you indicate in the video however the only issue I experienced was that after assigning the static IP address to the NAS and re-setting all devices, the search function on find.synology.com/ could not then find the NAS device (on macOS which is what I am using).
I am able to navigate directly to the login page by using the newly assigned static IP address, but not not sure whether operating in this manner brings up any issues down the line and why the device can't be located via the online webpage tool.
Perhaps a mis-step on my side (I re-did the process outlined in your video 3-4 times however just to be sure with the same result), but wanted to check if there is anything I may be missing here that you could kindly point out? Any recommendation on solving this issue would be greatly appreciated! Thanks in advance.
The NAS used in my TH-cam videos is not my production NAS, but a secondary NAS that is only used purely for filming. I actually have a production Synology NAS which sits on a separate network which I have already fully configured.
To confirm, my production NAS exhibits the exact same behaviour as your NAS. So if I try and use find.synology.com on my production network I receive the message "DiskStation not found on LAN". However, my production NAS is in a totally different state of configuration to the NAS as seen in episode 4 of my videos.
When we assign a static IP address to any Synology device (I also use Synology Routers) find.synology.com should still be able to find those Synology devices within the LAN. The reason my production NAS can not be found by find.synology.com is because I have enabled the NAS's Firewall. Which is preventing my production NAS from being discoverable via find.synology.com
If I turn off the NAS firewall, my production NAS is once again discoverable via find.synology.com. So to put your mind at ease, making your NAS non-discoverable via find.synology.com should not impact the running of your NAS, and if you happen to be a little paranoid about network security possible a good idea.
However, having said all this, you may still want to find out why your NAS is not discoverable purely for your own piece of mind. So if the issue is not resolved after you check your Firewall. It might be worth checking the following:
1. Just confirm in network settings the Subnet mask settings are exactly the same as the ones being use by the rest of your home network. Check that the NAS Subnet mask settings against those being used by your Mac
2. Check that find.synology.com has not some how automagically disabled itself. Take a looking in Control Panel - Info Center - Device Analytics - Share Network Location
3. As find.synology.com is a web browser utility. It might be worth clearing your browser cache to see if that make a difference.
Sorry, I can’t think of any other places to check but please do let us know if any of this helps.
mydoodads I have the same issue using a Surface Pro with Windows 10. After configuring the manual IP, it appears the find.synology.com setting is subsequently disabled (unless it was already disabled in here). I’ve re-enabled it, checked the subnet masks match and also cleared the browser cache. I also didn’t have any firewall activated on the NAS at the time but the issue persists. Is there any further updates on how to resolve this? Thanks - great videos by the way.
Update: Strangely, while the find Synology web assistant no longer works on the device I configured the static IP from, it does appear to work whenI search from another device on my network. Strange??
By having a quick look at the html code for Synology Web Assistant. It would appear that the code works with a number of web technologies, primarily javascript and . So to double check that Windows 10 does not have some sort of fundamental issue with Web Assistant.
I just pulled out a Surface 3 with Windows 10 10.0.18362 Build 18362 and can confirm that Web Assistant works within Microsoft Edge on my network.
As you did note that other devices can load Web Assistant. I would suspect an issue in your Surface Pro rather than a setting on your network or Synology NAS. A way to test this might be, to create a second dummy user account on your Surface Pro, and then see if from within that profile you can access Web Assistant.
If you can, then you will know that the issue relates to something in your main user profile, rather than the whole computer. If you can’t then the issue might be something in the instance of Windows or the web browser you are using.
By installing a second browser such as FireFox, and then re-testing if Web Assistant works within that second browser. You might be able to further narrow down where the issue is.
Sorry I can’t offer some sort of magic fix to your problem, but I hope that at least this response will point you in the right direction.
Excellent work! I just bought my first NAS, a Synology 918+ with 2 Seagate 10TB Ironwolf drives, and I'm setting it up using your instructional videos, and so far they have been very helpful. My question is, when I set up the static IP like you show in this video, the first available number is 192.168.1.3, and it said the 2 is already in use. Any idea why it said that, or is it anything to worry about? Thanks again for all the information. ps, my status light is constantly flashing. Is that normal?
Its nothing to be worried about.
Your router's DHCP will be set to lease an IP address for a specific amount of time for example 24 hours. When a device requests an IP address from DHCP, DHCP also informs that device about how long it can use that specific IP address for.
Its sounds like a device on your network was assigned 192.168.1.2, but has not yet relinquished that IP address. When the lease time for 192.18.1.2 has expired, the device using that address will automatically ask DHCP for a new address.
However, your probably don't want to wait to assign your NAS with 192.168.1.2 So you will need to find the device using that IP address and reboot it. That should clear and free the address 192.168.1.2
In the first instance try using a ping command. You want to ping 192.168.1.2 on your network. If you receive a reply to your Pings, that will confirm that a device on your network is using 192.168.1.2.
How to Ping:
On MS Windows: open search, type CMD and press enter. At the command prompt, type PING 192.168.1.2 and press enter. To cancel the Ping press Ctrl + C
On macOS: open Spotlight, type network utility and press enter. In network utility select ping. Enter 192.168.1.2 and press the Ping button.
Once you have confirmed that a device is using 192.168.1.2, you need to hunt it down. You can do this in one of three ways. Your router might list the ip addresses that it has assigned to devices on your network. If you check that list it might tell you which device is using 192.168.1.2
Alternatively, you could manually check all the devices in your home network to see which device is using 192.168.1.2. Finally, you could download a piece of network scanning software that will help you identify which device is using 192.168.1.2
To answer your last query, I have two Synology NAS units, the one I use in the videos, and one which I use as my production NAS. Neither of their status lights constantly flash, so I would say thats not normal. A green flashing light might be an indicator that no hard drives are installed. If you are in the process of initialising your Hard drives and they are creating Volumes(it will take hours depending on the size of the drives you fitted), that might explain why your status light is flashing.
However, this Synology article might help you identify why the status light is flashing.
www.synology.com/en-uk/knowledgebase/DSM/tutorial/General/What_can_I_do_if_the_STATUS_LED_keeps_flashing_in_orange
Hope this all makes sense and thank you for your support.
Sending love for these great videos, although I do set playspeed to 1.5 :)
Thank you!
I've said it before, and will say it again: I LOVE your video series! (And thank you for it).
My question is what if I cannot find/determine assigning a static IP address to my NAS?
My network provider issues the hardware routers (which does both 5ghz and 2,4 ghz) and even when I open the admin settings of my router, I cannot find where to tamper with the DHCP server settings, and it doesn’t show me a start and end IP address range.
Is there another way to find/determine the static IP address?
Please let me know.
Hi Erich
If you can’t make any adjustments to the DHCP settings on your router, there are a couple of alternative methods that might be worth considering. For example if your router has a DHCP Reservation option. With this option you could use the setting to assign a static IP address to your NAS. However you will have no control over which IP address is assigned to the NAS. So for example, rather than 192.168.1.2 you might have to use 192.168.1.236.
If you can turn off the DHCP server on your router, a second alternative might be to use the DHCP server built into your NAS. If you look in the DSM under Control Panel - System - DHCP Server - Network Interface. You will find an option to enable DHCP server to a LAN port on the back of your NAS.
While this is how I have my NAS configured to my personal network. You do need to be careful to assign a static IP address to your NAS, have the computer you are working from connected via a network cable (to your router) and also assign a static IP address to your computer. This is all so your NAS and computer can communicate with each other, while you disable DHCP on your router and setup DHCP on your NAS.
Finally, if you can place your router into modem mode, and then buy a new Wireless Router for example a Synology RT2600ac or Google WiFi. By using your older router just as a modem to connect to the internet. You will have full control over your new Wireless router including DHCP. This will also give you all of the advantages of a modern Wireless router along with better control over your home network.
Hope this helps
I hate to do this now but how do I undo all my mistakes?
Thank you so much. Can you tell me how to setup the internal access ex: \\customname instead of using \\192.xxx.x.x ?
You would do this by installing DNS server on your NAS - th-cam.com/video/iqgp2L1K6RQ/w-d-xo.html
However, because of a trend with modern browsers, in that they will only open web pages that have a valid SSL certificate. You will also need to install a valid SSL certificate on your NAS.
Sorry I don't have a video on how you just install an SSL certificate because one was automatically when we configured Direct Access.
thank you very much
These are excellent videos! Thank you. I, too, am a NON TECH person and I'm setting up my first NAS (ds918+). I'm primarily planning to use it as a media server with Plex. I would love to be able to use Plex away from home by remotely accessing my NAS. This video I think sets up an important first step by assigning the NAS a static IP address. When I get home later today I plan to follow your tutorial to set my static IP address on my Synology NAS (I have a Linksys EA9500 router so it might look slightly different, but fingers crossed). But I am having trouble finding any tutorial on how to set up the remote access through Plex so that I would be able to access my videos and photos on my NAS through Plex while I'm away from home. Do you have a tutorial on this, or instructions on this, or could you please make a video tutorial on this? I'm sure these videos require a lot of work but they are wonderful and I would really appreciate any help. Even if it is just pointing me in the right direction. I feel like the other instructions I've found for enabling remotes access to the Plex are written for folks who are more tech savvy than I am. Thanks in advance.
Hi Jeffery,
Thank you for your kind comments. You are correct, these videos do take a great deal time to plan and produce. So I am always glad to hear from anyone that finds them useful.
At the moment, Im about a third of the way through the basic setup process for a Synology NAS. My hope is to start looking at remote access in the spring of 2019. So, to answer your question. No, I don't have any tutorials or instructions on remote access or Plex yet.
However, the following might help you in the meantime. Synology's support notes for Quick Connect offers a simple method for gaining remote access to your NAS.
www.synology.com/en-uk/knowledgebase/DSM/help/DSM/Tutorial/cloud_set_up_quickconnect
Then once you have remote access this video might help you to setup Plex.
th-cam.com/video/t4VvwjJQ2as/w-d-xo.html
mydoodads excellent! Thank you very much. I’m confident I can do this now, which is a big step for me. Keep up the great work!
HI, How do i setup a static address for the External Address. I use the DS File App on my mobile but the IP address within the External Address keeps changing and doesnt allow me to connect after a day or so. Is there a way I can manually set the External IP, please send me the instructions if possible
There is no way for you to set your own External IP address. That has to be done by your Internet Service Provider (ISP). However, as most ISP’s (certainly in the UK) will not offer a service to give your domestic broadband connection a static IP address. They will instead offer to upgrade you to business connection, which usually is very expensive.
Luckily, In the UK there are a couple of small ISP that will offer static IP addresses to domestic customers for a small fee. Both, Plusnet and John Lewis Broadband do offer static IP addresses which are activated once you make a single £5.00 one off payment. While I have not used John Lewis Broadband, I do use Plusnet and have found my broadband connection to be very solid and reliable.
If you are not based in the UK or you don’t want to change supplier. An alternative option to having a Static IP address, is to setup DDNS or Dynamic Domain Name System on your Synology NAS. While this service will not assign you with a static IP address. It will monitor the changes to your broadband address to make sure that a domain name can always connect back to your NAS.
I cover setting up DDNS in my video How to setup a Synology NAS Part 34: Configuring a NAS for External Access - th-cam.com/video/STlKmQE5luM/w-d-xo.html
Hope this helps.
I set the static address at home/in network running a wireless hotspot to hopefully simulate being away from the same network instead of actually leaving every time I made a change. Then when I actually left and tried to access the drive using the same hotspot I can’t connect to it. What am I missing? Also I run a Mac. When I’m home I can mount the shares as if I have physical hard drives attached to the USB ports. How can I mount the shares as drives outside of the network? This crap is driving me up the wall
If I have understood your question correctly, it would appear that you are trying to test that you can access your NAS remotely. Unfortunatly, setting a 'local' static IP address is only the first step in getting "Direct Access" on a Synology NAS working.
While the local static IP address you have assigned is important. It will only allow the devices on your home network to know that your NAS can always be found on the local IP address you gave it.
Basically, you have to do the same thing but with your public IP address (the one your router is using to connect your home network to the internet)
However, I would recommend that you do the following first:
1. Make your NAS secure
2. Enable Firewalls
3. Get a public static IP address from your Internet Service Provider, or plan to use DDNS
4. Setup your router so that it port forwards specific internet traffic to your NAS
5. Configure Direct Access
So I would suggest taking a look at the rest of my series on setting up a synology NAS, if you have not already done so. While you could just jump to the part about External Access, I did try and produce a series that works in a systematic fashion. The link will take you to the series playlist - th-cam.com/video/Yua6dGpg4qo/w-d-xo.html
As to being able to access your network shares when working remotely from a Mac. The best option is to setup a VPN server. Once again there is a full video on the topic along with a separate video on configuring the VPN clients for macOS, iOS, Windows and ChromeOS.
Hope this helps to clear up any confusion.
Thanks a lot.
great video thanks
it fails to me when checking at the very end through findsynology web address. i restarted and followed step by step and this stopped working, i can access with the fix ip though. will it generate any issue ?
As the find.synology.com webpage is really just a convenience to help you find out which dynamic IP address you are using. Not having it working will not generate any issues.
For me, when I installed DNS server onto my NAS, was the point when the code that runs in the find.synology.com webpage broke for me.
As I have always felt that the find.synology.com webpage was a bit of a security risk. You will see that in the newer videos to this series I no longer reference find.synology but instead just use the fixed IP address.
Eventually I will be making a quick tip video to show people how to turn the feature off but if you find that it no longer works, I would argue that that was a good thing.
If the NAS has 2 ethernet ports should they both have the same static ip? I'm not really even sure why it needs 2 ethernet ports
If you have a Synology NAS with 2 ethernet ports, you can create something called a Bond. The aim of a Bond is to create additional bandwidth by merging two network ports into one. So for example, if you have x2 1Gigabit network ports, you can Bond them and create 2Gb of bandwidth for your NAS.
When you create a Bond, it will use a single static IP address. However, while, I do use a NAS that has two network ports, currently I do not Bond those ports. Instead, I have left the second port unused, then if I make a mistake with the configuration of my NAS.
For example if I were to accidentally set my firewall to lock myself out of the DSM, by simply plugging my computer into the second network port. I can regain control of my NAS.
Hope this help clear up you query.
Fantastic work, thank you. I had issues because I'd already set up a VPN on my NAS, meaning find. synology. com couldn't find my NAS!
Hi i have tried to get DHCP to say yes in LAN 1 but ever time i reboot etc, it always come back as no. I have a bt smart hub if that helps.
Hi James,
I can't think of a reason why your NAS should be giving you that behaviour. So I would suspect the DHCP on your BT Smart Hub is not correctly issuing IP addresses.
A quick google did highlight a few people experiencing issues with BT HomeHub 6's DHCP.
community.bt.com/t5/Home-setup-Wi-Fi-network/BT-HomeHub-6-DHCP-IP-address-allocation-not-working/td-p/1930852
Sorry I cant be of more help
Superb.
Hi,
I have a Synology NAS DS213j and a Router ZTE H368N.
This router has two DNS servers 1 and 2 with the IP adresses 192.121.1.34 and 192.121.1.66.
The DHCP IP adress is 192.168.2.1 to 192.168.2.252 what is different from the IP adress of the DNS servers. How do I know what static IP address I can use?
Can I sent you a prtscrn of this configuration?
thanks
Hi,
While Im not familiar with a ZTE H368N router, I did find a couple of screenshots online, so I think I understand its layout and default settings. However, please double check that what Im trying to explain does match your routers settings.
First, we can (sort of) ignore the two DNS server addresses as there is no need to touch them. The reason your router has two, but the NAS only allows entry for one. Is that the router needs to have redundancy so if one DNS server address fails to resolve a domain name request, the router can fall back on a second or third DNS server.
When assigning your NAS with a static IP address, you are isolating a few IP addresses in your DHCP address pool. This is so that those IP addresses cant be automatically assigned (via DHCP) to a device on your network.
Looking at the manual for the ZTE H368N router, it appears that your router has by default already isolated three IP addresses within its address pool: 192.168.2.253, 192.168.2.254, and 192.168.2.255.
If you check the Network settings on your ZTE H368N router, you will see in the LAN IP address field, one of those IP addresses. I think your router IP address will default to using 192.168.2.254. If this is the IP address that has been assigned to your router, we should never try and assign this IP address to another device on your network.
At the moment DHCP can assign any device connected to your network with any number in its address pool between 192.168.2.1 and 192.168.2.252.
You should be able to see a table called Allocated Addresses. In that table are the ip addresses that DHCP has currently assigned to devices on your home network.
Note down the following information about your router:
The routers LAN IP address
The routers Subnet Mask
The routers default gateway [which should be the same as the routers LAN IP address]
The routers first DNS server address
So armed with the above information we can do one of two things. As the router has already isolated three IP addresses, we could assign one of the unused static IP addresses to your NAS, i.e. 192.168.2.253 or 192.168.2.255. However, as you are new to assigning static IP addresses, lets play safe and use the second method.
*** Instructions ***
Lets remove a series of number from the beginning of your DHCP address pool. This is similar to what I was demonstrating in the video.
1. Working on your router, locate the option Network - DHCP start IP address
2. Change the DHCP start IP address from 192.168.2.1 to 192.168.2.10
3. Select Submit
This will give you 10 static IP addresses to use with specific devices for example your NAS, a Printer, network Switches etc.
4. Now reboot all devices connected to your home network (accept your router). This will force DHCP to assign new IP addresses, and stop any devices from using the 10 IP addresses you just turned into static IP addresses.
5. When your computer reboots, log back into your NAS and Select Control Panel - Network - Network Interface
6. Just like In the video select your LAN and click on Edit
7. Under the IPv4 tab, change the following settings
Address: 192.168.2.1
Subnet Mask: 255.255.255.0
Gateway: [is the IP address of your router so I would guess ]
DNS server: 192.121.1.34
6. Select OK to save the changes...
DNS tip. In the DNS server setting field you don't need to use the DNS server address that you were given by your Internet Service Provider. On my server I actually use a DNS of 8.8.8.8 (while my ISP DNS is 212.159.6.9) which is a DNS server provided by Google. As 8.8.8.8 is easy to remember, its very handy for troubleshooting network problems.
Really sorry for the long winded answer, but I hope it helps.
Does this change ip for all devices using the same router?
Because of the way DHCP works, all of the devices on your network have the potential to change IP addresses. For example if you were to reboot your router there is no guarantee that all of your devices would receive the same IP address they were previously using.
This is why devices like servers, printers or NAS devices need to use static IP addresses. Using a static IP address will help to ensure that you always know what IP address your NAS is using. This in turn helps to keep any network shares reliable as they will always be accessible from the same IP address.
So, if you were to follow the procedure shown in the video. As you would exclude 19 IP addresses from your Routers DHCP address pool. If a device was using one of the 18 IP addresses you removed. That device would receive a new IP address from the DHCP address pool.
So to answer your question... sort of.
@@mydoodads Thanks for the quick
response, I just have one thing to ask :D Is there any easier method to port forward a plex media server? :)
@@Thefisk101Gaming Check if your router has a DHCP reservation option. DHCP reservation will allow you to lock the IP address that DHCP has assigned to a device. So it will achieve the same goal.
The only reason I personally don't use DHCP reservation, is that if you replace your Router. You will no longer know the IP address your NAS has been assigned by the new routers DHCP.
So getting your network back up and running again takes longer.
Hi again what if I don't have a static ip adress from my ISP.
Can I use this method instead to make my ip static? :)
Unfortunately not. You actually need two static addresses. One for the NAS on your Local Area Network and a second static IP address for your broadband connection. What you can see in the video only addresses assigning a static IP address to the NAS on your LAN.
Basically, the IP address on your broadband connection needs to remain static. This is so that when you use your domain name (example.com) to remotely connect to your home network. The domain name is always pointing at your network and not some strangers home network. Your router will then route your request to access your NAS, via something called port forwarding. However, in order for port forwarding to work. Your NAS also needs to have its own static IP address from within your local network.
As most domestic ISP’s don’t tend to offer static IP addresses, unless you purchase a business broadband connection. You will need to use a service called Dynamic Domain Name System (DDNS) to make it appear as if your broadband connection has a static IP address. Unlucky, your NAS can be setup to support DDNS.
There are loads of DDNS services that are free and will work with your Synology NAS. However, if you use QuickConnect, DDNS can be automatically setup as one of the steps in the setup wizard.
Very fucking good 👍👍
can't figure out how to share (video) file as video stream instead of download. I wan't to give link of video file, so user can directly connect and watch it.
Hi Yusuf
One method is via Video Station.
First you need to log into video station as a user with Administrators credentials. Then place the mouse pointer over the video you wish to share ie a movie. This will place three icons over the the poster art. If you select the Options icon a quick menu will be displayed. Select Public Sharing. When the Public Sharing Window opens, if you tick the tick box to make the video public, the URL to stream the file will be displayed.
When someone tries to load the URL, Video Station will automatically start to stream that film.
Hope this helps
@@mydoodads yeah it does thank you. is there a way to protect the link with password? I need something like vimeo (or wistia) .
Not that I know of. Sorry.
Instantly made the connection fail and unable to connect. Great. Guessing because I am using LA when I changed to a static IP it's showing 2 clients using 1 IP and now I can't get on my NAS....I have never been able to find my NAS with that site. I have to use the assistant for windows.
*Update. After a router reboot, I had to go unplug the Ethernet cables from the back of the NAS (twice) and eventually SA was able to find the active connection.
Now if you could (if you haven't already) go about finding the NAS external IP or just doing one of these on wordpress/website hosting that would be great. I own a domain from godaddy.. but I can't get my wordpress and that domain linked... i also can't just see a wordpress site from outside my network.
what if I don't have a synology router? please help
Hi Alex.
Regardless of your router, the same basic principles for assigning a static IP address to your NAS should apply. So from the administrators interface on your router. You should be able to find the DHCP settings. Then just like in the video, you remove a block of ip addresses from your DHCP address pool. After saving the changes to your router. You will have a block of ip addresses that are not part of DHCP. Any address in this block can now be assigned to your NAS to give it a static address.
A couple of tips that might help.
1. Really get to know where all the settings on your router are. When I play with a new router, after I have configured it, I like to screen print all the settings/options for that router. That way I will always know what a setting should be, if I decide to change something. It also helps me to plan what I need to do and were I need to go from within the routers interface.
2. Make sure you know how to factory reset your router. If things go really badly wrong, you can factory reset and start again.
3. Make a file which contains all the basic information about your router and broadband connection. So if you ever have to factory reset your router you have the basic information for setting up your router again. For example note down all the details your ISP may have sent you. This will include all account names, passwords, and telephone numbers (as you might have to call your ISP's Helpdesk). In the same document note down the default factory settings for your router ie routers default IP address, its default admin user name and password.
4. If you are planning to make your NAS remotely accessible via the internet. You will have to make more changes to your router. So you will need to study your routers user manual and make sure you understand concepts such as a firewall and how to set port forwarding.
Sorry, I can't be more specific to your router but I hope this helps a little.
@@mydoodads thanks man
Why setting static on nas? Just assign static on router for nas based on mac
Just bought new router cannot connect to synology nas
What’s a rooter
Does not seem to apply to a DS218 - does more harm than good.
Rooter.... Hahaha.. Good tutorial though!
can you do Mikrotik router setup for synology NAS?
What is the source of the webpage that is "find.synology.com/"? NSLOOKUP shows that it is an Internet resource. That is, the DNS is resolved by the ISP DNS server. If so, how can that DNS server resolve and find something that is inside the LAN? Below is a forum thread that addresses this concern, namely how can an Internet DNS server able to resolve a DNS query for a LAN resource that is behind a router/firewall? With that said, you should do a series of videos that explores the security of exposing the NAS to the Internet.
www.reddit.com/r/synology/comments/8ls0cs/findsynologycom_scared_me/