How to access my "local website" from outside

Shaye87

Shaye87

Shaye87

Associate
Joined
29 Apr 2006
Posts
1,456
Hello there,
I have IIS web server installed on a local machine, with a website running in it, everything is working perfectly except the fact that when i try to access the site with the local ip (http://10.0.0.7) it works from my network computers, but when i try to access the site with my external IP it takes me to my router's control panel :mad: any idea how to solve this? i want people to be able to view the site from outside as well not just from local network computers...
 
Probably also a good idea to change your routers external access port to something other than 80, or disable it unless you really want to be able configure your router from the outside world.
 
well I have forwarded the port 80 TCP to 10.0.0.7, now when i try to access to the site using my external ip address it still takes me to the routers control panel, and if i type in the browser http://10.0.0.7 it tells me that the page can not be found... :|

Not Found

HTTP Error 404. The requested resource is not found.
 
It's secure so long as IIS (and to some extent, the machine running it) is secure.
If you want people to be able to access your web server, it's your best choice.
 
OK I appreciate the help for now, will probably have some more questions soonish :)
seems like it's all good now.
Will secure it as much as I can.
 
real web hosts cost money, and if its only a temporary website or going to be used by a small amount of people, no reason not to host it from your own network.
but yes i do reccommend putting the site in a VM, and then putting that vm on the DMZ on your router. if you don't know enough about this don't worry but it makes it more secure if you are keeping your site up for a long time.
 
the 10.x.x.x is a private address - not accessible outside of the LAN

by port forwarding on the router, you are basically saying any traffic on port 80 should be handled by => this machine. Only the router is publically accessible, so you need to go through that to access something internal
 
UniqueID said:
real web hosts cost money, and if its only a temporary website or going to be used by a small amount of people, no reason not to host it from your own network.
but yes i do reccommend putting the site in a VM, and then putting that vm on the DMZ on your router. if you don't know enough about this don't worry but it makes it more secure if you are keeping your site up for a long time.
Click to expand...

Not that much, if it's ran inside a network then what about machine cost? licences? electricty? admin work? e.t.c. You can buy good hosting for less than £20 a year. (TSOHOST) they brilliant.
[Depends what work though needs done to it.]
 
Shaye87
Port forwarding is what you need to do.
80 tcp to the ip of the inside host.

Now as to is it safe, you will have opened up your server to port 80 traffic from the internet.
You will get attacks from every man and his dog as all internet hosts do.
Make sure your patched up to date and keep an eye on your server.

If you want internet access to your server for yourself only then put access restrictions on the server.
You could have IP restrctions and just allow the public IP's of your workplace for example.
Or you could password protect the site.

Really though if security is troubling you it may be best not to add the inbound port forwarding in the first place.

A lot of ISPs dont allow hosting officially, even though they dont block the ports and you will probably be in breach of the Terms and Conditions.

BTW
You have to test the port forwarding from outside your network.
Trying to http your own publc IP from inside your network won't
work.
You will just get your routers admin page.
Only packets sourced from the WAN will be redirected to your Webserver.
 
You must log in or register to reply here.
Back
Top Bottom