Installation Problems
I'm trying to setup Exchange Server 2007 on Windows Server 2008 R2. I'm having problems with the Exchange Transport Service which is failing to start. When I view the event logs I see two events coming up: Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=4868). Exchange Active Directory Provider failed to obtain DNS records for domain www.--------.com. DNS Priority and Weight for the Domain Controllers in this domain will be set to the default values 0 (priority) and 100 (weight). Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=4868). Exchange Active Directory Provider failed to obtain DNS records for forest DC=www,DC=---------,DC=com. DNS Priority and Weight for the Global Catalog servers in this forest will be set to the default values 0 (priority) and 100 (weight I've removed our domain name from the above messages for confidentiality reasons. So I get the feeling I have DNS issues. I'm slightly confused with the DNS side of things as to what I should be trying to achieve. We have purchased a domain name from 123Reg.co.uk. From 123Reg.co.uk we can control which IP Address the domain name points to, and also the MX record. Now having set up Active Directory that's forced me to create a DNS service on our server... Do I need to create Forward/Reverse lookup zones still on the DNS Server? Could use some help. I'm kind of digging around in the dark here a little. Thanks, Chris.
November 14th, 2010 1:58pm

On Sun, 14 Nov 2010 18:53:33 +0000, Mr ChriZ wrote: > > >I'm trying to setup Exchange Server 2007 on Windows Server 2008 R2. > >I'm having problems with the Exchange Transport Service which is failing to start. > >When I view the event logs I see two events coming up: > >Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=4868). Exchange Active Directory Provider failed to obtain DNS records for domain www.--------.com. DNS Priority and Weight for the Domain Controllers in this domain will be set to the default values 0 (priority) and 100 (weight). > >Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=4868). Exchange Active Directory Provider failed to obtain DNS records for forest DC=www,DC=---------,DC=com. DNS Priority and Weight for the Global Catalog servers in this forest will be set to the default values 0 (priority) and 100 (weight > >I've removed our domain name from the above messages for confidentiality reasons. > >So I get the feeling I have DNS issues. Your entire AD is named www.------.com ??? That's pretty unusual, isn't it? The "www" is usually associated with a URL assigned to a web site. >I'm slightly confused with the DNS side of things as to what I should be trying to achieve. > >We have purchased a domain name from 123Reg.co.uk. From 123Reg.co.uk we can control which IP Address the domain name points to, and also the MX record. > >Now having set up Active Directory that's forced me to create a DNS service on our server... The AD won't work with out DNS. Make sure things are right before you try installing Exchange. >Do I need to create Forward/Reverse lookup zones still on the DNS Server? You should have one for the forest already. Within the zone you should have other zones named _msdcs, _sites, _tcp, _udp, DomainDnsZones, and ForestDNSZones. >Could use some help. I'm kind of digging around in the dark here a little. Are you currently logged on to that domain on your workstation? Id so, start a command prompt and run "set". Look for the "USERDNSDOMAIN=whatever.com" in the output. That's the name of the domain. If the domain's name really is www.------.com then you certainly do have a DNS problem. But you'll have to use the management console's DNS snap-in to see what you've got in the DNS zones. Are you sure you don't have the DNS IP addresses on the Exchange server's NIC set to use some external DNS? The Exchange server's a domain-joined server, isn't it? Until the AD and DNS are right, trying to install Exchange is futile. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP
Free Windows Admin Tool Kit Click here and download it now
November 14th, 2010 3:21pm

OK when I run set those variables return: USERDNSDOMAIN=WWW.ourdomainname.COM USERDOMAIN=WWW So I'm guessing that's bad news. When setting up the first forest I'm guessing I should have just put in the ourdomainname bit?
November 14th, 2010 5:42pm

The Exchange server's a domain-joined server, isn't it? I'm not sure? What's the alternative? I only installed AD because Exchange requires it. Thanks Chris
Free Windows Admin Tool Kit Click here and download it now
November 14th, 2010 5:44pm

On Sun, 14 Nov 2010 22:38:45 +0000, Mr ChriZ wrote: >OK when I run set those variables return: > > > >USERDNSDOMAIN=WWW.ourdomainname.COM > >USERDOMAIN=WWW > >So I'm guessing that's bad news. No, not necessessarily. It's just unusual. The AD DNS domain name isn't the one that you'll expose to the Internet. Your account domain will e "www" so when you provide credentials it'll be "www\userid". >When setting up the first forest I'm guessing I should have just put in the ourdomainname bit? That's usually the case. Do you have any A or CNAME records in your DNS for the name "www.ourdomainname.com"? What about those other items I mentioned before? Are they in your DNS? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP
November 14th, 2010 9:45pm

On Sun, 14 Nov 2010 22:40:49 +0000, Mr ChriZ wrote: >>The Exchange server's a domain-joined server, isn't it? >I'm not sure? What's the alternative? There is none. >I only installed AD because Exchange requires it. If you're not that far into your deployment of the AD you might consider remving any machines that are joined to the domain and then DCPROMO the DC back to a regular old stand-alone server. Then DCPROMO it again and give the name of the domain as "ourdomainname.com" -- and remember that the name you use internally doesn't to bear any resemblence to the names you expose to the rest of the world. When you're satisfied that that your AD is named the way you want it and you can join a machine to it and log on using your credentials, then install Exchange. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP
Free Windows Admin Tool Kit Click here and download it now
November 14th, 2010 9:50pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics