Re: Network Discovery Stopped Working

From: fwiest (fwiest_at_us.grundfos.com)
Date: 10/26/04 

Date: Tue, 26 Oct 2004 11:43:03 -0700

Can you tell me what "annonymous access" means to a Cisco router? I take it
that is not a readonly SNMP community? No device authentication?

fred

"Dave Halperin" wrote:

> YOu also need to allow for annonymous acess to the router in order to get
> the ARP tables.
> "fwiest" <fwiest@us.grundfos.com> wrote in message
> news:50D80CD3-D946-4F27-98FA-2C461FA2C7F4@microsoft.com...
> > Hello Matt. Thank you for responding.
> >
> > 1. We are running on a 2003 server. The SQL database is on a seperate
> server.
> >
> > 2. The SMS Site server and all devices are members of a NT 4.0 domain.
> >
> > 3. We have options Subnets, Domains, and SNMP enabled.
> >
> > 4. All OSes are Win XP.
> >
> > 5. The Site Boundaries are correct.
> >
> > We have done some expiermenting since yesterday which may shed some more
> > light.
> >
> > I understand with SMS 2003 and Win 4.0 domains that the Domain discover
> does
> > not work, by design. Can you confirm this?
> >
> > So that leaves Subnet and SNMP discovery. We thought that the first
> > discovery that worked was using the ARP table in the router (a Cisco 6509
> > switch). But I am now wondering if it used SNMP to find the router. But we
> > can't understand why it worked the first time but wouldn't work now.
> >
> > I added an entry for the router in the SNMP Devices and discovery worked.
> So
> > now I am confused. I thought it should find the ARP table in the switch
> > without SNMP.
> >
> > We also tried the Enhanced System Discovery tool, which worked as well.
> >
> > So, is there a trick to pointing to the ARP table without using SNMP?
> >
> > Kind regards,
> > fred
> >
> > "Matt Goedtel [MSFT]" wrote:
> >
> > > Thanks for your posting,
> > >
> > > In order to better assist you, can you provide a little more background
> > > information on your environment and the SMS Site Server:
> > >
> > > 1. Is SMS Site Server running on Windows 2000 or Windows Server 2003?
> > > 2. Is SMS Site server domain member of NT 4.0 Domain since you state
> you do
> > > not have AD implemented yet?
> > > 3. What Network Discovery options did you enable - IP Subnet, Domain,
> etc?
> > > 4. What OS are the clients running you are trying to discover?
> > > 5. You state it discovered all the clients initially, did you correctly
> > > configure the Site Boundaries?
> > >
> > > Once you provide some additional info on your environment, I can better
> help
> > > you and determine what the issue may be. To help you get up to speed on
> SMS
> > > 2003, may I suggest the Concepts, Planning, and Deployment Guide -
> > >
> http://www.microsoft.com/resources/documentation/sms/2003/all/cpdg/en-us/default.mspx
> or http://www.microsoft.com/smserver/techinfo/productdoc/default.asp
> > >
> > > Regards,
> > >
> > > Matt Goedtel
> > >
> > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > >
> > >
> > > "fwiest" wrote:
> > >
> > > > We are new to SMS and have installed SMS 3.0 with SP1 and are having
> problems
> > > > with discovery. We don't have SNMP on clients, don't use Microsoft
> DHCP, so
> > > > Network Discovery is our only option. We are not running AD.
> > > >
> > > > When we first installed SMS, we got what looked like a pretty complete
> > > > discovery. It now appears that, from the netdisc.log, it is
> discovering the
> > > > SMS server itself and creating a DDR (which is strange because it is
> already
> > > > there) but not finding any other devices. It's almost like we "broke"
> > > > something. We added a new system to the network and it can't find it.
> I then
> > > > deleted two systems and it won't re-discover them.
> > > >
> > > > With the attached netdisc.log, could someone shed some light on what
> is
> > > > going wrong?
> > > >
> > > > DD: ThreadIdle 1 About to unlock m_pOutstandingTasks(0x0078EF30)
> Thread ID:
> > > > <0x00000690>, Task Count: <0> SMS_NETWORK_DISCOVERY 10/25/2004 1:05:32
> > > > PM 1680 (0x0690)
> > > > DD: Thread pool object shutdown. NT Browser and OS Retriever. Thread
> ID
> > > > <0x00000690> SMS_NETWORK_DISCOVERY 10/25/2004 1:05:32 PM 1680 (0x0690)
> > > > DD: ThreadIdle 1 About to unlock m_pOutstandingTasks(0x007F6DA8)
> Thread ID:
> > > > <0x00000950>, Task Count: <0> SMS_NETWORK_DISCOVERY 10/25/2004 1:05:32
> > > > PM 2384 (0x0950)
> > > > DD: Thread pool object shutdown. DNS Thread. Thread ID
> > > > <0x00000950> SMS_NETWORK_DISCOVERY 10/25/2004 1:05:32 PM 2384 (0x0950)
> > > > DD: ThreadIdle 1 About to unlock m_pOutstandingTasks(0x0078EF30)
> Thread ID:
> > > > <0x00000180>, Task Count: <0> SMS_NETWORK_DISCOVERY 10/25/2004 1:05:32
> PM 384
> > > > (0x0180)
> > > > DD: Thread pool object shutdown. NT Browser and OS Retriever. Thread
> ID
> > > > <0x00000180> SMS_NETWORK_DISCOVERY 10/25/2004 1:05:32 PM 384 (0x0180)
> > > > DC: Protocol module <AD_ADM.dll> reports it is in an idle state while
> > > > checking idle state. SMS_NETWORK_DISCOVERY 10/25/2004 1:05:34 PM 3120
> (0x0C30)
> > > > DC: Protocol module <AD_SIM.dll> reports it is in an idle state while
> > > > checking idle state. SMS_NETWORK_DISCOVERY 10/25/2004 1:05:34 PM 3120
> (0x0C30)
> > > > DC: Idle state detected. Stopping
> > > > discovery. SMS_NETWORK_DISCOVERY 10/25/2004 1:05:34 PM 3120 (0x0C30)
> > > > STATMSG: ID=1304 SEV=I LEV=M SOURCE="SMS Server"
> > > > COMP="SMS_NETWORK_DISCOVERY" SYS=FRSMS SITE=GMU PID=2116 TID=380
> GMTDATE=Mon
> > > > Oct 25 20:05:34.725 2004 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4=""
> > > > ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9=""
> > > > NUMATTRS=0 SMS_NETWORK_DISCOVERY 10/25/2004 1:05:34 PM 380 (0x017C)
> > > > DC: Notifying protocol module <AD_ADM.dll> to stop
> > > > discovering. SMS_NETWORK_DISCOVERY 10/25/2004 1:05:34 PM 3120 (0x0C30)
> > > > ADM: RIP thread shutdown. Thread ID
> > > > <0x00000A7C> SMS_NETWORK_DISCOVERY 10/25/2004 1:05:34 PM 2684 (0x0A7C)
> > > > ADM: DHCP thread shutdown. Thread ID
> > > > <0x0000051C> SMS_NETWORK_DISCOVERY 10/25/2004 1:05:34 PM 1308 (0x051C)
> > > > ADM: ICMP thread shutdown. Thread ID
> > > > <0x00000D3C> SMS_NETWORK_DISCOVERY 10/25/2004 1:05:34 PM 3388 (0x0D3C)
> > > > ADM: ICMP second thread shutdown. Thread ID
> > > > <0x00000EA0> SMS_NETWORK_DISCOVERY 10/25/2004 1:05:34 PM 3744 (0x0EA0)
> > > > DC: Notifying protocol module <AD_SIM.dll> to stop
> > > > discovering. SMS_NETWORK_DISCOVERY 10/25/2004 1:05:34 PM 3120 (0x0C30)
> > > > ADM: OSPF thread shutdown. Thread ID
> > > > <0x00000518> SMS_NETWORK_DISCOVERY 10/25/2004 1:05:34 PM 1304 (0x0518)
> > > > ADM: NtBrowser Waiting for thread manager to exit. Thread ID
> > > > <0x00000608> SMS_NETWORK_DISCOVERY 10/25/2004 1:05:34 PM 1544 (0x0608)
> > > > ADM: NtBrowser Thread manager exited. Thread ID
> > > > <0x00000608> SMS_NETWORK_DISCOVERY 10/25/2004 1:05:35 PM 1544 (0x0608)
> > > > ADM: NtBrowser thread shutdown. Thread ID
> > > > <0x00000608> SMS_NETWORK_DISCOVERY 10/25/2004 1:05:35 PM 1544 (0x0608)
> > > > ADM: DNS Waiting for thread manager to exit. Thread ID
> > > > <0x00000E00> SMS_NETWORK_DISCOVERY 10/25/2004 1:05:35 PM 3584 (0x0E00)
> > > > ADM: DNS Thread manager exited. Thread ID
> > > > <0x00000E00> SMS_NETWORK_DISCOVERY 10/25/2004 1:05:35 PM 3584 (0x0E00)
> > > > ADM: DNS thread shutdown. Thread ID
> > > > <0x00000E00> SMS_NETWORK_DISCOVERY 10/25/2004 1:05:35 PM 3584 (0x0E00)
> > > > SIM: SNMP thread shutdown. Thread ID
> > > > <0x000004EC> SMS_NETWORK_DISCOVERY 10/25/2004 1:05:36 PM 1260 (0x04EC)
> > > > DC: Deleting systems which are old... SMS_NETWORK_DISCOVERY 10/25/2004
> > > > 1:05:36 PM 3120 (0x0C30)
> > > > DC: Flushing network cache... SMS_NETWORK_DISCOVERY 10/25/2004 1:05:36
> > > > PM 3120 (0x0C30)
> > > > DC: Finished flushing network cache... SMS_NETWORK_DISCOVERY
> 10/25/2004
> > > > 1:05:36 PM 3120 (0x0C30)
> > > > DC: Flushing system cache... SMS_NETWORK_DISCOVERY 10/25/2004 1:05:36
> > > > PM 3120 (0x0C30)
> > > > DC: Finished flushing system caches. SMS_NETWORK_DISCOVERY 10/25/2004
> > > > 1:05:36 PM 3120 (0x0C30)
> > > > STATMSG: ID=1307 SEV=I LEV=M SOURCE="SMS Server"
> > > > COMP="SMS_NETWORK_DISCOVERY" SYS=FRSMS SITE=GMU PID=2116 TID=380
> GMTDATE=Mon
> > > > Oct 25 20:05:36.718 2004 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4=""
> > > > ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9=""
> > > > NUMATTRS=0 SMS_NETWORK_DISCOVERY 10/25/2004 1:05:36 PM 380 (0x017C)
> > > > DC: Exporting systems... SMS_NETWORK_DISCOVERY 10/25/2004 1:05:36 PM
> 3120
> > > > (0x0C30)
> > > > ExportDevice <10.96.10.180 255.255.252.0> SMS_NETWORK_DISCOVERY
> 10/25/2004
> > > > 1:05:36 PM 3120 (0x0C30)
> > > > FRSMS is not in any AD Site. SMS_NETWORK_DISCOVERY 10/25/2004 1:05:36
> > > > PM 3120 (0x0C30)
> > > > ** DDR creation record **~Filename:
> > > > C:\SMS\inboxes\auth\ddm.box\3obd1va7.DDR~Device: System~Device info:
> NetBIOS
> > > > Name FRSMS~Resource Domain OR Workgroup US.GRUNDFOS.COM~Operating
> System Name
> > > > and Version Microsoft Windows NT Server 5.2~IP Addresses
> 10.96.10.180~IP
> > > > Subnets 10.96.8.0~Resource Names
> > > > frsms.us.grundfos.com SMS_NETWORK_DISCOVERY 10/25/2004 1:05:36 PM 3120
> > > > (0x0C30)
> > > > DC: Exporting systems finished. SMS_NETWORK_DISCOVERY 10/25/2004
> 1:05:36
> > > > PM 3120 (0x0C30)
> > > > DC: Exporting networks... SMS_NETWORK_DISCOVERY 10/25/2004 1:05:36 PM
> 3120
> > > > (0x0C30)
> > > > ** DDR creation record **~Filename:
> > > > C:\SMS\inboxes\auth\ddm.box\nulz8s17.DDR~Device: IP Network~Device
> info:
> > > > Subnet Address 10.96.8.0~Subnet Mask
> > > > 255.255.252.0 SMS_NETWORK_DISCOVERY 10/25/2004 1:05:36 PM 3120
> (0x0C30)
> > > > DC: Exporting networks finished. SMS_NETWORK_DISCOVERY 10/25/2004
> 1:05:36
> > > > PM 3120 (0x0C30)
> > > > STATMSG: ID=1305 SEV=I LEV=M SOURCE="SMS Server"
> > > > COMP="SMS_NETWORK_DISCOVERY" SYS=FRSMS SITE=GMU PID=2116 TID=380
> GMTDATE=Mon
> > > > Oct 25 20:05:36.938 2004 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4=""
> > > > ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9=""
> > > > NUMATTRS=0 SMS_NETWORK_DISCOVERY 10/25/2004 1:05:36 PM 380 (0x017C)
> > > > DC: Shutting down protocol module
> > > > <AD_ADM.dll>. SMS_NETWORK_DISCOVERY 10/25/2004 1:05:36 PM 3120
> (0x0C30)
> > > > DC: Shutting down protocol module
> > > > <AD_SIM.dll>. SMS_NETWORK_DISCOVERY 10/25/2004 1:05:36 PM 3120
> (0x0C30)
> > > > DC: Shut down of protocol modules finished. SMS_NETWORK_DISCOVERY
> 10/25/2004
> > > > 1:05:36 PM 3120 (0x0C30)
> > > > DC: Discovery controller event sender thread shutdown. Thread ID
> > > > <0x00000E90> SMS_NETWORK_DISCOVERY 10/25/2004 1:05:37 PM 3728 (0x0E90)
> > > > DC: Discovery controller event listener thread shutdown. Thread ID
> > > > <0x00000C30> SMS_NETWORK_DISCOVERY 10/25/2004 1:05:38 PM 3120 (0x0C30)
> > > > DC: Network discovery completed and
> > > > shutdown. SMS_NETWORK_DISCOVERY 10/25/2004 1:05:38 PM 2444 (0x098C)
> > > > STATMSG: ID=1308 SEV=I LEV=M SOURCE="SMS Server"
> > > > COMP="SMS_NETWORK_DISCOVERY" SYS=FRSMS SITE=GMU PID=2116 TID=380
> GMTDATE=Mon
> > > > Oct 25 20:05:38.070 2004 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4=""
> > > > ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9=""
> > > > NUMATTRS=0 SMS_NETWORK_DISCOVERY 10/25/2004 1:05:38 PM 380 (0x017C)
> > > >
> > > > --
> > > > Kind regards,
> > > > Fred
>
>
>

Relevant Pages

  • Re: Network Discovery Stopped Working
    ... We have options Subnets, Domains, and SNMP enabled. ... But I am now wondering if it used SNMP to find the router. ... > I added an entry for the router in the SNMP Devices and discovery worked. ... I thought it should find the ARP table in the switch ...
    (microsoft.public.sms.admin)
  • RE: DSL Modem or Router Cracked?
    ... first set up my Linksys cable/DSL router, I noticed it was sending out quite ... a bit of SNMP trap traffic, it appeared to be a periodic update on the ... I seem to recall these packets being sent at a rate ... DSL Modem or Router Cracked? ...
    (Incidents)
  • Re: Linux vs LinkSys 4 port Cable router
    ... As far as SNMP logging is concerned, ... shed some light on this particular router. ... > It also doesn t talk about any of its SNMP capabilities. ...
    (comp.security.firewalls)
  • Re: Polling external router through SNMP
    ... I'm just using the basics of ISA, ... So do I just create an access rule for the SBS server to the router IP for SNMP protocol? ...
    (microsoft.public.windows.server.sbs)
  • Re: WRT54G v5.0 - limit data?
    ... Is there a way to on a monthly basis assign each mac address say 1gig? ... inside the router. ... If your WRT54G v5 could support SNMP, ... Dedicate a computer for data collection that is running full time. ...
    (alt.internet.wireless)
Quantcast