![]() You may need to forward other ports: 80 are common workarounds for such blocking, for http and https. Note that some ISP's block using the first 1024 ports so folks cannot set up public websites on residential accounts. So, set up a Port Forwarding rule to forward your desired ports to your Virtualbox host. You'd have to tell the router to forward port 80 to 192.168.0.10. (There could be a possibility something on the internet will turn the request around and send it back to you, but I have not had this happen reliably.)Īnd, even if you do get the request returned to you, you have to open a port for the request in your network router, using the Port Forwarding section in the router. So your router would say "34.56.123.87 is therefore out on the internet, let me send it out the gateway." And it disappears out into the internet. You can access the web service from another LAN computer by 192.168.0.10:80 or PCnetworkname:80. You can access the web service from the PC itself by localhost:80. ![]() ![]() Your network router is getting internet and is given a public IP address 34.56.123.87, and you've set up your no-ip DUC to give you a dynamic DNS name "". You have a web server running on the PC, and you've opened port 80 in the PC OS's firewall. I have found that you have to be outside your local network, on the internet, to try accessing services running inside your local network using the public IP address or DNS name.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |