apache装配后运行正常,为什么在此服务下网页打不开
apache安装后运行正常,为什么在此服务下网页打不开
先把我的配置和apache的错误分析说下,最后就是请各位看下我遗漏了什么地方了,帮我解决这个问题
1:配置:win2003+mysql+php+iis+apache 机器上还安装了.net3.5+mssql
杀毒的软件只有卡巴(其实我已经停了,并退出了)
apache的端口配置:Listen 80 iis的80端口一直是停用的
目录:DocumentRoot "d:/wamp/www/"
几个月前我是手动配置的有点问题,也出现了网页打不开,网页一直是在加载中,后来我把360safe给卸了,讯雷也给卸了,卡巴给停了,就可以了
现在是停了卸了也不行,就换了wampserver2.0,但是还是不行,所以我这里就判断问题是出在apache上了,如不对,请指出
2:继续分析
netstat -ano|findstr 80
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 4768
TCP 127.0.0.1:80 127.0.0.1:2193 ESTABLISHED 4768
TCP 127.0.0.1:2193 127.0.0.1:80 ESTABLISHED 5172
TCP 127.0.0.1:30523 0.0.0.0:0 LISTENING 1804
tasklist /fi "PID eq 4768"
映像名称 PID 会话名 会话# 内存使用
========================= ======== ================ =========== ============
httpd.exe 4768 Console 0 14,796 K
到这里应该是没有错的,我看了任务管理器里的进程是对的,有两个httpd.exe进程,这个是apache特有的两个进程,没有问题的
到了这里我怎的找不出是什么问题了,请各位帮忙,谢谢
------解决方案--------------------
iis 和 Apache 能同时使用吗?
应该是顿口被占了
把Apache端口改成82试试
------解决方案--------------------
打不开的原因,好像就是你的服务器被战用了,其它的服务器的端口也是80的。你需要做的是将其它一切有可能的服务器关掉。然后重启。
------解决方案--------------------
IIS和Apached都是服务器哦!!!
------解决方案--------------------
IIS和Apache共存是没有问题的,只要其中的应用端口不冲突。
迅雷开着的话有可能出这种问题,现在都卸了应该不是迅雷的问题;系统自带的防火墙关闭没有?
可以给Apache设置其他的端口试试看。
实在不行,就装个2008Server,装个PHP的插件IIS就可以直接运行PHP了,既然在Windows下,就用IIS吧。
------解决方案--------------------
囧,就这样放弃了。
------解决方案--------------------

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











To set up a CGI directory in Apache, you need to perform the following steps: Create a CGI directory such as "cgi-bin", and grant Apache write permissions. Add the "ScriptAlias" directive block in the Apache configuration file to map the CGI directory to the "/cgi-bin" URL. Restart Apache.

There are 3 ways to view the version on the Apache server: via the command line (apachectl -v or apache2ctl -v), check the server status page (http://<server IP or domain name>/server-status), or view the Apache configuration file (ServerVersion: Apache/<version number>).

Apache connects to a database requires the following steps: Install the database driver. Configure the web.xml file to create a connection pool. Create a JDBC data source and specify the connection settings. Use the JDBC API to access the database from Java code, including getting connections, creating statements, binding parameters, executing queries or updates, and processing results.

When the Apache 80 port is occupied, the solution is as follows: find out the process that occupies the port and close it. Check the firewall settings to make sure Apache is not blocked. If the above method does not work, please reconfigure Apache to use a different port. Restart the Apache service.

How to view the Apache version? Start the Apache server: Use sudo service apache2 start to start the server. View version number: Use one of the following methods to view version: Command line: Run the apache2 -v command. Server Status Page: Access the default port of the Apache server (usually 80) in a web browser, and the version information is displayed at the bottom of the page.

How to configure Zend in Apache? The steps to configure Zend Framework in an Apache Web Server are as follows: Install Zend Framework and extract it into the Web Server directory. Create a .htaccess file. Create the Zend application directory and add the index.php file. Configure the Zend application (application.ini). Restart the Apache Web server.

Apache cannot start because the following reasons may be: Configuration file syntax error. Conflict with other application ports. Permissions issue. Out of memory. Process deadlock. Daemon failure. SELinux permissions issues. Firewall problem. Software conflict.

To delete an extra ServerName directive from Apache, you can take the following steps: Identify and delete the extra ServerName directive. Restart Apache to make the changes take effect. Check the configuration file to verify changes. Test the server to make sure the problem is resolved.
