Norton blocks file sharing due to samba smb but smb is disabled

Hi all, I have had no problem sharing files between windows computers but since the latest Norton 360 product update norton is blocking connection attempts between a win 11 laptop and a win 10 desktop. Norton says " samba smb brute force attack blocked and device added to blocked list". When I check the blocked list it is empty. SMB is disabled on both computers. The only way to share files is uncheck samba smb protection in norton on the win 10 computer. Does anyone know how to fix this? and is it safe to run with samba smb protection turned off in norton?

Norton 360 v22.x or v24.x?

24.8.9372

I have wiped both computers and reinstalled clean copies of windows and Norton 360, I also have Norton utilities installed v24.2. Multiple full system scans, startup scan on both computers show they are clean.

as you wrote in your opening post…may be related to v24.x

I’m v22.x

I also encountered the same problem, which caused my tablet to be unable to connect to Windows 11 through SMB.
Even if I added the allowed connection IP in norton 360, I still could not connect. Can the norton support
help solve this problem?

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

@waygal888 If you’d like to revert back to version 22.24.8.36, if you haven’t already use this guide from another post of mine. Please post your progress with the SMB issue.

SA

I have had multiple phone conversations with support and each time they did things, including adding firewall rules, and these only worked until one of the computers went to sleep. The last person I spoke to said they would call back in a couple of days to check but never did. My experience with support has not been good. When my subscription is due for renewal I will be trying another product.

I had given up trying to solve this but recent posts prompted me to try again. It appears to be working now. I have the home network setup as private on both widows computers and all I did was change the network in norton firewall to public, so windows thinks it is a private network and norton thinks it is a public network. Don’t know why this would make a difference but it seems to be working now, that said windows 11 recently had a version update so it may have been that?

1 Like

Hi, I’m using Norton 360 version 24.12.9725 (build 24.12.9725.902). This just started happening for me also. While not a fix, I have found for my Windows systems (Win 10) that if I disable IPV6 on the incoming computers, the problem stops. It starts again when I re-enable IPV6 protocol. I do not disable IPV6 on the computer that has the share that is being accessed. Hope this can help someone.

1 Like

This worked for me. Thank you!

1 Like

Experienced the same problem with Win11 Server and Win10 Client. The solution I found was to remove shared drives and access passwords (in windows credentials manager) on the client side an get a new password entry for accessing the server. Then I could set up shared drives again and everything is fine.

is SMB enabled in the Win11 features? I gave up one sharing (like the old days) I too have computers with both windows and linux, they just do not communicate. It might work for you…some people have had some success.