Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
 Topic: Win7-Apache 2.4.6 win32 - localhost works - remote fails |
|
| Author |
|
macirish
Joined: 22 Nov 2013
Posts: 4
Location: USA, Pendleton
|
 Posted: Fri 22 Nov '13 17:13 Post subject: Win7-Apache 2.4.6 win32 - localhost works - remote fails |
 |
|
My customer wants a Windows system - but I'm rusty at best in Windows.
I downloaded VC11 x86 Thread Safe (2013-Nov-13 20:57:44), unpacked it, moved it to it's own directory, edited httpd.conf (no auto installation) and confirmed it was working (localhost/index.html)
I added PHP and ran a PHP info - a little trouble getting the php.ini found.
Apache seems to work fine on the local system - either localhost/index.html or nn.nn.nn.nn/
But remote browsers timeout when attempting to connect.
1. I've opened command as administrator and run httpd.exe directly
2. I've installed httpd.exe as a service, opened it's properties window and started it from there
3. Changed the listen port to 8080
4. netstat sees the remote browser with a waiting connection - and the local service
5. The Windows system is on my Mac network (same systems where the remote browser is) and I have transferred megabytes of files between the two systems.
----
In Component Services - the Apache2.4 service shows Log On As 'Local Service' - I'm guessing it should show as 'Network Service.
I tried changing this - used the local user login - restarted the service. I didn't see any way to change it to 'Network Service'. Perhaps this is the problem?
ODDLY - the remote browser worked briefly - then failed with the same 'time out'.
I'm guessing this is something simple that I don't understand about Windows - (then again, since I don't understand much about Windows, it could be complicated too).
Thank you.
KenMc |
|
| Back to top |
|
daniel1975
Joined: 05 Feb 2006
Posts: 24
Location: RO, Bucharest
|
| Posted: Fri 22 Nov '13 17:22 Post subject: Re: Win7-Apache 2.4.6 win32 - localhost works - remote fails |
|
|
P
You might consider checking the same with turning off Windows Firewall (or other similar app from other vendor), and if that's to blame, you need to open the relevant ports to be used outside. |
|
| Back to top |
|
macirish
Joined: 22 Nov 2013
Posts: 4
Location: USA, Pendleton
|
| Posted: Fri 22 Nov '13 17:38 Post subject: |
|
|
Turned off Windows Firewall. No joy.
Restarted system - Apache service show's it is running (under my account) - but remote browsers still time out.
Netstat still shows the remote request with a TIME_WAIT status. |
|
| Back to top |
|
glsmith
Moderator
Joined: 16 Oct 2007
Posts: 2268
Location: Sun Diego, USA
|
| Posted: Fri 22 Nov '13 22:52 Post subject: |
|
|
| Quote: | | 1. I've opened command as administrator and run httpd.exe directly |
Step one should have popped up a warning and a choice for allowing the app to connect to the internet.
Turn the firewall back on and while you're there, choose "allow program through windows firewall" then use the add program button, browse to the httpd.exe file, select it and OK your way back to the start.
restart Apache and it should be able to be connected to by the remote computer's browser. |
|
| Back to top |
|
macirish
Joined: 22 Nov 2013
Posts: 4
Location: USA, Pendleton
|
| Posted: Sat 23 Nov '13 14:16 Post subject: |
|
|
Thank You! Problem solved.
Turned the firewall back on.
The 'Allow Program' selection is available in Control Panel - System Security - but not in the window I was using to turn the firewall off/on. That took a few minutes to sort out.
There were 3 instances of Apache2.4 in the 'Allow Program' selection - checked all 3.
Restarted Apache and remote browser worked fine.
(The next problem was an AJAX failure - I was certain it was the same kind of problem - traced it through with Firebug and discovered that I'd hard coded an IP from the development system...duh...)
Thanks again.
KenMc |
|
| Back to top |
|
|
|
|
|
|
