Author Topic: How to disable a module which intercepts nmap scans on ports 25, 110, 119, 143 (Read 1544 times)

LionGold · « **on:** March 24, 2020, 08:58:27 AM »

How to disable a module which intercepts nmap scans on ports 25, 110, 119, 143 etc?
http://my.jetscreenshot.com/demo/20200324-hxql-87kb.jpg
Only port 3389 is real open

Asyn · « **Reply #1 on:** March 30, 2020, 03:30:43 PM »

Please attach your screenshot(s), some of us don't follow external links.

LionGold · « **Reply #2 on:** April 04, 2020, 11:32:34 PM »

I did

Asyn · « **Reply #3 on:** April 05, 2020, 05:47:38 AM »

So, how is this related to Avast..?

LionGold · « **Reply #4 on:** April 05, 2020, 01:23:13 PM »

All of this ports are declared by Avast (except 3389). And I want to exclude them.
For example, When I knocking by telnet on port 25 I have that answer:
"... concurrent connection limit in Avast exceeded ..."
And its ports are really closed in my infrastructure

Asyn · « **Reply #5 on:** April 06, 2020, 06:09:14 AM »

-> https://support.avast.com/article/25/ (Firewall FAQ)

Author Topic: How to disable a module which intercepts nmap scans on ports 25, 110, 119, 143 (Read 1544 times)

LionGold

How to disable a module which intercepts nmap scans on ports 25, 110, 119, 143

Asyn

Re: How to disable a module which intercepts nmap scans on ports 25, 110, 119, 143

LionGold

Re: How to disable a module which intercepts nmap scans on ports 25, 110, 119, 143

Asyn

Re: How to disable a module which intercepts nmap scans on ports 25, 110, 119, 143

LionGold

Re: How to disable a module which intercepts nmap scans on ports 25, 110, 119, 143

Asyn

Re: How to disable a module which intercepts nmap scans on ports 25, 110, 119, 143