by dobyabywal » 21. August 2015 23:45
When I originally wrote around 8/15/2015 I had changed the Apache "listening" port from 80 to 78 because I got a message that 80 was not available. Apache worked on port 78, but I wanted to see what app was blocking port 80. In the windows Command Prompt I typed: netstat -ano |find /i "listening". I could see Apache on port 78 and MySQL on 3306, but nothing on port 80. Today, 8/21/2015 following your suggestion to keep Apache listening to port 80 I changed it back and now it works. I sure would like to know why why it was blocked days earlier and not now.