If output will be something like this: TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 1776 Now go and start shutting down net-type applications and services you may be running. Depending on the application it may be hard to quit, so press Enter a few times, or just close the DOS box. If you see anything else - especially a PURE BLANK SCREEN for more than a few seconds, it means that something is listening. This means that port 80 is not in use already, which means the web server can now be started. What we want to see immediately is ' Could not open connection to the host, on port 80' and a return to the command line. It's a common method to get through firewalls when the normal protocol is blocked.Įnsure the expected web server is not running. There are some other net applications (like P2P apps, chat applications, Media Centres or, of course, other web servers like IIS) that also sometimes grab port 80. It's also possible to configure Apache to use other ports if necessary. If you still have trouble, try closing Skype.

You should now be able to start the WAMP, XAMPP or XAMPPlite server again. This is our problem, so simply uncheck it and save. In Skype options:, there is a checkbox labeled ' Use port 80 and 443 as alternatives for incoming connections'. When installing wampserver the port 80 test determined that Skype might be using it.Īfter closing Skype and the server was able to run and WAMP came online displaying the test pages - working fine. If this test does not show port 80 is 'free' proceed with the settings below. In the xammp or xampplite directory, there is a utility named 'xampp-portcheck.exe' - running it will tell you if port 80 is 'free', or if it is not it may show 'SYSTEM' for example. It appeared to be a problem with using port 80. When Installing XAMPP and XAMPPlite it could not start the Apache HTTP server.

Skype number portability