I've got most of the problems resolved, but still no luck with Exchange. Netdiag is clean & dcdiag is clean. Replmon shows full replication. All of the SRV records are now showing up in the wbgkent.com DNS zone on the wbgkent.com DCs. The kpassword SRV record is still missing for the wbgkent.com 2003 DC on the wrightbg.com DCs, which is where I'm installing Exchange. These are all AD-integrated zones. I've tried reloading the zones, but it didn't help. Exchange setup still can't find the wbgkent.com domain. I think I need a high-energy lunch. Steve
_____ From: Andy Shook [mailto:[EMAIL PROTECTED] Sent: Monday, December 31, 2007 9:50 AM To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 install problem - DNS? No problem, homey; that's what we're here for. Do you need help researching these errors? Shook http://www.linkedin.com/in/andyshook _____ From: Steve Hart [mailto:[EMAIL PROTECTED] Sent: Monday, December 31, 2007 12:44 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 install problem - DNS? Should have thought of that. I guess I was working too late last night. Turns out there are big errors that explain teh Exchaneg problem. Domain Controller Diagnosis Performing initial setup: Done gathering initial info. Doing initial required tests Testing server: Portland\KENT-DC03TEMP Starting test: Connectivity The host 27dabf5f-5831-496a-8105-74914fb4bb71._msdcs.wrightbg.com could not be resolved to an IP address. Check the DNS server, DHCP, server name, etc Although the Guid DNS name (27dabf5f-5831-496a-8105-74914fb4bb71._msdcs.wrightbg.com) couldn't be resolved, the server name (kent-dc03Temp.wbgkent.com) resolved to the IP address (10.10.10.17) and was pingable. Check that the IP address is registered correctly with the DNS server. ......................... KENT-DC03TEMP failed test Connectivity Doing primary tests Testing server: Portland\KENT-DC03TEMP Skipping all tests, because server KENT-DC03TEMP is not responding to directory service requests Running partition tests on : DomainDnsZones Starting test: CrossRefValidation ......................... DomainDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... DomainDnsZones passed test CheckSDRefDom Running partition tests on : ForestDnsZones Starting test: CrossRefValidation ......................... ForestDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... ForestDnsZones passed test CheckSDRefDom Running partition tests on : wbgkent Starting test: CrossRefValidation ......................... wbgkent passed test CrossRefValidation Starting test: CheckSDRefDom ......................... wbgkent passed test CheckSDRefDom Running partition tests on : Schema Starting test: CrossRefValidation ......................... Schema passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Schema passed test CheckSDRefDom Running partition tests on : Configuration Starting test: CrossRefValidation ......................... Configuration passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Configuration passed test CheckSDRefDom Running enterprise tests on : wrightbg.com Starting test: Intersite ......................... wrightbg.com passed test Intersite Starting test: FsmoCheck Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355 A Global Catalog Server could not be located - All GC's are down. ......................... wrightbg.com failed test FsmoCheck Now I'm off to figure out why these errors are here. Steve _____ From: Andy Shook [mailto:[EMAIL PROTECTED] Sent: Monday, December 31, 2007 9:30 AM To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 install problem - DNS? If you run DCDIAG on the wbgkent.com DC, does it throw any errors? Shook http://www.linkedin.com/in/andyshook _____ From: Steve Hart [mailto:[EMAIL PROTECTED] Sent: Monday, December 31, 2007 11:53 AM To: MS-Exchange Admin Issues Subject: Exchange 2007 install problem - DNS? I'm starting my first Exchange 2007 install and I've run across a problem. Business demands and spending restrictions have unfortunately left our network in transition all over the place. The domain that I'm installing in is Win 2003, with two 2003 DCs, including a GC, both running DNS. We also have two trusted domains each with a single 2003 DC and two 2000 DCs, one of which is a GC. In the trusted domains, the 2000 servers are running DNS. Each of the 3 domains has it's own Exchange 2000 server. I'm running setup.com /pl and it's throwing an error that one of the trusted domains (wbgkent.com) is unreachable. The other trusted domain seems OK. My first instinct is DNS. When I compared all of the SRV records, I found that the 2003 DC in the wbgkent.com domain was missing most or all of the SRV records in DNS. ipconfig /registerdns didn't help. netdiag/fix added some of the missing records, but others failed to add I added the appropriate ldap and kerberos records manually. It's also missing kpassword records, but I'm not sure how to add those. Still no luck on the Exchange setup. I installed DNS Server on the 2003 DC in question, but that hasn't solved the problem either. Ideas? Steve ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
