My company has a DMZ which I've stood up a new 2016 domain controller for.
As soon as I install Symantec Endpoint Protection 14MR2 latest version, then reboot, then all network communications seem to cease. It's like networking is totally broken because you can't even browse the web or do dns lookups.
Looking into it deeply, it seems that the Symantec Firewall Driver isn't getting applied properly. I found a forum thread with manual steps to apply the driver with the "install" button in the ipv4 network adapter properties, but am met with an ACCESS DENIED message from Windows when trying to do this.
I called support and had a ticket open (might still be open) and when seeing how things were working they tried these same manual steps to bind the Firewall driver to the NIC but it didn't work due to the same error.
I tried all kinds of things and found that Windows firewall service is not running and neither is the base filtering engine, and these things need to be running for normal TCPIP operations.
Well, Symantec changes something because once it is installed these things happen. Even after removing Symantec using the cleanwipe utility I had networking issues persist until I ran a tool that repairs Windows Firewall/base filtering engine.
Strangely, after that the networking issues would always return after a reboot etc.
So, I totally started over with a new VM, fresh install of Windows Server 2016 and promote to a DC.
Install SEP, reboot, can't ping the server, can't get to the net, can't do anything, networking is hosed.
Support was not much help and didn't have much idea other than trying to uninstall and reinstall it.
Is anyone using SEP on Server 2016 in the wild with any issues?? This is extremely frustrating as I'm not able to finish my project because of this.