Since the update to V24, I have not been able to connect computers for file and printer sharing across my Private internal network scope. I could before the update. I also could set a Network or Device Trust level before the update. Now I get a SAMBA blocked (SMB Brute Force) message.
SMB is turned off on the Laptop that I usually use to access my main computer. I have also set an exclusion for the network IP Scope and for the individual machine, But still no luck. About ready to uninstall Norton!
1 Like
Your Automatic Network Control is Smart Mode with Notifications?
You Allow incoming file and printer sharing over SMB protocol?
You’re “Connected to” Private & your “Recent networks” are Private?
Curious, was v24 update thru LiveUpdate or clean install?
Hello Duane. Have you attempted creation of a new rule for the issue?
And/or changed this setting as well? Changed to Windows Settings Mode, restart and recheck?
SA
Yes, ANC is set to Smart mode with notifications.
network is Private.
Here are my SMB settings on the computer that is rejecting the connection.
And this install was done using the Norton Remove and Reinstall tool. The Norton 360 crashed and this was what I used to “bring it back to life”
this form will not let me upload an image of the SMB settings for some reason.
Are your images .bsp, jpg,jpeg or png ? A pdf is not supported. Your profile suggests that you have not achieved “basic” trust level on the forums. That is a part of the new format Norton went with so that is the most likely cause of not being able to post screenshots.
SA
Attachment was jpg.
Hello @Duane_Sellers
Please try uploading image to https://postimages.org/
Please try copy Direct link: and paste (space characters after dot - before Reply to break link) with your message.
for example:
https: //i. postimg. cc/FRDnZ2Zr/png-20065. png
or try Preformatted text </>
https://i.postimg.cc/FRDnZ2Zr/png-20065.png
1 Like
I too am having the same issue of receiving multiple SMBBF messages.
I found a workaround by adding the ip address as an exclusion and turning off samba protection.
It is very frustrating to have to try multiple solutions when there was no issue before V24.
I hope this helps.