You keep trying things until it works, figure out why it didn't work in the first place, then fix the holes you made. If this person is having trouble allowing access, perhaps instead of showing them how to allow it in the firewall (which someone already did) having him disabling it and trying again will net the results that the person wants. On a software firewall, generally you allow all communications on your network or subnet range to communicate to your computers blindly.if you don't, usually you are a bit more knowledgeable than the average user. another computer gets infected on your network, do you know what the chances of your computer getting infected? Lets say you have antivirus/antimalware software installed on your computers.same scenario. Lets take your home for instance, you don't run a software firewall on your computer. Going way off topic here.in what world would having a software firewall on a secure, trusted network be bad practice? I can't begin to tell you how many times the firewall blocked communications even though the rule stated to allow. Not always is it simple to allow a port, sometimes another port is required and blocked. There are many reasons to turn off the firewall. Can see what ports are being attached to and opening those ports when vendor documentation is lax or non existent.

Easy to determine culprit of connectivity issues.

How to remote desktop to server 2012