Using iis windows 2008

For this reason, we recommend using Windows authentication for intranet environments, and using Basic authentication over SSL for internet environments. If you have not enabled a suitable authentication method Windows authentication, Basic authentication, or Digest authentication , you will receive the following error dialog when you connect.

To resolve this, enable one of the authentication methods mentioned above. After you have opened a Web site or application in Visual Studio, you can take advantage of Visual Studio debugging features to test it. In doing so, you have the following options:. F5 debugging provides the most convenient way to debug your Web application with Visual Studio.

To use it, do the following:. In order to successfully debug a local IIS Web application, you must meet the following requirements:. Be logged on as a user that has Administrative privileges on the local computer Either the built-in Administrator account, or an account that is a member of the built-in Administrators group.

Start Visual Studio in Administrator mode by right-clicking the Visual Studio icon in the Start menu and selecting Run as administrator.

If you have opened an ASP. NET Development Server to host your application. In this option, IIS is not involved, and you are not required to be an Administrator to debug your application. However, when using the ASP. NET Development Server, you do not have the full range of features and services that IIS environment provides, which may make your application behave differently from when it is deployed on IIS. This includes the following:. The process is similar to what was described earlier for debugging local IIS applications, but requires additional configuration to enable remote debugging to take place.

In order to successfully debug a remote application, you must also meet the following requirements:. Install the Remote Debugging components on the server machine. Run the Remote Debugging monitor msvsmon. See further notes about how to do this properly. When you run msvsmon. If you want to configure the firewall manually or to see which ports are opened, see How to: Manually Configure the Windows Vista Firewall for Remote Debugging.

If you are using a Web application project and publishing to a remote IIS server, or if you have opened the remote Web site project using the File System or FTP Site options, you must configure the Visual Studio project start options to enable debugging. To do this for a Web site project, right-click on the Web site project node, and then chose Start Options.

For a Web application project, right-click on the project node, chose Properties , and the click the Web tab. Configure permissions to allow debugging to take place. How you run the Remote Debugging monitor msvsmon. Create an account with the same username and password on both the Visual Studio client computer and the remote server computer. This account must have Administrative rights on the remote server computer. If you are using Windows authentication in your application, this account must be the built-in Administrator account.

This means that the built-in Administrator account must have the same password on both computers. Log on to the remote server computer using the account created in Step 1, and run the Visual Studio Remote Debugger from the Start menu by right-clicking it, and choosing Run as administrator.

Do not use the RunAs. If you use this option, you must configure the Remote Debugging monitor to log on using the account created in Step 1. Log on to the Visual Studio client computer with the account created in step 1. Run Visual Studio by right-clicking its icon in the Start menu, and choosing Run as administrator. It is very important to both log in using the account created in Step 1, and use the Run as administrator option when running Visual Studio.

If you are using Windows authentication in your IIS Web site, you must be running Visual Studio using the built-in Administrator account and therefore also run the Remote Debugging monitor on the remote computer using the built-in Administrator account. The password for the Administrator account must be the same on the client and remote server computers. If you need to use Windows authentication in your IIS Web site, and you cannot use synchronized Administrator accounts, you must turn off UAC on the remote server computer and reboot prior to attempting to debug.

This is not recommended for production servers because it may negatively affect the security of your server. Debugging in a domain environment is simpler to configure. Sign in to vote. We have checked web.

Monday, November 17, AM. You can try the following ways: Commonly, we can set enableEventValidation to false and viewStateEncryptionMode to Never in Page directive to resolve this issue. But it will cause security issue.

We can try to set " PostBackUrl " of Button to itself. Override the Render Event of the page to place the hidden fields for Encrypted Viewstate and Event validation on the top of the form.

Wednesday, November 19, AM. User posted when u have webfarm the server macid1 which responds to the first request may not be the server macid2 serving the consequent requests.

The Administration Tools window appears. In the Connections pane on the left side of the window, expand the item that corresponds to the name of the server on which you are working. The Add Application Pool dialog appears. In Name , enter NmConsole. NET Framework version , select the highest version available. Under Managed pipeline mode , select Classic.

Click OK. The new application pool is created. Configure advanced settings on the NmConsole application pool. Right-click the NmConsole application pool from the list, then select Advanced Settings from the right-click menu. The Advanced Settings dialog appears. Expand Process Model , then select the Identity row.

Click the browse The Application Pool Identity dialog appears. Select Custom account , then click Set. The Set Credentials dialog appears. Enter the name and password of the user you created for the WhatsUp Gold web interface to run as, then click OK.

Make sure the Maximum Worker Processes are set to 1. Click OK to exit the Advanced Settings dialog. In the Connections pane on the left side of the screen, under Sites, locate the Web site under which you want WhatsUp Gold to run.

Right-click it and select Add Application. The Add Application dialog appears. In Alias , enter NmConsole. Click the Select button next to Application pool. The Select Application Pool dialog appears. Select the NmConsole application pool, then click OK. In Physical path, enter or use the browse button to select the path to the WhatsUp Gold web interface.

Click Connect As.