Firewall - advanced security - remote desktop (tcp/in) - inbound rule - scope error I have restricted access to a win7 machine via the firewall and have set a IP access restriction as defined in the section outlined above and topic. the problem I have encountered is in the section Local IP and Remote IP. Under Local IP i have it set to Any IP address ( thus allowing any local ip access) remote access I have set one WAN IP from which I will be coming to the machine from, which is fine as i am not even testing this yet. infact i am adding this rule to this machine via remote desktop from a IP of 192.168.1.15 the win7 machine i am connected to is 192.168.1.16, once applied I loose access to this machine via RDP and only have console access. So I logged on via the console and figured it ( maybe its me, hence me askin!) does not know the difference between local ip and remote ip, so i added a rule-range in remote ip, 192.168.1.0 - 192.168.1.255 meaning any IP from this range can then connect, which, infact worked, and i could rdp to this machine again. my gripe is surely since my machine is in the same subnet then i should be under local ip and thus should be allowed to rdp to this machine, but i had to add a rule under remote ip? is this right, or is it a bug?

Local IP stands for the IP addresses of the local host. This is because you can have multiple IP addresses on a single NIC or systemand you canfor which address on the system your ruleapplies.The other system you are running is a remote system on the same subnet for Windows Firewall with Advanced security. You can define a rule select "Predefined set of computers" and then choose "Local Subnet", to establish what you just did by defining the address range of your local subnet.I hope this clarifies your issue.Ray