Discovery problems

[Jonestown]

I have a small test network set up with a Windows 2003 server as my DC, a windows 2000 server as my SMS site server, and two clients - a windows xp pro and a windows 2000 pro. The only box that shows up in any Collections
is my Windows 2003 server (Domain Controller). I have every Discovery Method enabled, yet it won't discover either client PC.

The network is using static 10.10.1.X addresses. Name resolution is working properly. SMS is installed correctly as far as I can tell (i.e. the SMSLOGON share is present, all services started, etc.).

I have manually loaded the client on the windows xp client box. I let it search for my SMS site and it found it without any problems, but it still is not listed in any collections. So why can't my site server find my clients?

 

[ceigl]

Are the boundaries set correctly ?

Chris

 

[Jonestown]

As far as I can tell the boundaries are set up right. Doesn't the site server automatically set up a boundary for the subnet it is on? The only IP subnet on my Boundaries tab is "10.10.1.0". Shouldn't that work? What else could be wrong?

 

[DavidLeeRoth]

Has the sms client been on these client machines before? If so try removing the local sms accounts and any reference to sms from the registry on the client machines. The local accounts may be locking out the domain accounts (differing passwords) and preventing network discovery (this happened to me once).

 

[justcamcity]

You will need to query either a router's ARP cache or a DHCP server's database. I would suggest installing DHCP service on your test D.C and then add your scope, reservations, etc.
Keep in mind also that SMS depends on WINS, so it would be helpful to have a WINS server running as well.