


I created new rules on the workstation to allow those connections through from the server running the SEP management console.

I tried to push the client again and found that Windows Firewall was dropping connections from the management console on TCP ports 139 (NetBIOS) and 445 (MS Active-Directory). When the SEP console couldn't connect to and push out a client to the workstation, I decided to turn on dropped packet logging on Windows Firewall on the workstation. I decided to test redeploying a managed client to one of my workstations from the SEP management console. I found out what the problem was and I'm kicking myself in the tail for not seeing it sooner. Thanks all, for your replies and suggestions.
