Hi All, I installing SCCM 2007 SP2 on a client, but the error below is shown when I enable Discovery Network: The current environment is a Windows 2008 Server machine with SCCM 2007 R2 Enterprise SP2 and SQL 2005 Enterprise Network Discovery failed to perform a WinSock operation relating to multicast membership. Network Discovery will not discover other routers on your local subnet by listening for OSPF packets. However, if Network Discovery can detect your default gateway using SNMP, it will find those routers anyway. Possible cause: Some other network software on the server is preventing Network Discovery from joining the OSPF multicast group. Solution: Ensure that the TCP/IP stack is installed and running. Also, verify that you are using Windows NT version 4.0 or later. Note that this message will not be generated again during this Network Discovery session, regardless of how often the error occurs.

Please don't take this the wrong way but are you sure you want to do network discovery? I've never used it except for when I first used SMS 2.0 and I didn't really know what it was. It makes a huge mess of things. It's only good for people without AD. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |

Hi John, What in your opinion is the best for me to use on the environment? Best Regards

Dennis, What are you trying to do? Kind regards Tim Nilimaa IT Consultant at Mindgrape (Sweden) Please remember to mark this answer as helpful if it helped you.

If you have AD just use the AD discovery methods, network discovery makes a huge mess. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |

Nothing to add except that I concur with John. Network discovery pulls in non-managable devices (which is where the mess comes from) and relies on either SNMP or DHCP -- it is not a simple ping sweep.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys