I'm somewhat familiar with IIS, but I've never run across this problem.
Setup is standard: Net -> router -> computer with IIS
First, I every time I add a file and want to access it through the browser, I have to reset the security permissions to "public website", and cannot access the file otherwise.
Second (and more serious), I can't access my website through an external IP. If I type in localhost or the internal LAN IP (192.168.x.x) it works fine, but if I try to use my external IP, it doesn't work. Of course, I opened up the relevant ports on the router and tested that by switching utorrent's port and testing with an external port scanner. Its definitely not a port forwarding problem, but IIS not accepting external IP requests for some reason.
Any help on either of the two issues?
Edit:
Also, when I go to the website's properties in IIS, then go to Directory Security, the "IP Address and Domain Name restritions" button is disabled. After some searching, it seems that this is by design in XP Pro's IIS (5.1). Is there some other limitation in XP Pro's IIS where it can't serve content to external sites at all?
Setup is standard: Net -> router -> computer with IIS
First, I every time I add a file and want to access it through the browser, I have to reset the security permissions to "public website", and cannot access the file otherwise.
Second (and more serious), I can't access my website through an external IP. If I type in localhost or the internal LAN IP (192.168.x.x) it works fine, but if I try to use my external IP, it doesn't work. Of course, I opened up the relevant ports on the router and tested that by switching utorrent's port and testing with an external port scanner. Its definitely not a port forwarding problem, but IIS not accepting external IP requests for some reason.
Any help on either of the two issues?
Edit:
Also, when I go to the website's properties in IIS, then go to Directory Security, the "IP Address and Domain Name restritions" button is disabled. After some searching, it seems that this is by design in XP Pro's IIS (5.1). Is there some other limitation in XP Pro's IIS where it can't serve content to external sites at all?
