This has bothered me from XP to now, win7 Ult on my home network. Does IIS restrict my web developed pages to my local/home network? Yet again, when I publish to my localhost, is the site (my files) accessible to external viewing/browsing? If yes, how do I restrict browsing to my other network box/stop 'external to my net' browsing? We all have the ubiquitous 192.168.n.n IP for internal networking (or one of the other free for all IP sets) so can I use a deny all (except) IP range? Detailed techy (real word, ¡honest! grin) explanation(s) welcomed and hoped for. Yes, I am a webmaster and the SA for IIS on our 20 + web servers. I have looked in MS, technet, msdn, forums, WOPR (Woody's forums), and other Q&A developer sites. I found this site and am again asking for some valid information and answers.
TIA JL
-
Unless you've gone out of your way to enable it, your pages won't be accessible from the internet. You'd have to setup some sort of port-forwarding through your firewall to even allow people to see the machine. Most ISPs won't even allow home-users to run publicly-accessible servers.
If you want to be extra-super-duper sure, see this article for IP-based access restrictions: http://support.microsoft.com/kb/324066
me r jl : Thank you for your quick response. I will access the link now.me r jl : Thanks. This link states what I do all day at work. I was hoping for a home network specific deny all (except) solution. But, I do like your 'Most ISPs ...'. I do feel more secure about my developments now.bemace : Why would securing a server at home be any different? Allow the IPs you want and block the rest.From bemace
0 comments:
Post a Comment