Solved

Moving Exchange mailboxes

Posted on 2011-03-02
3
256 Views
Last Modified: 2012-05-11
Setup a member server in a 2003 domain with Exchange 2003 to migrate Exchange off of our DC.  Followed Microsoft's article 822931 to replicate PF's, OAB, etc.  Let that run for a day or two and then moved a couple test mailboxes.  Cannot login through OWA to the new member server were the test mailboxes reside and access.  Have to first login to the DC (which Exchange is still running on as well) and then it prompts me to login again to our member server seems something is amiss with the authentication.  Hopefully you can help!
Thanks
Bill
0
Comment
Question by:Webcc
  • 2
3 Comments
 
LVL 12

Expert Comment

by:mlongoh
ID: 35021431
How are you trying to run OWA (using server name in URL?).  The double authentication is strange, but more details might make it clearer.

Also, I'm assuming that you don't have a front-end server handling OWA requests and that the only 2 servers running Exchange are the DC and the new box?
0
 

Author Comment

by:Webcc
ID: 35023387
http://IP-ADDRESS/exchange
Will not authenticate when I plug in the member server's address just keeps popping up the username/password dialog box.   What I just found out is that when instead I use the FQDN it works just fine instead of the IP Address (192.168.2.240) - !!!!!  Not sure what's happening there.  Need to test from a workstation using Outlook, will do tonight.
0
 
LVL 12

Accepted Solution

by:
mlongoh earned 500 total points
ID: 35028311
I found in the past that I had to specify the server's name in the URL when initially testing, and once I was ready to implement into production I had to update DNS to point to the new server's IP address (and/or reconfigure NAT on the firewall to point the public IP address for the mail server to the new server) and configure IIS on the new server with the domain names.  It's been awhile so I don't recall the details, but you're definitely on the right track by NOT using the IP address in the URL.
0

Featured Post

The curse of the end user strikes again      

You’ve updated all your end user’s email signatures. Hooray! But guess what? They’re playing around with the HTML, adding stupid taglines and ruining the imagery. Find out how you can save your signatures from end users today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
Disabling the Directory Sync Service Account in Office 365 will stop directory synchronization from working.
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…

919 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

23 Experts available now in Live!

Get 1:1 Help Now