Exchange Server

Nathan Kirkman · Guest

Hello -

We currently have Exchange Std. and I've been noticing that our database
size is rapidly increasing to the 16gb limit. I want to upgrade to
enterprise version, but I have several questions about the process.

First, we have our primary DNS server that will soon be replaced by a new
bigger/faster server. We tried to switch this before, but Exchange did not
like this too much. It couldn't mount the info store or start any of the
processes needed, until we brought the old DNS server back online. What
steps do I have to take to make Exchange point to the new DNS server? I
figure what better time to get this to work than when I'm upgrading.

Also, for the upgrade are there any necessary requirements for this process
to go smoothly? Thanks in advance.

Tony Murray · Guest

http://support.microsoft.com/?id=170280

Tony
www.activedir.org

"Nathan Kirkman" <NathanKirkman@discussions.microsoft.com> wrote in message
news:130A37E8-548E-4A22-A78A-CBFE813B00DD@microsoft.com...

Nathan Kirkman · Guest

Yes I found this link, looks like its that simple. Are there any ways to fix
the problem with switching DNS servers? Thats my main problem I'm worreid
about. I just need for Exchange to see the new DNS server w/o any problems.

"Tony Murray" wrote:

Ben Winzenz [Exchange MVP · Guest

I'm assuming Exchange 2000/2003 here, but you didn't say. If you are 5.5,
this doesn't really apply.

It depends on what kind of DNS server. In order for Exchange to work
properly, it needs to be able to find the AD DC's/GC's. That is done via
DNS. Is your current DNS server an Active-Directory integrated DNS server?
If so, my suggestion would be to simply add the new one as another
AD-integrated DNS server (which will result in the current DNS zone file
being "replicated" to the new server). Once all the information is on both,
you can change the DNS server on the IP settings of the NIC in the Exchange
server, and remove the first one.

--
Ben Winzenz
Exchange MVP

"Nathan Kirkman" <NathanKirkman@discussions.microsoft.com> wrote in message
news:6A2522D6-D5C2-4163-BCF7-5E284E4FF46B@microsoft.com...

Nathan Kirkman · Guest

Thanks for the response.

Yes I'm using 2003. Also the 'old' DNS server is AD integrated. I've
already set up the new server and it too is AD integrated. Could my DNS be
set up incorrectly then if thats why it's not working? Your response is what
I assumed, but when we took off the old DNS server and pointed the Exchange
server's DNS ip to the new server, it couldn't mount the info store because
it was looking for the old DNS server.

If I take off the old DNS server and point the Exchange server to the new
DNS server, will this correct the problem when I upgrade to Enterrpise?

"Ben Winzenz [Exchange MVP]" wrote:

Ben Winzenz [Exchange MVP · Guest

Upgrading to Enterprise won't change anything DNS-related. Are you sure you
changed the settings on the NIC properties? Doing that shouldn't even have
caused the stores to dismount. Have you made sure that the appropriate
zones have been created on the new DNS server? I.e. _msdcs, _sites, _tcp,
_udp...

Also, have you ensured that your DNS replication is set up to replicate
correctly to all servers? Are they set up to accept dynamic updates? Did
you try clearing the DNS cache from the Exchange server after re-pointing?
ipconfig /flushdns if memory serves me right.

--
Ben Winzenz
Exchange MVP

"Nathan Kirkman" <NathanKirkman@discussions.microsoft.com> wrote in message
news:40631E99-DF5F-491B-AC44-49C3E9F5E426@microsoft.com...

Nathan Kirkman · Guest

Thanks for the reply Ben.

Yes, I remember changing the DNS ip of the NIC to the new server. Let me
clarify somethings as well.

I setup the Exchange server up before I added the new 'soon-to-be' DNS server.
The current DNS server (which is what we are removing) is on Server2000. It
is set to be the primary DNS server as well. The new server is on Server2003
and I imported the dns entries from the current DNS server, so all of the
entries are there. Would running dcpromo on the new DNS server help with
this problem?

As for the information store process not starting, that happens after I
rebooted the Exchange server, figuring that that is what it might have needed
to see the new DNS server. I checked the event log and it says its looking
for the DNS server that we took offline. Wouldn't rebooting the server,
flush the cached dns entries stored on the server? Thanks again for the
help, hopefully we'll get this resolved.

"Ben Winzenz [Exchange MVP]" wrote:

Ben Winzenz [Exchange MVP · Guest

I guess the big question would be that if you go to the DNS management
console on the new server, and go to the properties of the zone, are you
sure it is an AD-integrated zone. You shouldn't have had to do an "import".
If it is AD-integrated, then the DNS zone information automatically gets
replicated amongst servers. I don't recall off the top of my head if you
can be running an AD-integrated zone on anything but a DC. I'd have to
check.

The other big question is...is the old DNS server also a Domain Controller?
What is the specific Event that Exchange logs? I'm just wondering if it is
truly DNS related, or if it is more along the lines of Exchange looking for
a Domain Controller.

--
Ben Winzenz
Exchange MVP

"Nathan Kirkman" <NathanKirkman@discussions.microsoft.com> wrote in message
news:59075F07-757A-4C21-AEBF-C1F5EA88FF4E@microsoft.com...

Nathan Kirkman · Guest

Yes the old DNS server is also a domain controller. I've checked DNS on the
new server and it is AD-integrated as well as the old dns server. I assumed
it was a dns issue, but it could be causing that error because it can't find
the controller. What I meant by "import" was zone-transfer. I transferred
all of the dns entries on the old dns server to the new dns server.

Several event log errors read:

-LDAP Bind was unsuccessful on directory 'dcname.domainname.local' for
distinguished name. Server down.
-NSPI Proxy cannot contact any Global Catalog that supports the NSPI service
-Win32 API call 'DSGetDCNameW' returned error code. Could not find
specified domain.
-All the DS Servers in the domain are not responding.

So I guess the new question is, how do I specify the new domain controller
for Exchange once I take the other down? Thanks in advance!

"Ben Winzenz [Exchange MVP]" wrote:

Ben Winzenz [Exchange MVP · Guest

Yeah - it isn't a DNS issue per-se, rather it is a problem with Exchange
being unable to find any Global Catalog servers. How many DC's do you have
in your environment? More importantly, how many of those DC's are Global
Catalog servers? Exchange should normally maintain a list of domain
controllers (and those that are GC's) and should automatically switch over
if there is more than one listed. You can find this list on the properties
of the server in Exchange System Manager. You will see a Directory Access
tab. If you want to manually change the DC it is looking to, you have to
use the drop down menu to select each role, then you can un-check the
"automatically discover" checkbox and change it to a different one.

I guess the most important point I'd make here is make sure that you have at
least 2 Domain controllers, and that both of them be Global Catalog servers.
In a single domain environment, there is no reason not to make all your DC's
GC's. Finally, on this topic, you will need to figure out which DC's are
hosting your FSMO roles. If you aren't sure where to look to find out which
servers are holding which roles, you can use the following document. In
your example, if the DC/DNS server was hosting some FSMO roles, that would
also cause problems. Make sure that it isn't hosting any of those roles
before you retire it. You might also simply consider removing/uninstalling
DNS from that computer, or leaving DNS active, but repointing all
servers/clients to the new server.
http://support.microsoft.com/kb/234790

--
Ben Winzenz
Exchange MVP

"Nathan Kirkman" <NathanKirkman@discussions.microsoft.com> wrote in message
news:077D7FA9-1BCB-4D9A-9B5A-176E0AFE6604@microsoft.com...

	Exchange Server Forum Index -> Administration	All times are GMT
Page 1 of 1