#Access minimserver from outside network windows
P.s., if this is the cause of the issue, then you should be able to fix it by only rebooting the Windows machine, or by disconnecting and then reconnecting it’s wifi. The Windows machine can still retain it’s default gateway through NAT, which means that it will be able to reach internet addresses, but it will then lose connectivity to other devices on the LAN which are in a different subnet.
So if for example the Windows machine before had an IP in the 192.168.* or 10.0.* range (LAN), they can drop back to a 169.* address when the upstream router is temporarily unavailable: Windows devices however don’t do this, so sometimes they can drop their IP’s back to a local range which is outside of the rest of the subnet. When an upstream router / dhcp server resets, linux devices such as a NAS are capable to receive a new IP address but will also keep their old address up, in case any devices were still accessing the old address. Your macbook sends the request to the router, which sends it to the ISP, the ISP sends it back and the router is not expecting it, so it ignores the request, resulting in a time out because it can't connect to itself.Another thing you can check next time are the network stats of the Windows machine. If you setup port forwarding, most routers will not understand that your public ip address is that of your own, so you most likely still cannot access your website from your own public ip address. Now, there is one addition to the question. Once this is done, and that someone from outside enters your public IP address in their browser, your router now knows that it has to forward the request to your macbook. Websites use HTTP traffic, which defaults to port 80, so you would need to create a rule in the router to tell that port 80 needs to be forwarded to the Internal IP address. When someone on the internet wants to access your webserver, and they enter the public IP address, the router then needs to know where in the network the request is heading to. When you connect to the internet, your ISP gives you a public IP address so you can communicate with the internet. The reason this happens is due to NAT Translations. You can not access your laptop from the internet in this case. This would require to register a port-forward rule in the ISP's router, which they will not do for you. The ISP also uses NAT (to save global IPv4 addresses), the outside IP address of your router comes from your ISP's private subnet. Nowadays it is more and more common that ISPs doesn't even give you a public (globally routable) IP address. If you want all HTTP requests that addressed to your router be served by your laptop behind it, you have to add a port-forward rule in your router's menu to the laptop's IP address and port 80 (standard HTTP port), or port 443 for HTTPS.
If you do a request from outside to your public IP address, you actually adressing your router. If you do a request to a remote server from LAN, from any device, the remote will see that the request originated by your router. Your home router (or most of the wifi routers) you connect to uses NAT to "hide" the subnet behind it and allow your multiple devices communicate on the single global IP address you get from the ISP.
#Access minimserver from outside network how to
I am not familiar with MAC OS so I can not tell you, how to configure the firewall. You can check this using a different machine on the same subnet/different subnet, but still behind your home router. Your OS may have a firewall configured and blocking incoming requests. If VPN is not an option to add to the external users workstation/laptop another alternative would be to add an external DNS record for the URL desired mapping it an assigned web servers public IP address, then on the sonic wall statically translate the public address to the web servers DMZ address.
There may be three blocking hops in the line, starting from your computer:
0 kommentar(er)
