|
So I have my website setup on my server as of now, and I have checked my public IP address and entered that into the website properties in IIS. My network consists of a cable router from the ISP connected to a Linksys private router. The Linksys router is then hooked up to the server. The files for the website are on the server already, and they are pointed to the right file. When I try to view the website in a browser, I get prompted to enter the login information to the Linksys router. When I do this, I then get an error page saying that my website is not available or something of the sort. I am soon getting a dedicated T1 with a router specifically for this. How come the website will not come up? Even if it did come up, how would I make sure the website users would not have to enter the login information? Would I have to structure the physical network differently? I am assuming I want the server placed in between the pop router and the the private network router correct?
I am trying to setup my web server. I am using IIS for Windows Sever 2003.?
The main problem here seems to be that the port your are attempting to access from outside of the network is the same as the router's default remote admin port. You have a few options to fix this.
1. Disable the router's remote administration feature.
2. Change the aforementioned port.
3. Use a different port to access your site remotely (i'm assuming it's currently set to 80?)
|