I am new to Windows Defender but have read about it to understand the basics of Inbound/Outbound rules.

As mentioned on the app, Inbound connections that do not match a rule are simply blocked.

For my system, I have few number of inbound rules for port 135 AND of these rules are disabled. Which if I understand correctly, will be closed for all the services coming through the port?

Yet an NMap scan shows that port 135 is open.

I think I am missing something here - maybe my understanding of open/closed ports is not correct. Appreciate any help or resources!

  • 2
    You probably port scanned on local ip and not public ip – Vipul Nair Aug 21 '19 at 17:21
  • @Malabika Sen What are the active rules? Did you check if they are permissive? Also as Vipul pointed out above, are you running scans on 'localhost'? – hax Aug 21 '19 at 21:23
  • Hi, I am not running scans on a localhost per se but yeah, these are the IPs of my private local network. Yes, they are not public IPs. Where can I see the active rules? @VipulNair – Malabika Sen Aug 22 '19 at 11:41
  • @hax - I understand that you mean firewall rules when you said active rules. Like I mentioned in the post, all of the rules for port 135 are disabled. – Malabika Sen Aug 22 '19 at 11:47
  • @MalabikaSen Try and port scan public ip.If it is closed then it is closed for everyone that is not on the same network.As for blocking for everyone including devices on the same network.There are firewall rules you can set for that as well.The implementation would be different for whatever you are using – Vipul Nair Aug 22 '19 at 11:55

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.