Hi David Your problem is being caused by your router. The IP addresses the router is assigning you are in what is called a private range of IP addresses. These are IP addresses which are only ever used on private networks. When a packet of information comes into your router it looks to see which private IP address to forward it on to. This process is known as Network Address Translation. The problem you've got is that when a request comes into your router IP address it's stopping dead there. What you need to do is tell your router to forward all web server requests to your Win2k server. The type of service that is being requested is identified by the port number that it's requesting. So say your router external IP address is 184.108.40.2067, when a request for a webpage comes into it it's actually going to 220.127.116.117:80. So what you need to do is tell the router to forward all requests on port80 to 192.168.1.1:80, this process is known as port forwarding. If you look in your router manual you should be able to find out whether it can handle it or not. Something to be very very aware of, IIS servers are very insecure out of the box. If you're going to make your publically available you should be aware of the risks involved, and the tools that are available to help you minimise them (check the Microsoft site for their lockdown tool and security updates) HTH Norman -----Original Message----- From: thelist-admin at lists.evolt.org [mailto:thelist-admin at lists.evolt.org]On Behalf Of David Bindel Sent: 18 May 2002 16:00 To: thelist at lists.evolt.org Subject: [thelist] Configuring a IIS behind a router Hi all, My name is David Bindel and I am a 15 year old web developer (working with XML, CSS, ASP, and learning PHP and Perl). I am running Windows 2000 Server and I'm trying to set IIS up so I can test websites I make from other locations. Let me explain my situation: * We have Road Runner Cable Internet * My younger brother lives in the same room with his computer also * Because of that, we have to use a router to split the cable connection to use it on both of our computers * The router assigns us "fake" (example: 192.168.1.xxx) IP addresses to separate the computers i guess Now, our Internet access works perfectly fine, but when it comes to setting up IIS as a server, I'm not really sure what to do. My problem (I think) is that the router is assigning me its "fake" generic IP address and because of that, people outside of the network my brother and I have set up will not be able to get to the server... it stops at the router I guess. Here are the symptoms: * I CAN access the website by typing in the fake IP address the router assigns me * I CAN access the website by going to http://localhost/ * I CAN'T access the website by going to my real Road Runner IP address Has anyone run into this problem before, and do you know how I can correct this so I can serve websites? Thanks in advance, David Bindel (dbindel at austin.rr.com) -- For unsubscribe and other options, including the Tip Harvester and archive of thelist go to: http://lists.evolt.org Workers of the Web, evolt !