iis6不能用了,谁来帮我看看
windows2003系统,vs.net2003,本来都是正常的,有次不知道为什么iis启动的时候说找不到文件,启动失败,我就卸载了重新安装,但是现在vs却不能创建新 的web程序了,新建一个web项目以后就在弹出那个创建新web的窗口后,就没有反应了,程序没有死,也没有提示任何错误,好象是连接http://localhost连接不上,我在iis里浏览网页也打不开,好象凡是要连接到http://localhost的网页都打不开,配置server extensions 2002的页面也打不开,我又重装了几遍iis还是这个问题
谁能帮我看看是怎么回事
问题点数：100、回复次数：29Top
1 楼chNET（有神论者）回复于 2004-09-01 20:52:39 得分 2
又一个没有反应...
try
在cmd里执行:
C:\winnt\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis -iTop
2 楼zldcolin（叶子的离开,是因为风的追求还是树的不挽留?）回复于 2004-09-01 21:01:53 得分 2
iis需要在vs.net安装后安装，如果后安装的话需要运行aspnet_regiis重新注册才可以
C:\winnt\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis -i
Top
3 楼ltlx（）回复于 2004-09-01 21:38:23 得分 0
这个我试过了,还是不行,win2003重装iis以后好象不用再运行这个了吧,我运行了还是不行,还是在出现创建新web时没反应,没有任何错误提示,关键就是连接不上http://localhost,所以才会这样的Top
4 楼ltlx（）回复于 2004-09-01 21:41:25 得分 0
如果我在创建web项目时把Http://localhost改成http://本机的IP地址,就可以了,不知道为什么Top
5 楼kld3000（Never Say Never）回复于 2004-09-01 21:43:30 得分 2
同意书童的
C:\winnt\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis -iTop
6 楼ltlx（）回复于 2004-09-01 22:16:51 得分 0
C:\winnt\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis -i
这个我试了,不行Top
7 楼fzj21408（我才来）回复于 2004-09-01 22:22:54 得分 2
在vs.net自带的命令提示窗口输入：
aspnet_regiis -i
iisresertTop
8 楼chenczx1（昕）回复于 2004-09-01 22:24:49 得分 2
查查日志看看Top
9 楼ltlx（）回复于 2004-09-01 22:32:05 得分 0
凡是前面是http://localhost的本地网页都打不开,但是只要把localhost换成我的本地ip就可以了,郁闷Top
10 楼ltlx（）回复于 2004-09-01 22:34:08 得分 0
在vs中创建新web项目也是,默认是HTTP://localhost,这样就不行,换成HTTP://ip就行了Top
11 楼zhpsam109（JACKY.昊昊）回复于 2004-09-01 22:34:54 得分 2
顶！Top
12 楼lxcc（）回复于 2004-09-01 22:36:19 得分 3
在IIS的默认站点的属性里面改变IP地址为 全部未分配Top
13 楼ltlx（）回复于 2004-09-01 22:50:13 得分 0
在IIS的默认站点的属性里面改变IP地址为 全部未分配
这个我没动过,就是全部未分配
Top
14 楼lxcc（）回复于 2004-09-02 08:04:29 得分 0
http://blog.joycode.com/ceocio/archive/2004/08/02/29330.aspxTop
15 楼luckweb（冰川）回复于 2004-09-02 08:38:20 得分 2
好办法只有一个
重装Top
16 楼zldcolin（叶子的离开,是因为风的追求还是树的不挽留?）回复于 2004-09-02 08:55:12 得分 5
ping localhost
看一下结果Top
17 楼pgwron（情伤无痕）回复于 2004-09-02 08:56:52 得分 2
你看看是不是IIS里面分配了IPTop
18 楼cj777（H3）回复于 2004-09-02 09:00:53 得分 2
重装地IIS，要重装框架就可以用了！！Top
19 楼wangdequan1024（紫夜）回复于 2004-09-02 09:05:56 得分 2
这种情况我也遇到过，也有可能是你机器有病毒的原因。Top
20 楼sykpboy（小憩---每天解决1个问题,顺便升星）回复于 2004-09-02 09:10:06 得分 5
ping localhost
再看你有几块网卡Top
21 楼goody9807（http://goody9807.cnblogs.com）回复于 2004-09-02 09:13:48 得分 0
是不是你的机器的改过名字或IP地址Top
22 楼goody9807（http://goody9807.cnblogs.com）回复于 2004-09-02 09:14:30 得分 5
Dynamic or Static Content Errors
Applications Are Denied Access to Resources
After a clean install, IIS 6.0 runs in worker process isolation mode. Applications running in this mode use the Network Service identity, by default. Network Service is an account with few user rights and therefore provides better security by restricting access to resources on the Web server. If you migrate applications to IIS 6.0 while the server is in worker process isolation mode, and if your applications previously ran in-process (in Inetinfo.exe) as LocalSystem, the applications may fail to access resources because of the restrictions set forth by the Network Service identity. The LocalSystem account has access to almost all resources on the operating system, and therefore creates serious security implications. You should avoid using the LocalSystem account when possible. If it is absolutely necessary to use the LocalSystem account on an application, run that application in a new application pool in its own virtual directory so you can reduce the attack surface by isolating the application. As an alternative, and if your application needs permission to use the Trusted Computing Base (TCB), run the application as a configurable identity and assign the TCB permission to the configurable identity. This alternative, however, still presents a security risk because the TCB permission is very powerful.
For more information, see Configuring Worker Process Identities and IIS and Built-in Accounts.
Requests for Dynamic Content Return 404 Error
In order to take a more proactive stance against malicious users and attackers, IIS is installed in a highly secure and locked mode. By default, IIS serves only static content--meaning features like ASP, ASP.NET, server-side includes, WebDAV publishing, FrontPage® Server Extensions, and Common Gateway Interfaces--do not work unless enabled. If you do not enable this functionality after installing IIS, by default on this denial, IIS returns a generic 404 custom error page to prevent disclosure of configuration information. IIS also writes the 404 error with the substatus code of 2 (404.2) in the W3C Extended log files, by default.
Important You must be a member of the Administrators group on the local computer to perform the following procedure (or procedures), or you must have been delegated the appropriate authority. As a security best practice, log on to your computer using an account that is not in the Administrators group, and then use the Run as command to run IIS Manager as an administrator. From the command prompt, type runas /user:administrative_accountname "mmc %systemroot%\system32\inetsrv\iis.msc".
To enable or disable a Web service extension
In IIS Manager, expand the local computer, and then click Web Service Extensions.
In the details pane, click the Web service extension that you want to enable or disable.
To enable a disabled Web service extension, click Allow.
To disable an enabled Web service extension, click Prohibit.
Click OK.
To enable or disable Web service extensions programmatically, see WebSvcExtRestrictionList.
Requests for Static Files Return 404 Error
For requests to static content, this version of IIS serves requests for files with known file name extensions only, a feature called Known Extensions. If a request is made for a resource whose file name extension is not mapped to a known extension in the MimeMap property, IIS denies the request and logs a 404 error with the substatus code of 3 (404.3) in the W3C Extended log files (by default). To prevent disclosure of configuration information, IIS is configured to return the generic 404 custom error page by default on this denial. You can add or edit the Multipurpose Internet Mail Exchange (MIME) map using IIS Manager. To turn off the Known Extensions feature and allow IIS to serve files with any extension, add the *,application/octet-stream value to the list of MIME maps. If you update the global MIME map, you must wait until the worker process has recycled or restart the World Wide Web Publishing Service (WWW service) before changes take effect. If you update an individual Web site MIME map, the change is reflected instantly.
For more information on adding or editing the MIME map, see Working with MIME Types.
Note Tools like UrlScan can be configured to block the processing of certain file name extensions. Check your UrlScan settings.
Top
23 楼sea026（沸点海岭_____征求“海”字的26种写法）回复于 2004-09-02 09:14:31 得分 60
ping下localhost
ping不通就修改hosts文件
web访问失败
此项目的默认web访问模式设置为文件共享，但无法从路径“D:\inetpub\bweb”打开“http://localhost/bweb”处的项目文件夹，返回的错误是：
无法打开Web项目“bweb”。文件路径“D:\inetpub\bweb”与URL“http://localhost/bweb”不符。这两者需要映射到不同的服务器位置。HTTP错误404：Not Found
A:1。打开IIS管理器。
2。右键点击"Default Web Site"并选择Properties.
3。 点击"Http Header".
4。 点击"MIME Types".
5。 点击“New”。
6。 在Extension中，输入".tmp". (不需要引号）
7。 在MIME Type中，输入 "Temp". (不需要引号）Top
24 楼goody9807（http://goody9807.cnblogs.com）回复于 2004-09-02 09:15:15 得分 0
Clients Cannot Connect to Server
The Windows Server 2003 family provides a software-based firewall to prevent unauthorized connections to your server from remote computers. The Internet Connection Firewall (ICF) is disabled by default. However, if you have enabled the firewall in its default configuration after installing a member of the Windows Server 2003 family and before installing IIS, clients will not be able to connect to your server. The following procedure configures ICF to allow clients to initiate Web and other IIS-related connections to your server.
To configure Internet Connection Firewall for IIS
From the Start menu, click Control Panel.
Double-click Network Connections.
Right-click Local Area Connection, and click Properties.
Click the Advanced tab.
If you do not want to use the ICF, make sure the Protect my computer and network by limiting or preventing access to this computer from the Internet check box isn't available, and click OK.
If you do want to use the ICF, make sure the Protect my computer and network by limiting or preventing access to this computer from the Internet check box is enabled, and click Settings.
On the Services tab, enable a service to which you want to allow access to clients.
In the Service Settings dialog box that appears after enabling a service, do one of the following:
If you are enabling a service on the same computer you are working, the correct computer name is already filled in. Click OK.
If you are enabling a service on a different computer on your network, type the name or IP address of the computer hosting the service you are enabling, and click OK.
Repeat steps 7 and 8 until all the services you want accessible to clients are enabled.
UNC Connections Are Denied Access
The Universal Naming Convention (UNC) authentication method, also called UNC Passthrough authentication, determines the credentials to be used for gaining access to a UNC share on a remote computer. Beginning with IIS 6.0, the UNC authentication looks at the request user and the credentials stored in the UNCUserName and UNCPassword properties of the metabase to determine the credentials to pass through to the computer with the UNC share, in the following way:
If UNCUserName is specified (not empty) and UNCPassword is valid, the metabase user credentials are sent as the user identity for access to the remote share. If UNCUserName is specified (not empty) and UNCPassword is not valid, a 500 Internal Server Error: Invalid Username or Password message is sent to the client.
If UNCUserName is empty, then the credentials of the request user (either an authenticated set of credentials for authenticated requests or IUSR_computername credentials for anonymous requests) are sent as the user identity for access to the remote share.
Note The UNCAuthenticationPassthrough metabase key is no longer used for UNC authentication.
Access Denied to Console Applications in System32 Directory
Requests that use console applications in the Windows System32 directory, such as Cmd.exe, are denied access unless the remote user making the request is an authenticated member of the Administrators group. The denial is the result of special access control lists (ACLs) on all console application programs in the Windows System32 directory to restrict access to only administrators, LocalSystem, interactive users, and services. The ACL restriction does not affect local logon users that should have access, nor does the restriction affect your own custom CGI executable programs.
Client Requests Error-out or Time-out
In IIS 6.0, settings are set to aggressive and secure defaults to minimize attacks due to time-outs and limits that were previously too generous. IIS enforces the following time-outs at the connection level:
Limits on Response Buffering: The default value for the ASPBufferingLimit metabase property is 4 MB. If ASP scripts buffer more than this, they error-out. There was no limit to buffering prior to IIS 6.0.
Limits on posts: The AspMaxRequestEntityAllowed metabase property enforces a maximum ASP post size of 204,800 bytes, with each individual field limited to 100 KB. There was no limit to posts prior to IIS 6.0.
The ServerListenTimeout metabase property no longer exists: ServerListenTimeout has been replaced by the following metabase properties:
ConnectionTimeout: This property specifies the amount of time, in seconds, the server waits before disconnecting an inactive connection.
MinFileBytesPerSec: When IIS responds to a client request, the MinFileBytesPerSec property determines the length of time the client has to receive the entire response. If the client machine takes too long to receive the entire response, the kernel-mode driver, HTTP.sys, terminates the connection according to the time-out value.
HeaderWaitTimeout: When a client connects to the Web server, the client computer is given a time limit to send in all headers for the request (demarked by a final double \r\n). If the complete header set for the request is not received within the time period indicated by HeaderWaitTimeout, HTTP.sys resets the connection. You can configure the value of HeaderWaitTimeout.
Header size limitation: By default, HTTP.sys only accepts requests where the request header is less than 16 KB. This means that if HTTP.sys does not receive the terminating <CRLF><CRLF> sequence within 16 KB, HTTP.sys considers the request malicious and terminates the connection. You can change the header size limitation by adjusting the value in the MaxRequestBytes registry key.
Top
25 楼goody9807（http://goody9807.cnblogs.com）回复于 2004-09-02 09:15:35 得分 0
Miscellaneous Errors
File Requests to UNIX or Linux Server Return Wrong File or Error
If IIS must access files on a UNIX or Linux system, file name case sensitivity can be an issue unless Network File System (NFS) support is enabled in IIS.
UNIX and Linux both support mixed-case file names, and IIS fully supports requesting static files in a case-sensitive manner. An issue arises, however, when IIS makes a subsequent request for a file from its static file cache. Because all file names are converted to uppercase letters in the IIS cache, any request after the first request from the IIS static file cache might fail or return the wrong file.
To remedy this problem, disable the IIS static file cache so that all file requests are issued fresh, thereby retaining correct file name case. The static file cache can be disabled for individual virtual directories on Web sites, or globally for all sites.
Note Changing this setting has no effect on how ASP files and templates are cached.
To disable the static file cache for a particular Web site virtual directory
Edit the metabase and set the MD_VR_NO_CACHE property to 1.
To disable the static file cache for all sites
Edit the registry and add the binary value DisableStaticFileCache=1 to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\InetInfo\Parameters key.
Cannot Locate /Scripts or /Msadc Directory
By default, the /scripts and /msadc directories in IIS 5.0 allowed scripts and executables to run. These directories were removed from IIS 6.0 because, if a malicious user gained access to one of these directories, the user could run a script or executable and potentially gain control of the Web server. If your server configuration requires a directory of this nature, you will need to create the directory and establish the appropriate NTFS permissions.
ISAPI Filter Does Not Show Up as "Loaded" in UI
In an effort to optimize resources in IIS 6.0, an ISAPI filter is not loaded until a request is made to a Web site that requires the ISAPI filter. Until this request is made, IIS Manager does not display the status of the ISAPI filter. Also, if the ISAPI filter requires the SF_NOTIFY_READ_RAW_DATA filter notification, the filter will not load while IIS is running in worker process isolation mode. Review the Application Event Log for events from W3SVC-WP to verify that the filter did not load. To remedy this problem, run IIS in IIS 5.0 isolation mode or contact the vendor of the ISAPI filter for compatibility updates.
Important If the ISAPI filter is restricted by an access control list (ACL) in such a way that the IIS worker process identity cannot load it, requests receive a 503 error. To remedy this, set the ACLs on the ISAPI filter DLL to allow access for the IIS_WPG group.
To configure IIS for IIS 5.0 isolation mode
In IIS Manager, expand the local computer, right-click Web Sites, and then click Properties.
Click the Service tab, select the Run WWW service in IIS 5.0 isolation mode check box, and then click OK.
To start the WWW service, click Yes.
Top
26 楼ltlx（）回复于 2004-09-02 20:16:16 得分 0
可以ping通localhost,我以前改过ip地址和名字,不会与这有关吧Top
27 楼ltlx（）回复于 2004-09-02 20:32:27 得分 0
to goody9807() ( )
我E文不好,能不能告诉我应该怎么做,谢谢了Top
28 楼jierry007（风起云涌）回复于 2004-09-02 20:34:06 得分 2
我也遇见过这个问题，不能访问localhost
只能访问127.0.0.1。弄了很久都没搞定，最后还是重装了，郁闷啊Top
29 楼ltlx（）回复于 2004-09-03 23:15:35 得分 0
问题解决了,多谢各位朋友,
TO sea026(沸点海岭_____征求“海”字的26种写法)
谢谢你给我重要的提示
Top
