| Posted by firehawk1010, 03-11-2008, 08:42 PM | | im trying to install Exchange Server 2003 and going through the checklist. I have made my WS2003 EE R2 into a domain, has a manually configured DHCP/DNS (I have 2 IP's). I have also updated my NS on my domain to point to the hoster's NS.
but when running the tool i get this error and dont know how to resolve it:
|
| Posted by jfalcon, 03-12-2008, 12:45 PM | | It looks like the Active Directory DNS entries aren't set right (if they exist at all). What kind of BIND/DNS are you using?
|
| Posted by firehawk1010, 03-12-2008, 12:49 PM | | well all i did was create the server into an Active Directory following through the wizard, reboot and did the above.
The NIC/network settings i have entered manually since those are the settings given to me by the provider (hoster) as I have 2 IP's assigned to my account.
So I have manually entered DNS and IP Address and Subnet Mask info in order for it to be able to have network connectivity.
|
| Posted by jfalcon, 03-12-2008, 01:10 PM | | Ok... so it appears that it's not doing lookups directly against your AD's DNS server.
Check your NIC's DNS settings and make sure that it primary is pointing to the DNS server that you configured with Active Directory. Also check the eventlogs to make sure there are no DNS issues and that the service is running. If you're installing Exchange on a server that is also the DNS/AD server, you should set the DNS settings for the nic to preference 127.0.0.1 or the external IP of the server so that it loops back into itself.
|
| Posted by firehawk1010, 03-12-2008, 01:21 PM | | well im in the process of transferring my domain to the server - still waiting for DNS updates on that.
hmm now, the domain I set the server up with (say, abc.com) - the domain "abc.com" is in the process of having its DNS/namesevers updated.
Now, exchange will be running on the same server as the AD server. Does this help? What should I do?
in regards to the domain settings, I have changed the nameservers and also changed the "www" and "A" records to point to the IP Address of the server (the secondary IP Address)
does this help? Sorry, im new to all this
|
| Posted by firehawk1010, 03-12-2008, 01:31 PM | | this is the warning i get in the eventlogs:
??
|
| Posted by jfalcon, 03-12-2008, 01:35 PM | | Well, those parts don't matter as much as making sure that your server does lookups on it's own DNS server first (ie: 127.0.0.1 or the external facing IP).
Once you confirm that it's doing lookups against itself *first* you can continue your Exchange 2003 installation. The original error is talking about not being able to talk to your AD-Integrated DNS server. When you look at the extra subdomains in your AD-Integrated DNS server, you'll see what I'm talking about.
|
| Posted by jfalcon, 03-12-2008, 01:38 PM | | Right. I'd check your server properties (start-rtclick Mycomputer-properties) and make sure that it's showing the correct server name and domain. If it's a domain controller, it should have been set to a domain (since you can't change it once it's joined).
If what you see isn't correct, you'll have to demote your AD and make the changes then redo AD (dcpromo).
|
| Posted by firehawk1010, 03-12-2008, 03:17 PM | | hmmm sorry im still new to this and don't follow.
1) how do i get it to "talk to itself"? What exactly do I need to look for and configure?
in regards to the last error in the event logs.... when i right click on my computer > properties > Computer Name:
full computer name: computer-name.[domainName].co.uk
Domain: domainName.co.uk
|
| Posted by jfalcon, 03-12-2008, 07:47 PM | | Cool... so things are set in those respects.
Open your network adapter/tcp-ip properties.
Make sure under DNS Servers that either 127.0.0.1 is first on the list or the external (internet facing) IP is first. If not, add it and make sure that it's first in the lookup order.
|
| Posted by jfalcon, 03-12-2008, 07:48 PM | | You might also want to add [domainname].co.uk to the DNS suffix box in the same window as the DNS server just to associate the interface to your domain.
|
| Posted by firehawk1010, 03-13-2008, 06:55 AM | | the external IP is first on the list, followed by the second IP on the list.
and now added the [domainname].co.uk to the DNS Suffix box. (right click local network connections > properties > TCP/IP > Properties > Advanced > DNS Tab > "DNS Suffix for this connection: domainName.co.uk")
however running that tool, DCDiag, I still get the same error
|
| Posted by firehawk1010, 03-13-2008, 10:18 AM | | ok, im now getting a different result. the domain is now configured..... (the domain name). any ideas on what to do here:
|
| Posted by jfalcon, 03-13-2008, 07:05 PM | | Do you have the DHCP server running? In a hosted environment, you shouldn't be running this as it will cause havoc with others. Make sure it's not installed or at least not authorized to serve out IP's.
The first one was a warning so I'm not overly concerned about it. The only piece there to check is to make sure the DNS client cache is flushed so that it pulls only current info from your DNS server. ipconfig /flushdns
But I don't see any other problems why you couldn't continue installing Exchange 2003.
|
| Posted by firehawk1010, 03-13-2008, 09:10 PM | | I just cleared out all event log entries and just redid DCDiag - no errors at all now, but only that first warning
ill turn of DHCP now....
|
| Posted by firehawk1010, 03-13-2008, 09:21 PM | | ok, now running the netdiag tool and I get this failure.
remember, the 2 DNS Server IP's are configured static and provided by the hoster
Last edited by firehawk1010; 03-13-2008 at 09:24 PM.
|
|
 Add to Favourites
 Print this Article
|
