Hi
So there may be a bug with port 10123 in that it opens a connection to the
server, and when it doesn't get a response, it leaves the connection open.
Naturally, it should fall back to port 80 or 443, but the open connections
raise the handle count on ccmexec to often well over 20,000 threads, rendering
the client essentially useless without stopping the service remotely. We have a
case open with CSS on this now, but suffice to say, there are no firewalls
between the clients and servers that have this issue, and it mainly happens on
Server 2003 systems and VMWare systems.
So we turned off port 10123. However, it appears that some of the clients now
request policy but never download any, even after reinstalling the client. We
are thinking that is because they believe they are still supposed to talk on
port 10123 still since they never received the policy that that port is now
blocked. I queried the registry to see if there was port 10123 in there
anywhere but was not able to find it. Thus, it must be in WMI. Does anyone off
the top of their head know where to find this in WMI? I started poking around
in the Root\CCM\Policy, but haven't found it yet.
Any ideas?
Thanks,-S
