How to configure Sql Server 2008 R2 for debugging without disabling Windows Firewall?

Question

When I try to debug a procedure in Sql Server 2008 R2 I get a dialog box telling me to unblock some ports.
>>
The Windows Firewall on this machine is currently blocking remote debugging.  Remote debugging requiers that the debugger be allowed to receive informatino from the network.  Remote debugging also requires DCOM (TCP Port 135) and IPSEC (UDP 4500
/ UDP 500) be unblocked.
<<
I went to the Windows Firewall and added some new Inbound rules for each of the specified ports (in the images below.  But after this and rebooting entire computer -- I still get this dialog box when I want to go into debug mode from SSMS.  I can
actually kind of debug standalone code in the SSMS window if I cancel the dialog box.  But I can't debug an actual stored procedure -- which is what I need to do.  I also noticed that my server has an IP address instead of LocalHost.  This is
not a public Server -- it's my private development machine which is on a peer to peer network (with one other workstation), but I don't need that workstation to be able to access this server..  Would localholst make a difference for debugging?  How
should I configure the sql server?  The firewall?
Rich P

Answer 1

Use PRINT and SELECT for debugging. That's what I do. I used to play with the debugger in SQL 2000 and older days, but I realised that I spent more time on getting it to work that I gained from using it.
I thought about that.  I guess that IS the way to go.  Very well.  Thank you for the suggestion.   Although, when the debugger does work in the regular window (not a stored proc because it doesn't work there) the debugger IS nice. 
For debugging my proc I am thinking I will insert param vals into a test collection table for now.  One obscure error I am getting with a particular proc -- in a When loop on one parameter I get the "value will be truncated" error -- but everything
is set to accept 1000 characters and none of the source data even comes close to 1000 characters.  I have isolated at what point the error occurs and which section of data where the error is occurring but I have not isolated the cause of the error. 
I cannot reproduce the error when I run the procedure by hand in a regular query window with the exact same code.  The error only occurs when the code is run in the stored proc.
Rich P