Re: SMS 2003 Network Discovery

From: LaDawn (meandkaylab_at_cs.com)
Date: 08/04/04 

Date: Tue, 3 Aug 2004 23:18:19 -0400

Sean,

I am experiencing the same issue. SMS 2003 on W2K3 server, running Standard
Security, but we use Static IP Address. The MP and SLP have been added into
WINS, but my logs with "search" my domain and generate the message,
"<machinename> not in any AD Site", but will create, if I am lucky, one DDR.

I think the question is how can/ why does SMS discover and create a DDR for
one machine that is on the same subnet and have the same subnet mask as 30
others, but only one machine is discovered and a DDR created.

Dawn

"Sean Chitwood [MSFT]" <seanchit@online.microsoft.com> wrote in message
news:#VMtX8aeEHA.3124@TK2MSFTNGP09.phx.gbl...
> Darren--
> The reason it can't find which AD site that the systems are in is
> because they are not in any. AD was introduced in Win2K as a new model for
> creating domains. However that is not why the DDRs are not being created.
We
> need the IP subnet in order to assign to the site. Since we aren't getting
> the subnet mask (And thus the subnet), we aren't creating the DDR.
>
> Now, are you running standard or advanced security? If you are running
> standard all we need to do is point Network Discovery to the DHCP server.
> Network discovery works best when it is hitting the DHCP server. If you
are
> running Advanced security, we are in a bit of a bind. See the machine
> account cannot contact the DHCP server for security reasons, so an
advanced
> security site is blocked from the most efficient portion of Network
> discovery and is better off using AD System discovery, which is pointless
in
> an NT4 domain.
>
> --Sean
>
> --
> ------------------------------------------
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Darren Brinksneader" <anonymous@discussions.microsoft.com> wrote in
message
> news:bc0a01c479a0$fa8190e0$a401280a@phx.gbl...
> >I have done three other installs of SMS and have never
> > run into this before. The only difference is that the
> > other installs were in Windows 2000 or 2003 AD
> > environments, this is NT 4.0 Domain.
> >
> > One thing I did notice is that for the devices discovered
> > via SNMP have the following:
> >
> > ExportDevice <172.22.2.108 255.255.254.0>
> > SMS_NETWORK_DISCOVERY 8/3/2004 5:21:56 PM
> > 3760 (0x0EB0)
> >
> > where it shows the net mask the others don't:
> >
> > ExportDevice <172.21.4.144> SMS_NETWORK_DISCOVERY
> > 8/3/2004 5:21:58 PM 3760 (0x0EB0)
> >
> >
> >
> >>-----Original Message-----
> >>We are just logging that it is not in AD. This has
> > nothing to do with
> >>processing the DDR. If we find the system that we can
> > get the IP information
> >>we will populate the database.
> >>
> >>--
> >>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:b83101c4799a$d9beef70$a601280a@phx.gbl...
> >>>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

  • SunPCi II VNC weak authentication scheme vulnerability
    ... Trust Factory Security Advisory TF20020601 ... Discovery Date: June 2, 2002 ... copy of AT&T's Virtual Network Computing client and server. ... the modifications is the authorization process between VNC client and VNC ...
    (Bugtraq)
  • [VulnWatch] SunPCi II VNC weak authentication scheme vulnerability
    ... Trust Factory Security Advisory TF20020601 ... Discovery Date: June 2, 2002 ... copy of AT&T's Virtual Network Computing client and server. ... the modifications is the authorization process between VNC client and VNC ...
    (VulnWatch)
  • Re: SMS 2003 Network Discovery
    ... the subnet mask, we aren't creating the DDR. ... Network discovery works best when it is hitting the DHCP server. ...
    (microsoft.public.sms.admin)
  • Re: Incomplete Network Dircovery of SMS 2003
    ... We dont use MS DHCP servers and dont have snmp installed on the ... We do have snmp on our server and after about 72 hours it discovered these. ... > Q. Why can't I configure DHCP options for network discovery? ... > running advanced security. ...
    (microsoft.public.sms.setup)
  • Re: SMS 2003 Network Discovery
    ... With SNMP discovery ... or on remote subnets, ... The first system listed is a server on the same subnet as ... >> I have the Site Boundaries and Discovery subnets setup ...
    (microsoft.public.sms.admin)