Welcome to the most active Linux Forum on the web.
Go Back > Forums > Linux Forums > Linux - Networking
User Name
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.


  Search this Thread
Old 05-26-2007, 09:30 AM   #1
LQ Newbie
Registered: May 2004
Location: Gatineau, QC
Distribution: Ubuntu 6.10
Posts: 25

Rep: Reputation: 15
HTTP Server Response Problems ... Web vs. LAN

Hi all,

Before I added a wireless router (D-Link WBR-1310) to my network, my home LAN setup was configured as such:

(internet) <--> DSL modem <--> Ubuntu 6.04 webserver/gateway/router <--> LAN PCs

After the addition of the wireless router, I removed the Ubuntu server's routing capabilities, and added port-forwarding in the router to the webserver's IP address. The network is currently configured as such:

(internet) <--> DSL modem <--> wireless router ---> LAN PCs and Ubuntu 6.04 webserver

The problem that arose since this change, is that LAN PCs can no longer access the webserver by registered domain name or ISP-assigned IP address (, only by the webserver's LAN IP address. I have multiple domains hosted off the webserver, and accessing any of them from a LAN PC results in a timeout error in the web client browser.

After some digging around, I installed WireShark on the webserver, and captured packet data coming from a LAN PC. The first image below is a 'success' hit on the webserver's IP address. The second image is a 'failure' timeout on one of the registered domain names/ISP-assigned IP address.


My iptables ruleset isn't actively blocking syn/ack/rst flags in packets, so I am unsure what I can do to resolve this problem. I guess I should note too that if I accept all incoming traffic in iptables, the problems listed above are not resolved.

Any ideas?

Best regards,

Last edited by matrixcubed; 05-26-2007 at 09:33 AM.
Old 05-27-2007, 12:39 PM   #2
Senior Member
Registered: Mar 2004
Location: Wales, UK
Distribution: Debian, Ubuntu
Posts: 1,075

Rep: Reputation: 45
Remember that 66. and 10. means that the computers are on separate networks, and the PCs with 10. can only connect to a system with a 66. address if their router does the right thing with the packets. It probably doesn't have a specific route for that address ATM, so uses the DSL modem (which will be the default), rather than passing them to the interface that your server uses (which is what you want).


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Monkey HTTP Daemo (web server) Thulemanden Linux - Server 1 10-12-2006 05:19 PM
Slow web server response for net IP, fast for rpdillon Linux - Networking 1 03-09-2005 09:43 AM
HTTP Web Server Not Saving Changes goldcougar Linux - Newbie 5 06-28-2004 03:30 PM
Can't access Linux web server web pages from LAN client jaydave Linux - Networking 4 03-16-2003 02:38 AM
Error reading WWW server response (HTTP Header)?? cuboctahedron Linux - Newbie 7 02-20-2003 04:10 AM > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 09:30 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration