Microsoft KB Archive/292727

= INFO: Visual InterDev 6.0 ASP Debugging Through a Proxy or Firewall Is Not Supported =

Article ID: 292727

Article Last Modified on 10/15/2002

-

APPLIES TO


 * Microsoft Visual InterDev 6.0 Standard Edition

-



This article was previously published under Q292727



SUMMARY
Visual InterDev 6.0 Active Server Pages (ASP) server-side script debugging is not supported when there is a firewall or a proxy between the Visual InterDev 6.0 client and the Web server.



MORE INFORMATION
The debugger uses Distributed Component Object Model (DCOM) to communicate between the Visual InterDev 6.0 client and the Web server. However, the DCOM Remote Procedure Calls (RPCs) fail to go through a firewall. In addition, the authentication credentials that must attach to the process fail to pass through a firewall or a proxy.

If you are debugging automatically, you receive the following error message:

Unable to find server. Unable to set server into correct debugging state automatically. You may not be able to debug ASP pages. Do you want to continue launching the debugger?

If you are debugging manually, you receive the following error message:

Can't attach to machine  

If you are going through a firewall, your only option is to debug locally on the client computer.

If you are going through a proxy and are in a local intranet, you can bypass the proxy server to work around this issue. To bypass the proxy, follow these steps:
 * 1) Open Internet Explorer.
 * 2) From the Tools menu, click Internet Options.
 * 3) On the Connections tab, click LAN Settings.
 * 4) In the Local Area Networks (LAN) Settings dialog box, select the Bypass proxy server for local addresses check box.
 * 5) Click OK twice.

