Re: SMS 2003 Network Discovery

From: Darren Brinksneader (anonymous_at_discussions.microsoft.com)
Date: 08/03/04 

Date: Tue, 3 Aug 2004 13:45:45 -0700

I am not trying to push clients yet. With SNMP discovery
turned on, servers on the local subnet (with snmp
installed) are discovered and populated into the
appropriate collections. Any system on the local subnet
or on remote subnets, without the snmp service installed
are not getting DDR's generated.

Here is an example:

The first system listed is a server on the same subnet as
the SMS Site Server and has the SNMP service installed:

********** System that get DDR generated *********
ExportDevice <172.22.2.98 255.255.254.0>
        SMS_NETWORK_DISCOVERY 8/3/2004 4:20:06 PM
        2748 (0x0ABC)
HMC-HSM-INF is not in any AD Site.
        SMS_NETWORK_DISCOVERY 8/3/2004 4:20:06 PM
        2748 (0x0ABC)
** DDR creation record **~Filename:
D:\SMS\inboxes\ddm.box\6qq1kf5p.DDR~Device: System~Device
info: NetBIOS Name HMC-HSM-INF~Resource Domain OR
Workgroup HMC_DOMAIN~Operating System Name and Version
Microsoft Windows NT Server 5.0~SNMP Community Name
public~IP Addresses 172.22.2.98~IP Subnets
172.22.2.0~Resource Names HMC-HSM-INF~MAC Addresses
00:0B:CD:03:D9:73 SMS_NETWORK_DISCOVERY 8/3/2004
4:20:06 PM 2748 (0x0ABC)
********** End System that get DDR generated *********

Even though is states "HMC-HSM-INF is not in any AD Site"
it still generates a DDR because of the SNMP.

The next system is queried by the SMS_NETWORK_DISCOVERY
as you can see it gets info back from the system, but
when it tries to export the device to generate a DDR it
fails and states "PLANAR-0001743 is not in any AD Site".
So, it never gets populated into a collection.

********** System that doesn't get DDR generated *********
ADM: NtBrowser: Starting to talk to Device PLANAR-0001743
        SMS_NETWORK_DISCOVERY 8/3/2004 4:16:48 PM
        2084 (0x0824)
ADM: NtBrowser: Device PLANAR-0001743, reported name
PLANAR-0001743, reported OS Microsoft Windows NT
Workstation version 5.0, machine type information: LAN
Manager workstations|LAN Manager servers|Windows NT
(either Workstation or Server)|Server that can run the
Browser service|All servers SMS_NETWORK_DISCOVERY
        8/3/2004 4:16:48 PM 2084 (0x0824)
DC: Device reported by REPLY_SYSTEM_INFORMATION
<172.22.8.127> SMS_NETWORK_DISCOVERY 8/3/2004 4:16:48
PM 2084 (0x0824)

ExportDevice <172.22.8.127> SMS_NETWORK_DISCOVERY
        8/3/2004 4:19:00 PM 2748 (0x0ABC)
PLANAR-0001743 is not in any AD Site.
        SMS_NETWORK_DISCOVERY 8/3/2004 4:19:01 PM
        2748 (0x0ABC)

********** End System that doesn't get DDR generated
*********

Since I am in an NT 4.0 domain, I obviously am not in any
AD site.

The site server is in "Standard Security" and is pointed
to a WINS server in it's IP properties.

Any ideas? If you want a full log, I can send you one,
but it is large because I am trying to discover nearly
700 systems.

>-----Original Message-----
>Please attach more of the log.
>What do you mean it is not processing the DDR's? DO you
have push enabled?
>Are you just trying to discover the machines? Are you
collections not
>populating?
>
>--
>Thanks,
>Jeff Harbaugh [MSFT]
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>"Darren Brinksneader"
<anonymous@discussions.microsoft.com> wrote in message
>news:baeb01c47992$433f1410$a401280a@phx.gbl...
>>I have a newly installed SMS 2003 Primary Site intalled
>> on Windows 2003 as a member server in a Windows NT 4.0
>> Domain (Single Domain).
>>
>> I can watch the SMS_NETWORK_DISCOVERY in SMS Trace. I
>> cac see it query systems and get a response.
>>
>> It gets to "Exporting Systems...." in the log
>>
>> this is what I see when it tries to create the DDR...
>> Sample:
>> ExportDevice <172.22.20.126> SMS_NETWORK_DISCOVERY
>> 8/3/2004 3:39:04 PM 2216 (0x08A8)
>> 016Y8 is not in any AD Site. SMS_NETWORK_DISCOVERY
>> 8/3/2004 3:39:04 PM 2216 (0x08A8)
>>
>>
>> this happens for every system except for the Site
Server
>> and some routers it discovered.
>>
>> I have the Site Boundaries and Discovery subnets setup
to
>> encompass all the subnets. It is obviously discovering
>> the systems, it is not generating the DDRs.
>>
>> Help!
>>
>
>
>.
>

Relevant Pages

  • Re: SMS 2003 Network Discovery
    ... > or on remote subnets, ... > The first system listed is a server on the same subnet as ... > it still generates a DDR because of the SNMP. ... >>> I have the Site Boundaries and Discovery subnets setup ...
    (microsoft.public.sms.admin)
  • Re: SMS 2003 Network Discovery
    ... servers on the local subnet (with snmp ... >>> or on remote subnets, ... >>> the SMS Site Server and has the SNMP service installed: ... I have the Site Boundaries and Discovery subnets ...
    (microsoft.public.sms.admin)
  • Re: SMS 2003 Network Discovery
    ... servers on the local subnet (with snmp ... Any system on the local subnet ... >> The first system listed is a server on the same subnet ...
    (microsoft.public.sms.admin)
  • Re: Network discovery Problems
    ... * Arp tables on the routers (usually the site server doesn't have access ... snmp agent installed not ideal neither. ... To cut a long story short, Network discovery is a powerfull but not easy ...
    (microsoft.public.sms.setup)
  • RE: Anonymizing Packets yet ensuring 0 % packet loss
    ... IBM, SUN SOLARIS, CISCO & MICROSOFT ... Tor is an open network you can use for this - this is frowned upon by Tor ... exit server traffic and block them the minute they see probes/attacks from ... enumerate the services, administration subnets, department subnets, ...
    (Pen-Test)
Loading