up vote 1 down vote favorite
1
share [g+] share [fb]

I have public IP 89.103.xxx.yyy, then router and home network with 192.168.1.zz My router is set to portforward every 8056 on ip adress 192.168.1.5 (my PC), where apache is running. Apache listen is set to:

Listen 127.0.0.1:80
Listen 192.168.1.5:8056

When i try:

Listen 89.103.xxx.yyy:8056

I get message "unexpected end of apache" (I'm using easyphp for windows).

Added: When i try to access 89.103.xxx.yyy via browser, it's prompting router request for authorization to access router web-settings. And when i try 89.103.xxx.yyy:8056, browser says that connection timed out =(

link|improve this question
Check firewall settings as well. – MrStatic Mar 14 '10 at 19:13
My only windows fireawall is off =) – Filip Mar 14 '10 at 19:15
AV software will also have firewall... – marcusw Mar 15 '10 at 0:05
feedback

2 Answers

up vote 4 down vote accepted

You'll need to configure apache to listen on 192.168.1.5:80 (on 192.168.1.5, the requests will arrive on port 80. not 8056). Also make sure that on the router port 8056 is forwarded to 192.168.1.5 port 80

link|improve this answer
I dont have settings in my router webconfigurator to portforward on specified port =( .. just: Local IP Address - Protocol - Port Range – Filip Mar 14 '10 at 19:16
What's you router make and model ? You can also try to use wireshark on your windows computer to make sure on which port the HTTP requests are received. – Dominik Mar 14 '10 at 19:24
I have ZCOMAX WA 2204 and i have uPNP enabled. There are "Ping Access on WAN" and "Web Server Access on WAN" options as well, enabled too. – Filip Mar 14 '10 at 19:31
I set 192.168.1.5 with my apache to DMZ and still nothing =( – Filip Mar 14 '10 at 20:00
Access to 192.168.1.5:8056 from my notebook that is in same "home" network is working just fine even when listen is set to "Listen 192.168.1.5:8056", ping to my 89.103.xxx.yyy is forking fine and port 8056 on my 89.103.xxx.yyy is opened assuming info from ping.eu – Filip Mar 14 '10 at 20:25
feedback
up vote 0 down vote

Turn off the "Web Server Access on WAN" option.

change the port forward "range" to just be 80.

change apache back to "Listen 192.168.1.5:80"

link|improve this answer
This may not work as many ISPs block incoming port 80... – marcusw Mar 15 '10 at 0:52
quote the OP "Added: When i try to access 89.103.xxx.yyy via browser, it's prompting router request for authorization to access router web-settings. " – user23307 Mar 15 '10 at 2:06
feedback

Your Answer

 
or
required, but never shown

Not the answer you're looking for? Browse other questions tagged or ask your own question.