Analsysing the ProcMon trace and viewing real-time in Process Viewer it reveals there's a lot of chatter between itself Now it's restarted I've copied on Process Monitor and let a trace run while the server is starting to consume ports once more. I've had to restart the site server in order it's accessible on the network again, it had consumed all available ports. Maybe having hundreds of connections open at any oneĪny help and advice would be much appreciated. The question is whether this relates to underlying SCCM activity which isn't opening/closing connections as expected. The PID for these connections correlates to the SYSTEM process which isn't much help. More port 445 connections are steadily being established under the IPv4 interface, the concern being that the problem isn't resolved and will eventually reoccur albeit after a little more time now IPv6 isn't in the equation. We had IPv6 enabled which probably exacerbated the problem so this was disabled and everything sprang back to life. On further investigation, using NETSTAT, we found that there were thousands of connections over port 445. A server restart would resolve the problems for a few hours and then the issue would return. SCCM communication would stop, numerous event log errors and the Primary Site Server would display numerous Management Point and Distribution Manager errors for that We have 3 similarly configured servers at the site that don't use SCCM and there are no problems at all, hence the post in this forum.ĭomain communication secure channel authentication, group policy, etc would cease to work.

We have an SCCM 2007 R3 Secondary Site server that has been exhibiting a number of issues since it was installed.

Tcpview startimes