Arch Linux

bjackman

Member

Registered: 2011-12-27

Posts: 32

Can't connect to HTTP server over LAN (works from over the internet)

Hi!

I've just recently installed Arch for the first time and I'm loving the k.i.s.s style. I can't wait to be completely free of Ubuntu. I've just been putting together a full setup as an educational exercise mostly. So firstly, hello and thanks for this community.

After hours of fun, I've finally come up against a problem the excellent wiki doesn't have an answer for:

This computer (the arch computer, the server) is at 192.168.1.105 on the LAN. I can successfully ping that address from another computer.
My router is set to forward port 80 connections  to 192.168.1.105, so I can connect by sending a request to my external IP - from a computer on my LAN and from a remote computer.
Finally, from this computer I can get my pages by requesting them from 192.168.1.105 (as well as the loopback address/localhost).
I just can't get them by requesting them from 192.168.1.105 from another computer on the LAN (this matters because it means my server only works with a WAN connection: a request from my laptop, for example, needs to go to the ISP and back)

So my router is successfully sending requests to the server, so presumably requests are getting there from my other computers, but httpd is refusing to serve them. I suspect this is a trivial matter, but I don't know where to start! Could anyone help?

Thanks.

zenlord

Member

From: Belgium

Registered: 2006-05-24

Posts: 1,221

Website

Re: Can't connect to HTTP server over LAN (works from over the internet)

Looks like you got completely the opposite problem of https://bbs.archlinux.org/viewtopic.php?id=132266.

Are you using two NIC's? Might there be a configuration switch where you make the server listen for traffic on one NIC only? Our server has such a setting in the iptables-script...

bjackman

Member

Registered: 2011-12-27

Posts: 32

Re: Can't connect to HTTP server over LAN (works from over the internet)

Are you using two NIC's? Might there be a configuration switch where you make the server listen for traffic on one NIC only? Our server has such a setting in the iptables-script...

That's a good idea but I don't think it's the cause: the "server" (it's actually just an old PC) is only connected via WiFi: it's just the most basic home setup. I'm still working on this but now I've got a new problem: I can't start httpd at all! Seems to be a permissions issue.. I'll get back in here when I've got the thing running. Thanks!