How to link an Intranet website to my Internet accessible website - http

I've configured a dinamic DNS with my router and linked my external IP to no-ip.com, so I have a link to my intranet from everywhere. Now I have done a simple port forwarding from the port 80 to 8080 to my laptop, which is hosting a http-server with node.
Everything works fine but now I want to create a link to my router configuration, that I can access with the IP 192.168.1.1 from my laptop, directly from my website, hosted on my laptop. Can I do that in some way?
Thank you.

You can achieve this by writing a small code on a web server, which makes a call to the router config url and shows the output.

Related

IIS - Website at port 8080 can be accessed using localhost but not with external IP address

I have 3 websites running on my server, all of them on different ports. One is on port 80 and it works fine, the other one is on port 88 and it also works fine. Today I deployed a third one on port 8080, opened the port in Firewall.
I can access it with http://localhost:8080/, with 127.0.0.1:8080 and with it's internal IP address. I can't access it using the external IP address for some reason. I tried accessing it locally using the external IP address and I tried from another computer.
It is worth noting that the website on port 8080 is almost identical to the one on port 80.
Initially I thought it was a firewall issue but I disabled the firewall and tried again and I get the same result (The website took too long to respond).
I am using Windows 10 on the server.
Any ideas as to why this is happening?
I figured out the answer. I am using an EC2 instance from Amazon Web Services for a server. I forgot to go into the console in AWS and open the port there too. I did that and now it's working as it should.
There could be couple of reasons.
Cloud Provider(AWS) Specific
Check your subnet's ACL rules. Both ingress and egress
Check the security group attached to the instance. It should allow ingress
on that port/protocol
Windows Server Firewall: All windows servers and desktops have firewall running which blocks any non-standard traffic. Make sure to add a custom rule to allow the traffic that you want to allow. I found this https://computingforgeeks.com/how-to-open-a-port-in-windows-server-firewall/ link helpful

Making websites hosted in localhost "port" available to all on network

I have a website hosted in IIS in my local PC.
I can access to my IIS from other computers in the network by typing in http://my_lan_IP. However, when I try to get access to a specific port (http://my_lan_IP:8888) in my local PC, it says the "The site can't be reached."
I disabled all my firewalls and even tried allowing the specific port through Windows Firewall, but it didn't work. Viewing my IIS hosted site on other machines on my network
Thanks so much for your help :)
FYI: I am using Windows 10. My goal is to connect to the locally hosted ASP.NET website from other machines on the network.
Your web server needs to be configured to serve HTTP on port 8888 "for that particular website", in order for a client to connect to that port.
By default, your website is served on port 80, which is omitted from normal addresses. All http web addresses, if not specifying a port, is actually running on port 80, or 8080.
Your windows firewall will not effect local connections you make to your own pc. Get it working on your own machine, and then worry about firewalls that block connections from other machines on the network.
I was able to solve the issue by configuring a host header for a website. Thank you all for your help :)
https://technet.microsoft.com/en-us/library/cc753195(v=ws.10).aspx

Can't get my IIS website online

I just tried to publish my website via IIS.
I forwarded the right ports to my LAN and it successfully connects to the LAN, but can't connect the internet.
When using 192.168.1.20:8080 (which is my local IP address), it connects to the website, but when using my external IP address it doesn't work.
What do I do wrong?
Thanks!
It likely has something to do with the port being auto-blocked by your Windows firewall or :80 not being routed to :8080 in your router.
I had this issue too, Windows Firewall's default was to block the :80 port. I just had to go in and make an exception.
-first of all you should have a static IP address.
-second make sure you add the make sure you add that IP address to your Network (NIC) card Interface and I hope it will work fine.
Check This Please or this topics

WAMP - localhost can share to someone

I'm not really sure if this is possible, I have a WordPress theme installed and customized using localhost + wamp. Can my colleague view my site w/o uploading it to the server? I mean, can i share a IP address so that he can view it too?
You are looking at port forwarding. You will need to setup a port forwarding rule for Port 80 to forward to the localhost and port that is running your app locally. This way when your friend enters your ipaddress the request will be forwarded to your localhost and he will be able to view the page. Here is an article that discuss Port Forwarding.

Creating a Home Server - Port Forwarding Issue

So I'm trying to setup my home server that is accessible from the Internet. I have created my Web site in ASP and configured my IIS. It works great on my local machine AND other computers on the local network can access it. I want to make it online, so that it can be accessed from elsewhere. I created an account on DynDns, and configured it to redirect the requests to my Internet IP. Then, I configured my router to forward all the incoming requests on port 80 to my local IP address, on which my Web site runs. However, when I go to my DynDns address, it redirects me to my router's home page instead. I have disabled my firewall (I know, not a good idea, it's just for testing purposes) but still no success. Does anyone have any idea what could be going wrong? I have a SMCWBR14S-N4 if that helps.
I've heard of some routers that have reserved port 80 for there configuration pages. I think the general work around there is to run your webserver on a non-standard port like 8080, but I don't have a whole lot of experience with this, so it could be something else entirely. :)
Update: For any future readers, always remember to test your external address and port forwarding on a computer outside of the network the server is on.

Resources