GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
This is a windows computer, but I believe that you guys can help me:
So I'm trying to run a webserver off of my computer. I'm running Windows XP, Apache2, have a SBC DSL connection, WRT54G Linksys Router, and a 2wire 1000sw DSL modem.
When I installed Apache I configured it for "localhost" and installed it to "c:/apache2" It is installed as a service. I can get the default screen at http://localhost but when I try to access it from my ip at http://*.30.23.214/ it does not show up. I can also get it at the internal network ip (192.168.1.10) of my computer and 172.16.1.34 (wtf is that?)
When I connect my computer directly to the modem, I can acces at my ip (http://*.30.23.214/)
I think this is a limitation of the router. I have the same problem with my D-Link router. Had the same problem with a Netgear. I am forwarding ports to hosts on the private subnet. If I try to browse to the internet IP, it will not connect, but connecting to the private IP works. if you are coming in from the WAN port on the router (as you are if you are connected to the modem), it works, but if you are coming in from the private side of the router, it cannot port forward back to the same private network. If you try from a different computer on the Internet, will it connect? I'm guesing that it will work.
That is the IP that your router is shooting to you via DHCP. I am running a static IP too (not for a webserver, though) and I have turned off DHCP on the router. Try that, for starters.
shubb is right, I believe. Its not a router shortcoming. Its a NAT weakness. You can't access a public webserver from within the network the same way. I'm not sure if you'll be able to change that. So, if you're plannig on testing the "view" from outside your little lan, you may have to make friends with someone who is willing to help you test that. Good luck. I hope we're proved wrong, though.
192.168.x.x, 172.x.x.x, and 10.x.x.x are the "private" IP ranges that we can use on a network. These aren't used on the internet. That way we don't run out of IPs so quickly, as we can all use the same internal ones if we want.
According to the pics, your gateway is 172.16.0.1 and you have set your puter to 192.168.1.10 (same as mine). Change one to match the other. My Linksys befsr41 has an IP of 192.168.1.1, for example.
Originally posted by vectordrake According to the pics, your gateway is 172.16.0.1 and you have set your puter to 192.168.1.10 (same as mine). Change one to match the other. My Linksys befsr41 has an IP of 192.168.1.1, for example.
172.16.0.1 Takes me to the config screen for my modem.
192.168.1.1 Takes me to the config screen for my router.
172.16.1.34 is the dymanic IP assigned by the DHCP server on your router. If you reboot your puter, you won't have that IP any more. You have to have a static IP anyways when you have a webserver behind NAT or you won't be able to guarantee any uptime for the server. You have the right idea, but the IPs aren't meshing yet.
Originally posted by vectordrake 172.16.1.34 is the dymanic IP assigned by the DHCP server on your router. If you reboot your puter, you won't have that IP any more. You have to have a static IP anyways when you have a webserver behind NAT or you won't be able to guarantee any uptime for the server. You have the right idea, but the IPs aren't meshing yet.
I'm taking 192.168.1.10 from my router which is located at 192.168.1.1 which is being assigned 172.16.1.34 by my modem at 172.16.0.1 which is being served 209.30.23.214 by SBC
Overall I now believe that my modem is acting as a router and screwing me over because its so damn confusing.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
