Clients not being discovered in a Secondary site

Goto the SMS Home Page

 

We've been trying to get 5 NT workstations discovered at our first Secondary site we've ever set up for several days. Nothing has appeared yet so I think we must be doing something wrong.

I have a question as far as enabling the subnet to be discovered. There's a setting in the Site Settings of the Secondary site to enable the subnet - we've enabled that one, with the correct subnet, mask, hops, community name, etc. Do we need to enable the same subnet on the Primary site too? I didn't think we did, but based on the fact that we're not getting the workstations discovered, I'm looking for the reasons.

You don't need to enable the same subnet on both the Secondary and Primary sites. Make sure that the any subnet is enabled (on search local subnet is checked) and that the schedule time is set at least few minutes ahead of the present time - Network Discovery will not run if it missed the last schedule. Alternatively you can fire it manually from the "Service Manager" or the Registry.

As for troubleshooting check the "
NETDISC.LOG" file. Also check that the "Windows Management" service is running as it is required for Network Discovery to run. Every time I had a problem with Network Discovery at the Secondary site, Windows Management was the problem.
 

© FAQShop.com 2003 - 2008

Goto the SMS Home Page

Email the Author