Firewall Keeps Showing A Port Scan Block False?

I disabled it doing this:

Firewall -> Advanced -> Block Port Scans (switch off)

Until BitDefender creates a way to block port scans without needing that stupid message popping up every few seconds this will be the only solution. What kind of a response was that to his question Christian lol.

I am running BitDefender Security for Windows 8 as well.

If you have a hardware firewall that's pretty much the best protection available in regards to port scans.

Hello everyone,

Could you please let me know if the issue persists with the latest build version 16.27.0.1763 ? (See Christian's post on how to check the current build).

I have the same issue on my Windows 8 Laptop...(Internet security 2013 - Build 16.27.0.1763)

A port scan was detected and blocked.

Local IP: 192.168.1.101

Remote IP: 192.168.1.1

Protocol: UDP

Could we, at least, have confirmation that it's not some kind of virus/intrusion?

Any progress? It still does this even with most recent version.

http://www.help2go.com/forum/computer-help...ed-blocked.html

From Digerati

"It is not just Bit Defender users experiencing this.

Note: ESET

Symantec

Sophos

Understand this warning is telling you something is scanning your ports, but has been blocked. That is not saying you have been compromised, or that this is an attack. It could simply be another computer or networked device on your own network trying to join your home or workgroup.

That said, since it could be a nosy neighbor wizkid (if this is a wireless network) or a badguy with malicious intent trying to access your computers, it is wise to be cautious."

==============================================

Just make sure that it's a local network address - 192.168....

===============================================

Some reading about Port Scanning:

Port Scanning is one of the most popular reconnaissance techniques attackers use to discover services they can break into. All machines connected to a Local Area Network (LAN) or Internet run many services that listen at well-known and not so well known ports. A port scan helps the attacker find which ports are available (i.e., what service might be listing to a port). Essentially, a port scan consists of sending a message to each port, one at a time. The kind of response received indicates whether the port is used and can therefore be probed further for weakness.

Read here: http://www.auditmypc.com/port-scanning.asp

I have BDIS 2013 build 16.28.0.1789 and I just experienced a few "Blocked port scans" - and I didn't have them before, with earlier builds. The problem is that on every blocked port scan my connection drops for a few minutes. Windows 7 is then "diagnosing" the connection, fixes a few things, and in some 6-7 minutes the connection is back. For now I disabled the "Block port scan" but I would like to know what is causing this, and of course, how to sort it out. All my blocked "port scans" were coming from the "remote" IP 192.168.2.1

Internet Security 2013, false port scan detected blocked warning message

A few days ago I submitted a trouble ticket outlining the problem and received the response “disable port scan blocking”. Since I have a single PC (no other devices on the subnet) behind a hardware firewall this is a reasonable work around. However, I don’t think this would be an acceptable solution to anyone not protected by a hardware firewall.

I first noticed the status message “port scan detected and blocked” over six months ago and since the source of the address of the of the offending IP traffic was my ISP DNS servers I decided to ignore the message. I recently upgraded my PC to Window 8 Pro, 64 bit and am still seeing the warning message.

A quick review of the bitdefender forums indicate that this problem was first reported in July 2011 and was supposed fixed. However subsequent forum post indicate that the problem persists.

This would trend to indicate that Bitdefender does not know what causes the problem, or does not know how to fix the problem or is not willing to fix the problem.

The warning message usually pops up after I go to the MSN website (IE10). I assume this generates a significant number of DNS request and for some unknown reason triggers the warning message.