Solved

Exchange 5.5 to Exchange 2003 Migration - Clients cannot receive mail after moving mailboxes.

Posted on 2004-03-24
7
191 Views
Last Modified: 2010-04-11
Hi,

My organization currently has one Exchange 5.5 server running on NT 4.0 Platform. We have already upgraded our NT 4.0 Domain to Windows Server 2003 ADS. Now we have introduced another Windows 2003 Server in which we going to use to migrate over to Exchange 2003 from the old Exchange 5.5 server.

The installation of Exchange 2003 went smoothly with no errors but I change the LDAP port on the Exchange 5.5  server from 389 to 390. I didn't want it to interfere with the Active Directory. The ADC connection went well too. Now here's my problem. In the process of moving mail boxes over to Exchange 2003, all the mailboxes that reside in this new server can only send mail and not receive mail. I know it must be something silly, but show do I fix it so that mailboxes on the new Exchange 2003 server can receive emails?
0
Comment
Question by:vicrod3315
7 Comments
 
LVL 15

Expert Comment

by:mattisflones
ID: 10674132
Hi vicrod3315,
Here are some guides/articles on the subject..
http://support.microsoft.com/default.aspx?scid=kb;en-us;288593
http://support.microsoft.com/default.aspx?scid=kb;en-us;260973
http://support.microsoft.com/default.aspx?scid=kb;en-us;821832
Please look @ and post back here with any results..

Mattis
0
 

Expert Comment

by:blackss
ID: 10674552
check your mx reords in DNS...
0
 

Author Comment

by:vicrod3315
ID: 10680973
Blackss  how is DNS going to help me...  please explain.
0
How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

 
LVL 15

Expert Comment

by:getzjd
ID: 10683985
Double Check in active directory on the email addresses tab, make sure they have the correct addresses, if not you need to add a recipient policy.  Did you add recipient policy for domain?
0
 

Author Comment

by:vicrod3315
ID: 10684364
Getzjd,

Yes i checked the recipient policy and its ok. During the migration it added the correct organizational domain name.

I did a ping test to the new exchange 2003 and the IP addres is not correct. But when I check the adapter it has the right static IP address.  I don't get it ? Even when I try to reboot the server is getting a different address other than the static IP I assigned.  Any suggestions? Could it be stale Wins record or DHCHP lease?
0
 
LVL 15

Accepted Solution

by:
getzjd earned 125 total points
ID: 10686177
When you ping, are you pinging the netbios name?  

Do an IPCONFIG /ALL on the exchange server and see if it says DHCD Enabled......      

What is your DNS Server, the 2003 machine?  

WINS server?  

also do a tracert to the IP of your exchange server, does it resolve a name when finished?

Open a command prompt from the exchange server and do an nbstat -rr , if you are using wins, this will release and renew the record

Open your wins server and look for the record of your 2003 server  and delete it

To delete or tombstone an entry in the WINS database

Open WINS
In the console tree, click Active Registrations.
 On the Action menu, click either Find by Name or Find by Owner to display the names you want to delete from the database.
In the details pane, click the entry you want to delete.
On the Action menu, click Delete.
In the Delete Record dialog box, click one of the following options for deleting the selected records:
Delete the record only from this server.
Replicate deletion of the record to other servers (tombstone).







0
 

Author Comment

by:vicrod3315
ID: 10690701
Ok that's solved that problem.... Thanks,, but when i move a mailbox accross the connector to the new exchange 2003 server for some reason it's not  able to receive emails right away.  Do I have to synch the servers or something? Where I do this?
0

Featured Post

Highfive Gives IT Their Time Back

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

Suggested Solutions

Article by: IanTh
Hi Guys After a whole weekend getting wake on lan over the internet working, I thought I would share the experience. Your firewall has to have a port forward for port 9 udp to your local broadcast x.x.x.255 but if that doesnt work, do it to a …
Don’t let your business fall victim to the coming apocalypse – use our Survival Guide for the Fax Apocalypse to identify the risks and signs of zombie fax activities at your business.
Viewers will learn how to connect to a wireless network using the network security key. They will also learn how to access the IP address and DNS server for connections that must be done manually. After setting up a router, find the network security…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…

708 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

12 Experts available now in Live!

Get 1:1 Help Now