Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
Hi,
I just setup a Debian box, and I don't have any experience with setting up servers. So, I use apt to install apache2, and I also have a domain name from DynDNS point to my IP. My internet is cable and all my computers are behind a D-Link Router. I can see the Apache Welcome page on my other computer, but people outside of LAN can't see it. I just want to start with the basic of setting up apache, then later php, mysql.....and other services. What configurations I have to do? Any help will be appreciated, thanks in advance.
You will need to login to your router and configure it to forward port 80 to the internal IP of your server. Any remote users should then be able to connect via your public IP address.
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
Just to make sure disable the firewall completely on the server to rule it out and see if you can see the web server from outside. Since it can be seen from other computers I doubt that this is it. But it does not hurt to rule it out.
Also have you tried typing in your external IP instead of the domain name. http://x.x.x.x of your external routers IP.
Posiable your provider has block use of common ports. Configure the router to port forward an outside port of say 8888 to internal port 80 of machine.
Not sure how dyndns works but maybe it can be configured so when you type in your domain name that it points to your External IP and say port 8888 if cable provider blocks common ports.
Not sure how dyndns works but maybe it can be configured so when you type in your domain name that it points to your External IP and say port 8888 if cable provider blocks common ports.
No, dyndns is just a regular dns, but you update it often. People will have to access your site at http://www.you.dyndns.org:8888, if you decide to use port 8888. Be aware that this can cause proxy problems.
Note: Are you trying to contact your external ip address from your own network? On many rouers, this won't work.
I can see the apache welcome page from a browser on a machince within the lan, but I want people outside my network to see the web page, too.
I know. What I am asking is if you are performing the tests from your own LAN, or from some other place.
Quote:
I don't know how to do that, do you have any experience doing it with D-Link 604 Router?
On the di-624, you must create a virtual server and set 'public port' to 8888 and 'private port' to 80
Before doing this, check that your ISP is really blocking port 80.
I know. What I am asking is if you are performing the tests from your own LAN, or from some other place.
From my own LAN
Quote:
On the di-624, you must create a virtual server and set 'public port' to 8888 and 'private port' to 80
Before doing this, check that your ISP is really blocking port 80.
I have a DI-604, but it should not be a big difference. Thanks.
On many/most routers, if you are on the lan side and you attempt to access the router by its public ip, it will fail. Ask a friend to try to connect to your web site in order to know if you really have a problem.
Quote:
I have a DI-604, but it should not be a big difference. Thanks.
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
Doing a little research on dyndns and wondered if you went through thier tech and faq questions. Go over these questions from thier site and see if any of these are the problem. http://www.dyndns.com/support/kb/arc...my_server.html
Originally posted by Brian1 Doing a little research on dyndns and wondered if you went through thier tech and faq questions. Go over these questions from thier site and see if any of these are the problem. http://www.dyndns.com/support/kb/arc...my_server.html
Brian1
Thanks, I read through it and several other articles in it, and I figured that my ISP blocked the port 80. So I tried the web hop service they have, and now it works fine
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.