Apache2Triad Help, Support and Development

[mastertr]

Last 2-3 days, LAN machines (have local ip's, ex:10.1.19.13) can surf my website. But WAN machines (have differen ip and subnet, ex:85.103.27.45) can not.

I tried restart apache. But it doesn't work.
Only if i restart the Server, WAN machines can connect my site.
I also check Firewall and Router, and restart them, but it doesnt work.
What is the problem, you think?

netstat -na outputs;
Before Restart the machine,

TCP 10.1.16.40:80 10.1.16.222:1094 ESTABLISHED
TCP 10.1.16.40:80 10.1.16.254:1546 TIME_WAIT
TCP 10.1.16.40:80 10.1.16.254:1549 TIME_WAIT
TCP 10.1.16.40:80 10.1.17.65:1075 TIME_WAIT
TCP 10.1.16.40:80 10.1.19.38:1208 TIME_WAIT
TCP 10.1.16.40:80 10.1.19.38:1215 TIME_WAIT
TCP 10.1.16.40:80 10.1.19.44:1235 ESTABLISHED
TCP 10.1.16.40:80 10.1.19.44:1242 ESTABLISHED
TCP 10.1.16.40:80 10.1.19.118:1130 ESTABLISHED
TCP 10.1.16.40:80 10.1.20.35:2441 TIME_WAIT
TCP 10.1.16.40:80 10.1.20.35:2444 TIME_WAIT
TCP 10.1.16.40:80 10.1.20.63:1055 TIME_WAIT
TCP 10.1.16.40:80 10.1.20.63:1057 TIME_WAIT
TCP 10.1.16.40:80 10.1.20.122:1215 TIME_WAIT
TCP 10.1.16.40:80 10.1.20.122:1216 TIME_WAIT

After Restart the Machine,
TCP 10.1.16.40:80 10.1.17.0:3307 TIME_WAIT
TCP 10.1.16.40:80 10.1.17.74:1459 ESTABLISHED
TCP 10.1.16.40:80 10.1.17.74:1464 ESTABLISHED
TCP 10.1.16.40:80 10.1.17.74:1466 ESTABLISHED
TCP 10.1.16.40:80 10.1.17.153:3297 FIN_WAIT_2
TCP 10.1.16.40:80 10.1.17.153:3299 FIN_WAIT_2
TCP 10.1.16.40:80 10.1.18.72:1058 FIN_WAIT_2
TCP 10.1.16.40:80 10.1.18.72:1059 FIN_WAIT_2
TCP 10.1.16.40:80 10.1.18.234:1036 ESTABLISHED
TCP 10.1.16.40:80 10.1.19.18:1092 TIME_WAIT
TCP 10.1.16.40:80 10.1.19.18:1094 ESTABLISHED
TCP 10.1.16.40:80 10.1.19.18:1095 ESTABLISHED
TCP 10.1.16.40:80 10.1.19.126:1055 TIME_WAIT
TCP 10.1.16.40:80 10.1.19.126:1058 TIME_WAIT
TCP 10.1.16.40:80 10.1.20.162:2105 TIME_WAIT
TCP 10.1.16.40:80 10.1.20.162:2109 TIME_WAIT
TCP 10.1.16.40:80 85.96.68.58:1212 FIN_WAIT_2
TCP 10.1.16.40:80 85.96.129.109:1957 ESTABLISHED
TCP 10.1.16.40:80 85.96.129.109:2313 ESTABLISHED
TCP 10.1.16.40:80 85.96.175.137:60184 ESTABLISHED
TCP 10.1.16.40:80 85.101.1.251:3545 ESTABLISHED
TCP 10.1.16.40:80 85.101.1.251:3547 ESTABLISHED
TCP 10.1.16.40:80 85.101.151.107:2047 ESTABLISHED
TCP 10.1.16.40:80 85.103.99.115:1433 FIN_WAIT_2
TCP 10.1.16.40:80 85.105.139.63:61259 TIME_WAIT
TCP 10.1.16.40:80 85.105.139.63:61590 TIME_WAIT
TCP 10.1.16.40:80 85.105.139.63:61591 TIME_WAIT
TCP 10.1.16.40:80 85.105.139.63:61785 TIME_WAIT
TCP 10.1.16.40:80 85.105.139.64:60057 TIME_WAIT
TCP 10.1.16.40:80 85.105.139.64:60292 TIME_WAIT
TCP 10.1.16.40:80 85.105.139.64:61846 TIME_WAIT
TCP 10.1.16.40:80 85.105.139.64:61912 TIME_WAIT
TCP 10.1.16.40:80 88.229.113.163:1721 TIME_WAIT
TCP 10.1.16.40:80 88.229.113.163:1727 TIME_WAIT
TCP 10.1.16.40:80 88.229.113.163:1747 ESTABLISHED
TCP 10.1.16.40:80 88.233.50.45:1139 TIME_WAIT
TCP 10.1.16.40:80 88.233.50.45:1159 TIME_WAIT

[Vlad Alexa Mancini]

most likely a filter on packets entering or leaving your lan is the problem
or lack of fowarding if is the case