Free Microsoft Outlook Resources & Whitepapers

IPv6 / Windows 2003 Issues

My Exchange server fails to find the domain controller (localhost) when IPv6 is enabled. I have disabled IPv6, but I am using it and would like to be able to reenable it. This started after upgrading to SP1. Based on netdiag/ipconfig, I believe that it is attempting to use an IPv6 DNS server (ipconfig shows 3 invalid IPv6 addresses under DNS servers, althrough there are none configured) IS there a way to get rid of those? The server takes an hour to get past the "Applying Computer Settings" window on startup with both IPv6 and Exchange enabled, it dosen't do this if I disable either one.

Post your answer or comment

comments powered by Disqus
On I am maintaining a list of potential issues caused by
Windows 2003 SP1 relevant to Exchange:

Hope this helps any administrators in process of installing this important

If anyone comes across any confirmed issues missing from here please let me
know! Post to this thread or get in touch through the contact form:


Alexander Zammit
Software Development Consultant
Check out, the new MS Exchange Resource site at

I have a server that is housing about 400 user's files. This server is
holding folder redirection shares for desktop users (80% of the
systems on site), home directories (cough PST's cough) and is also
holding a network drive that holds some network applications. The
network has been experiencing network latency. Initially we thought
this to be a networking issue. We have since had a contractor on site
to network sniffs and it appears to be caused from one server, the one
mentioned above. He stated that the latency has to do with traffic
leaving the server is not getting to clients in a timely matter and
thus the network pauses.

We have other sites that have this configuration across the world and
do not run into this issue. I am struggling with getting a handle on
what this issue is from. I have looked at open files and they seem
higher than what i would expect but not beyond what i would typically
worry about.

I had this issue at our corp HQ with a file serving cluster but the
scale of users is much different.

I guess my question is does Windows 2003 x64 buy me anything with more
capacity with file sharing? I would think it would but i seem to
remember the issue is with connections timeouts and number off
connections in the paged pool maybe? if this changed in x64 with the
larger amount of addressable memory then that could be a possibility.

Does SP2 buy me anything with the Scalable Networking Pack being
included? It was something i saw in searching for my answer for what
the heck is going on.

Does a TCP offload engine by me anything? I have the capiblity with
the model server I have but never have used it. (Dell PE 2950 II )

Basically any help is needed because I know "tweaking" performance
settings with MS can take a while based on its a production server, I
cannot reboot the server every 20 minutes and I can't reproduce the
issue constantly.


Hi everybody,

I am struggling with a very weird problem. I have apache running on
Windows 2003 server. I have a simple Windows API C
(EnumFontFamiliesEx) program that all it does it lists all the fonts
installed on the system. When I run this program as a CGI application
through apache, I do not see ANY TrueType fonts. I see all other
OpenType fonts etc.

When I run the program as a standalone application i see all the
fonts. When I run apache as a standalone program and not a service I
see all the fonts. So this makes me think that it's an issue with the
service. Initially I thought it was a permissions issue, so I just
gave Everyone full access to the Fonts folder and all the fonts
inside. Same problem. When I recreate the scenario on Windows XP
everything is fine regardless how I run my test program... So this is
definitely a Windows 2003 problem.

Any help would be greatly appreciated. I've been googling for days now
to no avail.

Thanks for reading this :)

Andrzej Ciereszko
Software Engineer


I have Exchange 2003 Service Pack 1 installed on a Windows 2003 Domain Controller.  Windows Update is inidcating that the Windows Service Pack 1 needs to be installed. 

Is the installation of Windows 2003 Service Pack 1 going to create issues for Exchange.

Your thoughts on this would be greatly appreciated.


Hi folks,
anyone aware of any issues relating to the installation of exchange on Windows 2003 release 2?  I have heard of an instance of FORESTPREP failing.


im running a windows 2003 standalone server (I dont have front and backend servers).

I remebert that it required some hacks to get the owa working, and now im thinking about installing SP2.

But i want to know if there are any issues with sp2 and running standalone?

Anyone in here that has their exchange server set up the same way and has applied sp2?

Have a nice day

I had a Windows 2003 Server which was a Domain Controller over which Exchange Server 2003 was running, suddenly the server crashed i am not been able to start windows. The issue is most of the users email boxes are on this server now i want a recovery I have the drive with me suggeste me a better way.


This is probably more a Windows 2003 SP2 issue but...

We have an OWA server on a Front End server running Exchange 2003 SP2
Back-end servers are Exchange 2003 SP2

When I installed Windows Server 2003 SP2:
1. OWA no longer worked- could not access the page (due to point 2?) and errors in event viewer
2. IIS Manager did not show any servers in the list

I am logged in as Administrator of the Domain.


1. In IIS Manager, when I try to Connect to the server (Actions > Connect) I
receive the error:
You have been denied access to this machine

2. In Event Viewer > Application log I see the following errors:
Error 1009
Failed to access the metabase, error code is 80070005 (Access is denied.).

Error 1090
Windows couldn't log the RSoP (Resultant Set of Policies) session status. An
attempt to connect to WMI failed. No more RSoP logging will be done for this
application of policy.

Error 9097
The MAD Monitoring thread was unable to connect to WMI, error '0x80070005'.

3. In Event Viewer > System log, i see the error:
Service Control Manager
Error: 7023
The World Wide Web Publishing Service service terminated with the following
error:  Access is denied.

I uninstalled Windows Server 2003 SP2 and I had access again to IIS and OWA.

Any assistance is welcome in getting Service Pack 2 installed.


I have a exchange 2003 and Outlook 2003 on clients running windows xp.
Everything works fine. I have a client machine that is running windows 2003
and have outlook install. Before windows 2003 sp1 got released, outlook
worked fine. After applying windows 2003 sp1, Outlook stopped working.
it complains about Exchange server not being available.

After doing some search on MS site, there is a KB article that talks about
running security wizard configuration to roll back the security setting.
this cannot be done because SWC does not recognize the previous settings.
Also windows firewall is disabled.

Has anyone encountered this issue? Is there a fix for this?



I was wondering if somebody could help:

I have a customer with the following:

2 * Windows 2003 Servers running AD and DNS.

The main server is also running Exchange 2003, but needs to be rebuilt as
there is a system/software issue with it.

Is there a way of re-installing Windows 2003 and Exchange 2003 on the same
box, keeping the same name?

I saw articles where it isn't supported to demote AD on a box running
Exchange 2003, so I won't do that. Restoring the system state won't help,
as the issue may be related to the registry that is part of the system state


I have to migrate from Exchange 5.5 (on NT) to Exchange 2003 (on Win2003).

First I used ADC to move the Mailboxes from Windows NT to Windows
2003.Exchange 5.5 Server and Exchange 2003 Server are in different
After that I tried use Migration Wizard to Move Mailboxes from Exchange 5.5
to Exchange 2003(on NEW Organization).
But when I run Exchange server Migration Wizard I get the following error: "
Invalid server specified or you do not have permission required to complete
the operation". And occur the event id 7048 with the source MSExchangeMig.

The account that I'm using has administrator rights on Exchange 5.5.

What can I do?
Please :This is really urgent ,Need some expertise on this issue.

I have just inherited an Exchange 2003 enviorment with 1 2003 OWA frontend
server and 4 Exchange 2003 backend server, not clustered but all part of the
same farm. None of them have WINDOWS 2003 SP1 or Exchange SP1 installed.

What is the best way to proceed to get these service packs installed. I read
I need to update the frontend first, but what happens to the backend servers
if I do them one at a time. DOWNTIME is an issue so any information about
how long exchange sp 1 takes would be helpful. KB's are nice too. (i know
W2003 sp1 takes a little time)

no comment is too beneath me I dont want to miss anything.

Thanks, Mike


We have a native exchange 2003 org where all the servers are running
exchange 2003 SP1 on windows 2003. We are thinking on installing windows SP1
but are concerned with any issues they might be. We heard that installing
W2k3 SP1 on will cause a reindexing of the exchange store. Has any body
experience this or any other issues? Also, we have heard about the /PAE
switch issue...

Thanks in advance

I need to install Exchange 2003. It will involve a migration from the
company's current Exchange 2000 server running on Windows 2000. Would it be
less problematic to upgrade the whole network to Windows 2003 Server first,
then do the Exchange migration from 2000 to 2003? Are there known issues
with Exchange 2003 on Windows 2000?

In a small environment, is there any compelling reason to upgrade from
Windows 2000 to Windows 2003?


I am in the planning phases of migrating our NT 4.0 domains to Windows 2003.
I am planning on leaving the domains in Mixed mode until the end of the
year. This will give needed time for remote admins to migrate services from
their current NT domain controllers. The question that I have is as follows:
Will we have any issues when we install Exchange 2003 while still using
Mixed mode for our domains.

Thanks for any information.

Has anyone had any issues installing Exchange on a server with Windows 2003
SP1 already applied to it? I have had two separate incidents where the
Exchange services would become un-stable (not start at all, crash processes
etc...) after installing Exchange 2003 on a server with Windows 2003 SP1

I have not had any issues with installing Windows 2003 Sp1 after installing
Exchange SP1 on a server though.

Is there a process I should be aware of?


I want to install Exchnage 2003 on Windows 2003 Server SP1 32 bit
edition. Our 1 domain controller however is running the 64 bit edition
of Windows 2003 server.

When I ran forestprep I received the message "Exchange Server 2003 has
known compatiability issues with this version of Windows). But I ran
forest prep ont eh regular 32 bit W2k3 server so I am uncertain why I
woudl get this message.

I assuem it is refering to the domain controlerr's version of W2k3 which
is 64bit.

So what's the deal can I insatll Exchange 2003 onb W2k3 server 32-bit if
my DC is W2k3 64 bit?

Hi folks
I have a Windows NT 4 DOMAIN with One Windows NT PDC That is also hosting
Exchange 5.5 Server and THREE Windows NT BDC,S with 400 Workstations
connected to it.I want to do inplace upgrade from Windows NT to Windows
2003.The NT Domain has a WINS Service running without DNS.
My Plan is to take a new a Dell 2800 Power edge Server connect it to the
existing Windows NT Domain as BDC.Promote this NEW BDC as the PDC and demote
the existing PDC and Upgrade the New PDC to Windows 2003 Domain.
My question is:
1.Windows NT supports only 4BG for System Partation.How can i increase the
System Partation Size after Upgrading to Windows 2003 Domain.
2.How will i point my 400 workstations to Windows 2003 DNS, SINCE Existing
NT Domain does not have a DNS but it is running WINS.

Please provide me some details regarding this issue.

Fasahat Shafi.


I have Windows 2003 Server Enterprise Edition with Windows 2003 Service Pack
1 loaded. Now I am trying to load Exchange 2003 Server Enterprise Edition and
I get an error which says:

Exchange Server 2003 has a known compatibility issue with this version of
Windows. For more information, refer to

What is the solution for this problem?

Hi Everyone

I have a multi-site domain, each site with its own domain
controller/exchange server. I am conducting an in place (as in on the same
hardware) upgrade to Windows 2003 and Exchange 2003 from Windows 2000 and
Exchange 200. After perusing all the relevant documentation I come up with
the following upgrade path for each server (starting with the main server
which also holds all the FSMO's etc).

1. Ensure server meets minimum requirements (hardware and software) for
both upgrades.
2. Run Exchange 2003 Forest Prep & Wait for A/D to synchornise
3. Run Exchange 2003 Domain Prep & Wait for A/D to synchornise
4. Install Exchange 2003
5. Install Exchange 2003 SP1
6. Run Windows 2003 SP1 Adprep Forest Prep & Wait for A/D to synchronise
7. Run Windows 2003 SP1 Adprep Domain Prep & Wait for A/D to synchronise
8. Run Windows 2003 SP1 Adprep Domain Prep with gpprep & Wait for A/D to
9. Upgrade to Windows 2003 SP1

After completing this on the first server I would then perform steps 4, 5 &
9 on each subsequent server. The procedure sounds good and matches all
documentation I have found, so I started the upgrade process with the first

After completing steps 1-8 (but before 9) I started receiving the following
NDR's for any user on the server upgraded to Exchange 2003 when they
attempted to send messages to any user on an Exchange 2000 server, both
servers at this point are still running Windows 2000. Users on the Exchange
2000 server can still send messages to users on the Exchange 2003 server.

"There was a SMTP communication problem with the recipient's email server.
Please contact your system administrator.
" (I have edited out the server name).

I initially assumed that this was some kind of language or message body
formatting issue and I have:

1. Made sure that both Windows and Exchange have the same input locales
installed (English-Australia & English-US in this case).
2. Ensured that all code translation tables/pages are installed (they are)
3. Changed the character set under the internet message format ion global
setting from Western Europe (the default setting) to US-ASCII (as I had found
an obscure reference on google about the Western Europe character set
occasionally changing specific character sequences to NULL characters).

This however changed nothing.

I have temporarily resolved the issue by rolling back to the backup of the
system state prior to the adprep commands being run (steps 6-8), but this is
obviously not an optimum solution as it means I can not upgrade any of the
servers to Windows 2003.

Has anyone run across this problem, and got a solution for it.

Kind Regards

Drew Forscutt

To whom ever:

I have been testing an Outlook addin and we had to test some functions for a
mobile user. The administrator created a new user on the Windows 2003
Domain. This user was never on our Exchange 5.5 email server and was never
in the old NT domain. The user can access all folders on the Exchange 2003
Server but is unable to access the company calendar that is still on the
Exchange 5.5 server.

It appears to me to be some sort of authority issue but am not sure whee to

Any suggestions?

Thank you in advance

DW Gard

Hello. I am running a Windows 2000 Advanced Server SP4 system with Newly
upgraded Exchange 2003 Enterprise with SP1.
When I run the comptabily check for upgrading to Windows 2003 Enterprise I
get the following error:

Exchange Server 2003

Issue Description:

Exchange Server 2003 has a known compatibility issue with this version of
Windows. For more information, refer to

Contact Information:

Microsoft Web site:
Telephone: (425) 635-7172 (U.S.) or (905) 568-3503 (Canada)

After I go to the link I can see no problem that I should have if I want to
do the update. Any ideas? Thanks very much.


Hello all,

Dunno if this has already been stated but after applying Service Pack 1 on
computer running Windows 2003 as client OS (before you comment anything,
keep in mind many may use Windows 2003 as a host OS for Citrix for example).
I know new security settings are enabled but still can't figure out what to
fix to let Outlook work correctly.

Is someone able to help me with this issue ?


has anyone used Windows 2003 Server SP1 as the client system? I have an issue when I try to connect my outlook 2003 via RPC over HTTPS to my server. I get the check name to work after I type in the password about 10 times however I do not connect to my server at all.

Does any of the new RPC and DCOM issues have to do with this?

Any ideas?

Not finding an answer? Try a Google search.