Admin Console Crashes with active directory Discovery

MarkH · April 10, 2010

Right off, I am new to SCCM 2007 R2. The setup was done in a test environment. After installing windows server 2003 sp2 on 2 computer's, I made one a DC with dns, & dhcp. The other pc I installed sql 2005 with sp3 and SCCM 2007 R2. I extended the schema on the dc and varified it by looking at log files. I then ran through the sccm 2007 r2 pre-requirements and satified them all, but it still showed schema as not extended. The sccm 2007 pc is a member of the dc pc domain. The account I am useing is the built in administrator account on the dc with domain admin, ent admin rights and schema rights. I am useing dhcp to assign ip. After completing the sccm setup I started setting up the discovery zones, etc. I was able to setup all discovery methods except active directory discoveries. When I tried to do this the admin console hung for about a minute and then errored out and suggested I restart the console. It sounds like sccm 2007 can't find the domain or communicate/authenticate with My DC.

How can the Schema show being extended on the dc side and not in sccm pre-requirements, other windows server 2003 pc?

Help is greatly appreciated.

Thanks,

Mark

anyweb · April 10, 2010

first thing i always check is DNS, so does nslookup return a correct result from the SCCM box ?

MarkH · April 11, 2010

I can ping host name or ip of the dc and sccm pc from either pc, although it is slow to ping the sccm pc. If I use ping -a server name it resolves fine. If I use ping -a ip it resolves fine to a hostname.If I do a nslookup ip address of either sccm or dc server it resolves to a hostname and works. If I do a nslookup of the host name of either sccm or dc server it resolves to a hostname and but doesn't work and times out. I have my DNS server to pull from dhcp server which is on the same pc. Both servers I have register dns on bootup in network properties. I have the gateway configured, which is the dc. I have set the netbios setting to default or to come from the dhcp and to use netbios over tcp/ip if not avaliable.

Thanks for your help,

mark

MarkH · April 12, 2010

error.docDNS Event:

The zone 100.100.192.in-addr.arpa is configured to accept updates but the A record for the primary server in the zone's SOA record is not available on this DNS server. This may indicate a configuration problem. If the address of the primary server for the zone cannot be resolved DNS clients will be unable to locate a server to accept updates for this zone. This will cause DNS clients to be unable to perform DNS updates.

dcdiag

Domain Controller Diagnosis

Performing initial setup:

Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\ADPC

Starting test: Connectivity

The host 1ad0a9c5-ebc0-4572-bf3b-1f9ff3cac2a3._msdcs.BandAid.com could

not be resolved to an

IP address. Check the DNS server, DHCP, server name, etc

Although the Guid DNS name

(1ad0a9c5-ebc0-4572-bf3b-1f9ff3cac2a3._msdcs.BandAid.com) couldn't be

resolved, the server name (adpc.BandAid.com) resolved to the IP

address (192.100.100.100) and was pingable. Check that the IP address

is registered correctly with the DNS server.

......................... ADPC failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\ADPC

Skipping all tests, because server ADPC is

not responding to directory service requests

Running partition tests on : ForestDnsZones