Re: Remote debugging blocked by firewall in Windows Server 2003
- From: rainierwolfcastle@xxxxxxxxx
- Date: 14 Aug 2006 20:57:24 -0700
I've got it working, now. The only way it will work is if I configure
it to run as a service (which I was holding off on doing until it would
work as described in the docs). Since I was desperate, I gave it a shot
anyway and it works. Frigging Microsoft piss me off sometimes!
rainierwolfcastle@xxxxxxxxx wrote:
I'm trying to get remote debugging of ASP.NET v2 web applications
working between my XP Pro (64-bit) machine and Windows Server 2003
(32-bit) and the Visual Studio 2005 Remote Debugger Configuration
Wizard says "The Windows Firewall on this machine is currently blocking
remote debugging" whether I enable the firewall with TCP 135, UDP 500,
and UDP 4500 ports opened or whether I disable the firewall completely.
Does Windows Server 2003 have some other, hidden, firewall that isn't
configurable with the Windows Firewall applet in the control panel? I
have a trial version of server installed (doing uni assignments) and
I'm fast regretting my decision to switch from Java Servlets with
Tomcat. This remote debugging is a bitch to get working (even though
MSDN says otherwise).
I've also followed the various guides in MSDN on setting up remote
debugging, too, but apparently to no avail.
.
- Follow-Ups:
- References:
- Remote debugging blocked by firewall in Windows Server 2003
- From: rainierwolfcastle
- Remote debugging blocked by firewall in Windows Server 2003
- Prev by Date: Remote debugging blocked by firewall in Windows Server 2003
- Next by Date: Re: Customized Debug Watch for C++ objects?
- Previous by thread: Remote debugging blocked by firewall in Windows Server 2003
- Next by thread: Re: Remote debugging blocked by firewall in Windows Server 2003
- Index(es):
Relevant Pages
|