Re: Certain Subnets not found!

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Richard Threlkeld (pleasenospam_at_hotmail.com)
Date: 06/10/04 

Date: Wed, 9 Jun 2004 22:15:17 -0700

I need a bit more information. What Discovery Method are you using? It
sounds like you are saying that Network Discovery can't see the 3 remote
subnets correct? SMS has issues talking to some routers and you might need
to enter a Read-Only SNMP community string to walk through the routing table
in order to get those remote subnets.

AD System Discovery can still be run and not effect Network Discovery. 

--
Richard Threlkeld
Microsoft MVP - SMS
Management Blog: http://www.msmvps.com/Threlkeld/
Join the SMS email discussion list today:
http://lists.listleague.com/mailman/listinfo/mssms
"QBob" <notaspammer@hotmail.com> wrote in message
news:OC78TJjTEHA.1548@TK2MSFTNGP11.phx.gbl...
> Okay, there has to be some SMS admins or MS employees that have seen this
> issue.  I am reposting again hoping that people either never saw it before
> or maybe I did not explain it well enough.  Thanks for reading.
>
> My situation is this.  I have 10 subnets...they are all 134.197.X.X  7 of
my
> subnets are on this side of my 4500 router and are all discovered fine, no
> manual configuration required.  However, my 3 subnets that are remote or
on
> the other side of my router are not found...even though they follow the
> identical subnet scheme and mask (minus the third octet of course).
> These remote sites are all a part of my (ONE) local domain and I can ping
> the devices, remote control the devices and see them in my network
> neighborhood.  They are a part of my AD and they are referenced in one of
my
> DNS servers.
> Currently I have been trying to tell SMS how to get to these devices by
> saying now look at 134.197.0.0  then tell it to look at 134.197.0.1 then
to
> 134.197.0.2  then to 10.1.0.0 then to 10.1.0.1 then to 10.1.0.2 then back
to
> 134.197.X.X for whatever the acutal subnet may be on the other side of the
> router ports...this has worked to help me discover more, but I still can
not
> see them...any ideas or thoughts?
>
> What if I just turn on AD System Discovery?  Will this solve my problem or
> could I run into potential issues down the road?
>
> Should I just keep trying to tell SMS how to get there?  Is there some
port
> or protocol or something that I can open up on my router to remain secure,
> but get this done?
>
> Thanks again, sorry for the long post.  Any assistance or ideas greatly
> appreciated.
>
>

Relevant Pages

  • Re: Discovery problem
    ... Pass-through *may* work but is not reliable everywhere and not really ... The remote domain does not need schema extensions unless you intend to ... I would suggest establishing the trust and making sure the SMS service ... As the discovery process seems to hang I ...
    (microsoft.public.sms.setup)
  • Re: Discovery problem
    ... SMS uses explicitly the service account for discovery. ... A trust is required to discover resources in a remote forest, ...
    (microsoft.public.sms.setup)
  • Re: Discovery problem
    ... I got network discovery to work (either by selecting 'Slow Network' ... > "SMS cannot connect to the Active Directory container you specified. ... > * Which user account does SMS use when querying the remote AD? ...
    (microsoft.public.sms.setup)
  • Re: Overlapping IP subnets
    ... Do you have these subnets configured in Active Directory Sites & ... Have you ran AD System discovery after configuring these AD Sites 1 ... Sms Active directory system discovery can only find out your ip address ... wait for heartbeat discovery but that requires a functional sms client). ...
    (microsoft.public.sms.admin)
  • Re: Certain Subnets not found!
    ... What Discovery Method are you using? ... in order to get those remote subnets. ... Microsoft MVP - SMS ...
    (microsoft.public.sms.setup)