How to debug using a private address?

I have an odd problem. I'm beating myself bloody trying to get
debugging to work. I have VS.Net 2005 installed on a Windows XP SP2
workstation and on a W2003 Server. The asp.net application is
working. I need to debug. I get the error:

"Unable to start debugging on the web server. The debugger cannot
connect to the remote computer" ...and something about it not existing
or firewall problems. I'll note here that I can manually attach to
the web server process and that the debugger is loaded on the web
server. It shows "Administrator" as connected if I manually attach.

I do have a firewall. It's a Netscreen hardware firewall with Trust,
Unstrust and DMZ zones.

Trust: 10.0.1.x
DMZ: 10.0.0.x

Trust to DMZ is configured All/All.
Trust to Untrust is configured All/All
Untrust to DMZ is set to block TCP 135.

I opened TCP 135 and UDP 4500 and 500 from untrust to DMZ. It still
doesn't work. MS says one should not try to debug through a firewall
but the workstation and server are in 2 different zones for a very
good reason and opening TCP135 to the Untrusted zone is not wise. I
assume my data path from the workstation is from trust to untrust to
DMZ.

So what do I use? I can't debug to 10.0.0.9 because all of our
websites are DNS (host header) based. How do I debug
http://myweb.mydomain.com locally? It will always resolve to a public
address. I can't say myweb.mydomain.com is 10.0.0.9 in DNS, it's a
non-routeable address.

The server's actual name is www1. I'm thinking I could debug using
this name (resolves to 10.0.0.9) but if I go to http://www1 with a
browser I get nothing.

How do I resolve this or what's the best method of debugging when the
server uses host header names and is in a DMZ?

Thanks!

.

Relevant Pages

  • *****UNABLE TO MAP THE DEBUG START PAGE URL TO A MACHINE NAME - HELL ON EARTH - PLEASE HELP!
    ... ASP.Net debugging through a firewall. ... Terminal Services to log into the remote server and debug locally. ... "Were the proper setup programs run to install ASP.NET or ATL Server ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: QUERY: debugging ASP VBScript
    ... > the web application running and whenever I want to debug I follow these ... >> on the client and the server. ... In order to debug ASP pages, ... you should enable debugging manually on the server ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: how analyze malfunctioning asp.net application?
    ... a product server, correct? ... unhealthy and teh worker process will be recycled. ... production debugging in your environment. ...
    (microsoft.public.dotnet.framework.performance)
  • Re: QUERY: debugging ASP VBScript
    ... at a breakpoint. ... > the web application running and whenever I want to debug I follow these ... >> on the client and the server. ... you should enable debugging manually on the server ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: QUERY: debugging ASP VBScript
    ... effect to the debugging. ... >> dllhost.exe and click on attach. ... >> the web application running and whenever I want to debug I follow these ... >>> on the client and the server. ...
    (microsoft.public.dotnet.framework.aspnet)
Loading