Endpoint Protection

 View Only
Back to discussions
Expand all | Collapse all

Microsoft networking blocked, but configured to work (SEP)

  • 1.  Microsoft networking blocked, but configured to work (SEP)

    Posted Jul 15, 2009 11:37 AM
    Hi All,

    I'm running SEP 11.0.4000.2295 unmanaged. In Network Threat Protection, Microsoft Network Configuration, I have enabled both sharing and browsing for the only connected adapter on the system. In Firewall settings, I do not have NetBIOS protection enabled just to make sure NetBIOS is open. However, when another client attempts to connect over port 139, it is blocked. In the log, I see the following:

    Application: ...\ntoskrnl.exe
    Rule: ...NBBLOCK#BLOCK-TCP

    NB would certainly seem to be NetBIOS block. Just starting recently, I started getting so many messages that access to ntoskrnl.exe had been blocked that I disabled the messages. I have SEP configured on another machine -- same version, same configuration -- and I can map network drives to that machine no problem.

    It's not clear to me why this has suddenly become an issue on the one machine. Can anyone please provide guidance on how to correct the configuration and make sure that NetBIOS traffic works as expected? Thanks.

    Regards,

    Gordon


  • 2.  RE: Microsoft networking blocked, but configured to work (SEP)

    Posted Jul 15, 2009 02:12 PM
    Hi,

    you can manually create an explicit rule in the SEP firewall to allow the traffic on the desidered ports.
    http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/8de5eb2eb1471d038025736b003df09c?OpenDocument

    What is the O.S.?

    Regards,