Rex_Ger Posted September 23, 2009 Report post Posted September 23, 2009 Hey Guys, I have two test server in an virtual environment. The first server is an Windows Server 2008 DC Controller; Only DC and DNS is installed. I havent done anything to the DNS-Server, it is "out of the dcpromo.exe box". The second server is an 2008 Server too, DPM 2007 (official ms trial version) installed, without any (!!!) errors. For faster testing, i disabled on both the firewall completly. I did everything like the first and second tutorial said, the agent was installed perfectly on the DC. But when i came to the step for activating the end-user-recovery (when clicking "configuring active directory), it says, that the active directory cant be configured, because the domain can not be found... i can ping the dc without problems. The SchemaExtend-Tool has same problem, andybody has a solution or idea how i can fix it and get it working? kind regards Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted September 23, 2009 Report post Posted September 23, 2009 verify dns is working properly first, do an nslookup test paste the results of nslookup here Quote Share this post Link to post Share on other sites More sharing options...
Rex_Ger Posted September 23, 2009 Report post Posted September 23, 2009 Hi, thanks for the fast reply! I have to say, i havent did much with DNS and i dont know much about it! here the nslookup results: C:\Users\Administrator.TEST>nslookup TestDPMdc1.test.local Server: UnKnown Address: 100.100.100.10 Name: TestDPMdc1.test.local Address: 100.100.100.10 C:\Users\Administrator.TEST>nslookup TestDPMdc1 DNS request timed out. timeout was 2 seconds. Server: UnKnown Address: 100.100.100.10 Name: TestDPMdc1.test.local Address: 100.100.100.10 C:\Users\Administrator.TEST> C:\Users\Administrator.TEST>ping TestDPMdc1 Ping wird ausgeführt für TestDPMdc1.test.local [100.100.100.10] mit 32 Bytes Dat en: Antwort von 100.100.100.10: Bytes=32 Zeit=1ms TTL=128 C:\Users\Administrator.TEST>ipconfig /all Windows-IP-Konfiguration Hostname . . . . . . . . . . . . : TestDPMbu1 Primäres DNS-Suffix . . . . . . . : test.local Knotentyp . . . . . . . . . . . . : Hybrid IP-Routing aktiviert . . . . . . : Nein WINS-Proxy aktiviert . . . . . . : Nein DNS-Suffixsuchliste . . . . . . . : test.local Ethernet-Adapter LAN-Verbindung: Verbindungsspezifisches DNS-Suffix: Beschreibung. . . . . . . . . . . : Intel® PRO/1000 MT-Netzwerkverbindung Physikalische Adresse . . . . . . : 00-0C-29-0C-04-97 DHCP aktiviert. . . . . . . . . . : Nein Autokonfiguration aktiviert . . . : Ja IPv4-Adresse . . . . . . . . . . : 100.100.100.20(Bevorzugt) Subnetzmaske . . . . . . . . . . : 255.255.255.0 Standardgateway . . . . . . . . . : DNS-Server . . . . . . . . . . . : 100.100.100.10 NetBIOS über TCP/IP . . . . . . . : Aktiviert Tunneladapter LAN-Verbindung*: Medienstatus. . . . . . . . . . . : Medium getrennt Verbindungsspezifisches DNS-Suffix: Beschreibung. . . . . . . . . . . : isatap.{03B09239-61D7-44A9-AE67-70DB3C160 D8D} Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0 DHCP aktiviert. . . . . . . . . . : Nein Autokonfiguration aktiviert . . . : Ja Tunneladapter LAN-Verbindung* 8: Verbindungsspezifisches DNS-Suffix: Beschreibung. . . . . . . . . . . : 6TO4 Adapter Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0 DHCP aktiviert. . . . . . . . . . : Nein Autokonfiguration aktiviert . . . : Ja IPv6-Adresse. . . . . . . . . . . : 2002:6464:6414::6464:6414(Bevorzugt) Standardgateway . . . . . . . . . : 2002:c058:6301::c058:6301 DNS-Server . . . . . . . . . . . : 100.100.100.10 NetBIOS über TCP/IP . . . . . . . : Deaktiviert C:\Users\Administrator.TEST> Edit: I googled a bit around and have now configured a Reverse-Lookup-Zone, now nslookup has better result: C:\Users\Administrator.TEST>nslookup testDPMdc1 Server: testdpmdc1.test.local Address: 100.100.100.10 Name: testDPMdc1.test.local Address: 100.100.100.10 C:\Users\Administrator.TEST>nslookup testDPMdc1.test.local Server: testdpmdc1.test.local Address: 100.100.100.10 Name: testDPMdc1.test.local Address: 100.100.100.10 Quote Share this post Link to post Share on other sites More sharing options...
Rex_Ger Posted September 23, 2009 Report post Posted September 23, 2009 Solution: Start the C:\Program Files\Microsoft DPM\DPM\End User Recovery\DPMADSchemaExtension.exe Tool directly on the DC and everything is working.... Quote Share this post Link to post Share on other sites More sharing options...