Hello,
I can no longer get any SEP clients to communicate back to the SEPM server. Please read my findings and also what I think I may have done to cause it at the very end.
Here's my findings:
- Server PC successfully pings from client
- Client PC successfully pings from server
- SECARS test from client PC fails with "This page can’t be displayed" (I'm using: http://avconsole:8014/secars/secars.dll?hello,secars)
- Telnet fails from Client PC to server with "Could not open connection to the host, on port 8014: Connect failed" (I'm using: telnet avconsole 8014)
- Running netstat -a | findstr LISTENING from Server PC shows: TCP 0.0.0.0:8014 AVCONSOLE:0 LISTENING
- I'm not using the Symantec Firewall at all.
- I have a Windows Firewall Rules for both Inbound and Outbound allowing TCP 80, TCP 139, TCP 443, TCP 445, TCP 1100, TCP 1433, TCP 2638, TCP 2967, TCP 8014, TCP 8045, TCP 8443, TCP 8444, TCP 8445, TCP 8446, TCP 8447, TCP 8765, TCP 9090, TCP 49152 - 65535, UDP 137, UDP 138, UDP 1812, UDP 39999
- Open Symantec Client, going to Troubleshootling, under Management the Server is listed as Offline
- Open Symantec Client, going to Troubleshootling, under Connection Status, the Status is listed as Not Connected with Error listed as WinInet error 9
- I've attached my Sylink log
What I think I may have done to cause it:
My system was working fine last week. Green dots on all clients. But I made two changes where I think one or both could be the issue(s) but I'm not exactly sure how to fix them.
My 1st bone-headed mistake: I accidentally linked a GPO to the Server PC that reconfigured it's firewall rules and made them more complicated/broken (before the GPO was applied they were the generic initial firewall rules that comes with a typical Windows install). I then unlinked the GPO and in the Windows Firewall settings on the Server PC I hit "Restore Default Policy"
2nd bone-headed mistake: I re-organized my Active Directory structure the same week. The Symantec Management Console had the old hierarchy so I did a "sync now" and it reflected the new hierarchy.
One or likely both of these actions caused my issue. Please weigh in on what you think it is based on the Sylink log and my messed-up actions. :) I've spent hours looking through the archives here to solve my own issue but I'm missing something. Please help!