Fixing The “This Site Can’t Be Reached” Error While this is a frustrating error, there are often some simple fixes for it. However whether you connect locally or externally, you might sometimes get an error in your browser like “This site can’t be reached: (site) took too long to respond” or “This site can’t be reached. I will discuss this point in more detail later. Key Point: It is important to know whether the URL you are using is a local or external address, because no-one will be able to use a local address (starting with or outside of your own home network. This is known as external/internet access.
If you are away from your home, you can access your NAS by launching your web browser and going to (assuming you have enabled QuickConnect, of course). You can also access your files (and the admin panel) through your web browser by navigating to – or if you know your NAS’ IP address, by going to This is known as local LAN access, and it usually starts with “192”. This then allows your NAS to be accessed anywhere in your home, hopefully allowing super-fast file transfers. Your router might have DNS caching as well, which might be utilized for this purpose as well.ģ.Write to every computer's host file: the least amount of initial work! But the one that will keep you tripping! You could edit the host file on each computer to indicate that should be 192.168.1.5.2.8 Reset Your Synology NAS Overview: How Synology ConnectsĪ Synology NAS is usually connected to your home network via an ethernet cable: by plugging one end of the cable into your NAS, and the other into your router (or a network switch). Setup the internal DNS server so it will provide 192.168.1.5 instead of 93.107.237.199 to the internal computers. pfSense has good support for it ( pfSense Manual)Ģ.Split DNS (recommended): create your own internal DNS server, which will be queried first for all internal computers. That's why it's not working within your LAN.ġ.NAT Reflection: if your gateway/router supports this, then enable it. It will send your request outside the LAN, but since your outgoing IP is also your requested IP, it doesn't go anywhere. If so, what you have is that any internal computer asking to resolve the DNS name of "" will get the answer to look for 93.107.237.199, which is not an internal IP address. If I understand this correctly, you have this server on your LAN and you port-forwarded on your router from your WAN to the internal address? And your issue is that your other computers can see the server only if they are outside your LAN (or use the internal IP)? Your question can be answered here, but it's not a Ubuntu specific issue.
ACCESS MINIMSERVER FROM OUTSIDE NETWORK HOW TO
# DO NOT EDIT THIS FILE BY HAND - YOUR CHANGES WILL BE OVERWRITTENĬan anyone help? I guess its a DNS issue but don't know how to fix this. Pre-down ip addr del 93.107.237.199/32 dev loĪnd # Dynamic nf(5) file for glibc resolver(3) generated by resolvconf(8) Here is the output of /etc/network/interfaces and /etc/nf: # This file describes the network interfaces available on your system I can putty in using the IP address inside the network. If I putty into the hostname () outside the network, it resolves correctly, but I get a time-out from within the LAN.
Everything works fine if I access the server from outside LAN but I cannot use the server within LAN. I have a server set up with a static IP on 192.168.1.5.
0 kommentar(er)
