This is a new development. I have only had three occurences in the last 2 days to my SCOM 2007 R2 environment. One was a stand-alone server reporting to a Gateway Server and the other two were domain seervers communicating with a Management Server. The console alerts with a heartbeat failure and when looking at the agent's ops man log, I find this one: Event Type: Error Event Source: OpsMgr Connector Event Category: None Event ID: 21006 Date: 11/17/2010 Time: 12:43:36 PM User: N/A Computer: <Agented Server> Description: The OpsMgr Connector could not connect to <Managment Server.domain.com>:5723. The error code is 10055L(An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.). Please verify there is network connectivity, the server is running and has registered it's listening port, and there are no firewalls blocking traffic to the destination. The next Error was Event Type: Error Event Source: OpsMgr Connector Event Category: None Event ID: 21015 Date: 11/17/2010 Time: 11:46:04 AM User: N/A Computer: <Agented Server> Description: OpsMgr was unable to set up a communications channel to <Managment Server.domain.com>. Communication will resume when <Managment Server.domain.com> is available and communication from this computer is allowed. I restarted the health service on both Agent and Management Server. Cleared the health cache on the agent's server and still the 21006 error occured. Rebooting of the agent's server restored communication but thats not a good workaround in a production environment. Thoughts?

Can I assume that you have used certificates for communication between the gateway and agents/MS. If this is the case has the cert been loaded on the RMS also?Paul Keely

Certs in place and working correctly

Hi, Based on my research, I would like to suggest the following: 1. Please check the network connectivity between the server and the clients. You can try to ping each other. 2. Ensure the required ports are open: OpsMgr 2007: Port requirements for SCOM agents in a DMZ http://blogs.technet.com/b/operationsmgr/archive/2009/02/17/opsmgr-2007-port-requirements-for-scom-agents-in-a-dmz.aspx Hope this helps. Thanks. Nicholas Li - MSFT Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, Based on my research, I would like to suggest the following: 1. Please check the network connectivity between the server and the clients. You can try to ping each other. 2. Ensure the required ports are open: OpsMgr 2007: Port requirements for SCOM agents in a DMZ http://blogs.technet.com/b/operationsmgr/archive/2009/02/17/opsmgr-2007-port-requirements-for-scom-agents-in-a-dmz.aspx Hope this helps. Thanks. Nicholas Li - MSFT Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I've never seen the errorcode but i doesn't look like the "i don't have connection" problems... maybe a resource issue, which would explain why a reboot worked. "An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full"Rob Korving http://jama00.wordpress.com/

I am leaning in your dirrection but is the agent causing the buffer problem? Fortunately, it has not occurred again (so far). I have yet to find any other posts mentioning 10055L pertaining to a Ops Man Agent but was hoping someone else had experienced this.