Endpoint Protection

 View Only
  • 1.  SEP 12.1 RU1 & Samba Shares (OS X 10.5.8)

    Posted Mar 28, 2012 10:13 AM

    I am having an odd issue with the 12.1 RU1 client and connecting to OS X 10.5.8 Samba shares.

    A clean load of a Windows 7 x64 with SP1 system can connect to these servers with no issues but as soon as I install the SEP client I get nothing but "The specified server cannot perform the requested operation." error. Connections to all other Windows computers (WinXP, Win7, WinServer 2k8, WinServer2k3) works as it should. To add even more oddities to this it only happens on a clean load of 12.1 RU1. Computers that had a previous version of SEP then upgraded to 12.1 RU1 do not exhibit this issue. Also removing the SEP client from the machines does not fix the issue. Only completely reinstalling the machine does.

    Firewall and Application and Device Control do not seam to be causing the issue as I have disabled both of these and the problem still exists. Not to mention the exact same profiles are enabled on upgraded machines and they have no issues.

    The error pulled from the Samba logs:
    [2012/03/27 14:27:50, 0, pid=89419] /SourceCache/samba/samba-187.14/samba/source/lib/util_sock.c:read_data(540)
      read_data: read failure for 4 bytes to client 10.10.56.177. Error = Connection reset by peer



  • 2.  RE: SEP 12.1 RU1 & Samba Shares (OS X 10.5.8)

    Broadcom Employee
    Posted Mar 28, 2012 10:26 AM

    can you try installing only AV component and let know the results?



  • 3.  RE: SEP 12.1 RU1 & Samba Shares (OS X 10.5.8)

    Posted Mar 28, 2012 11:11 AM

    Ill give it a try.

    Just tried installing a older SEP client (11.0.7101.1056) and got the same result.



  • 4.  RE: SEP 12.1 RU1 & Samba Shares (OS X 10.5.8)

    Posted Mar 28, 2012 12:11 PM

    Just did an install of 12.1 RU1 on a clean install of Win7 Pro x64.

    I installed everything but network protection and it is giving the same error,



  • 5.  RE: SEP 12.1 RU1 & Samba Shares (OS X 10.5.8)

    Posted Mar 29, 2012 11:04 AM

    The issue is more of a connecting to Samba problem than a connecting to OS X problem. I set up a SMB server on a CentOS box we have here and got the same errors.