none
Diagnosing 21006 unable to connect to management server errors - help please RRS feed

  • Question

  • I would like to monitor Server X.  Server X is in a domain that has a management server that is functional.  Other servers on that domain are reporting back without any problems on that management server.  There are other servers on Server X's subnet that are reporting back properly as well.  Some of these servers are configured almost exactly the same as Server X.  Server X will not communicate with the management server no matter what I try.  I get mostly 21006 errors and 21016 errors.

    21006 :

    The OpsMgr Connector could not connect to (Managementserver):5723. The error code is 11001L(No such host is known.). 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.

    21016 :

    OpsMgr was unable to set up a communications channel to Managementserver and there are no failover hosts. Communication will resume when Managementserver is available and communication from this computer is allowed.

     

    Windows firewall on Server X is disabled.  I am able to ping the management server by name and by IP.  When I attempt to telnet on port 5723 from Server X to the management server I get the "press any key to continue" prompt but then I get "connection to host lost".  When I telnet on port 23, I get Connect Failed. 

     

     

    My networking group has of course said that there are no firewalls setup between these servers and that nothing should be blocking traffic on 5723 and 5724. 

    I'd like to know what specific steps you guys would try to diagnose this further?  I have full access to the windows OS on both machines, however I don't have any control over the networking area. 

    Monday, June 6, 2011 3:19 PM

Answers

All replies