VS2005 Remote Debugger and Windows Firewall not working

[Noël Danjou]

LH Feb CTP
Visual Studio 2005 Professional


Hello,

I am trying to debug a Windows Firewall-related issue in one of my program
using the Remote Debugger.

The installation of the Remote Debugger (Run as administrator...) went fine
but everytime I run it I am prompted with a "Configure Firewall for Remote
Debugging" dialog box with the following choices:

- Cancel remote debugging
- Unblock remote debugging from computers on the local network
- Unblock remote debugging from any computers

If I tick either of the Unblock options and click OK, I get the following
message:

"Visual Studio Debugging Monitor - Could not configure the Windows
firewall. Incorrect function"

Could someone please explain how I can use the Remote Debugger with the
Windows Firewall in Longhorn February CTP (I had the same issue in the
previous build) ?

"IPSec (IKE NAT-T)" (UDP 4500), "IPSec (IKE)" (UDP 500) and "RPC Endpoint
Mapper and DCOM infrastructure" (TCP 135) exceptions are all ticked in the
Windows Firewall.

Actually the Windows Firewall issue I wanted to debug in my program is also
the "Incorrect function" (or "The system cannot find the file specified")
error message. I'd very much appreciate if anyone had information about how
to fix the issue. Thank you.

 

[Guest]

LH Feb CTP
Visual Studio 2005 Professional

Longhorn questions should be addressed in the Beta newsgroups Microsoft
provides, that way you aren't leaking pre-release information to people who
aren't on the beta.

Alun.
~~~~

 

[Noël Danjou]

Hello Alun,

Actually the issue applies to Vista as well. I also asked in the LH private
newsgroup but got no reply yet.

Sincerely,

 

[Noël Danjou]

Hi Sylvain,

Thanks for your message. Unfortunately no, I still don't have a solution.
Any information or suggestion would be welcome.

Sincerely,

 

[Gregg Kowalski]

Unfortunately I don't have a solution either. I just thought I'd post to say that I am hitting this same problem. I've tried creating/enabling the firewall exceptions that it mentions:
- Authorized Application exception for: msvsmon.exe
- Globally Open Port for: TCP 135 (DCOM)
- Globally Open Port for: UDP 4500 & 500 (IPSec)
- Enabled the File and Printer exception

I even tried enabling all of the File and Printer Sharing rules using wf.msc, but this didn't help either.

The only workaround seems to be disabling the firewall all together.

- Gregg

EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com