Network Discovery does not work

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

Network Discovery does not work

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager >> Network Discovery does not work

Page: [1]

Message

<< Older Topic Newer Topic >>

Network Discovery does not work - 5/7/2008 10:58:36 AM

cxesam

Posts: 22
Score: 0
Joined: 10/29/2007
Status: offline

Hi

I've recently installed and configured SCCM in our production environment. The relevant boundaries have been defined etc. We have not enabled any of the AD discovery methods (for plenty of reasons) and would prefer using the Network Discovery method. However; it does not work. No log files (netdisc.log) is being generated and it doesn't pick up anything. The way we configured it is as follows:
Type of discovery - topology, client and client operating systems
Slow network is ticked
We've defined the subnets and "search local subnets" is selected
Under domain, we didn't specify anything except the "seach local domain" is selected
SNMP & SNMP Devices & DHCP we left as default. DHCP is not enabled in the environment.
Then of course we scheduled it to run after hours for 6 hours.

Collections were updated; but no entries. I checked under status message queries and saw that the component started and stopped at a specific time (2 minutes apart). There is no log file (netdisc.log), except the ddm.log.
Oh and the only other discovery method that is enabled is Heartbeat discovery set to 3 days.

Why is it not generating the relevant information/discovery or the log file? How are you suppose to configure the network discovery so that it actually works? I would appreciate any feedback pls?
Thanks!

Post #: 1

RE: Network Discovery does not work - 5/7/2008 5:21:02 PM

phaustein

Posts: 772
Score: 28
Joined: 3/21/2005
From: Washington, DC
Status: offline

Start by double-check that logging is turned on. This should be turned on be default. This can be checked by launching the ConfigMgr Service Manager located under the Tools folder. Select the SMS_Network_Discovery component name and right-click and select logging. This should be checked and give you the file size.

_____________________________

Hope this helps.
Paul

(in reply to cxesam)

Post #: 2

RE: Network Discovery does not work - 5/7/2008 5:24:30 PM

phaustein

Posts: 772
Score: 28
Joined: 3/21/2005
From: Washington, DC
Status: offline

Also, check the sitecomp.log for entries that relate to the network discovery. This should give you an idea of what is or is not happening.

_____________________________

Hope this helps.
Paul

(in reply to phaustein)

Post #: 3

RE: Network Discovery does not work - 5/8/2008 1:58:15 AM

cxesam

Posts: 22
Score: 0
Joined: 10/29/2007
Status: offline

Hi Paul

Thanks for the feedback. I checked and logging is enabled for netdisc.log. I also went through the sitecomp.log and didn't see anything unusual. I suppose the log file is not being created because nothing is happening (for some odd reason). I'm really confused right now as to why the discovery is not working....

(in reply to phaustein)

Post #: 4

RE: Network Discovery does not work - 5/8/2008 5:02:23 AM

cxesam

Posts: 22
Score: 0
Joined: 10/29/2007
Status: offline

Ok...we finally managed to figure out what the problem was. We had to define another SNMP community name besides "public", which was defined as a string on one of our switches. As soon as we entered that information, we scheduled the discovery and immediately the log file netdisc.log was created and it started picking up the resources.

(in reply to cxesam)

Post #: 5