Summary: The error ‘Unable to make connection to the server. (hr=0x80004005, ec=2423)’ may occur while migrating a mailbox from one server to another. In this post, we’ve discussed the solutions to fix this error. Also, you’ll find about an EDB to PST converter software that can help migrate mailboxes, if you face any issues while migrating.
Contents
In the Exchange Server environment, you would need to migrate to a new Exchange server version or Office 365 using a hybrid system. The biggest headache would be to move the data since this involves a lot of parries and configuration. If you are moving mailboxes from one server to another, you need to use the New-MailboxExportRequest PowerShell command.
However, while moving mailboxes from one server to another or exporting to PST and importing them into the new server, you might encounter the following error when running the PowerShell command New-MailboxExportRequest or New-MailboxMoveRequest.
Microsoft.Exchange.MailboxReplicationService encountered an exception. Error: MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)
Solution to Resolve the Unable to make connection to the server. ?(hr=0x80004005, ec=2423) Error
Firstly, check the services of the Exchange Server. Exchange Server depends on several services. If a service is not working or not started, this can lead to connectivity issues. There could be instances where the services did not start. This could be due to an update or something which is blocking the services from starting. To check the services,
- Right-click on the Start button.
- Click on Run.
- Type services.msc.
Once the MMC window loads and all the services are listed in the window, search for the Exchange Server services, which can be found under the Microsoft Exchange part.
If any service which has the Startup Type set to Automatic and is not shown as running, the first thing to do is start the service manually. If this doesn?t work, it would be best to schedule a reboot of the server, in case something is stopping the service from starting.
If the service is stopped and marked as Automatic, check the Event Viewer for any warnings and errors that might indicate what is stopping the service from running. You can check the Application and the Exchange Sections in the Event Viewer.
Another thing to do is try to ping the server using the IP, server name, and the full FQDN to ensure connectivity. If this is good, you can try to run an NSLookup against the server?s name to ensure that there is no NetBIOS name resolution issue.
If there is an issue, it could be due to a problem with the DNS server or you need to add the DNS Suffix to the Network TCP/IP Setting of the server to add the full FQDN. This can be done by updating the network settings of the Exchange Server. Exchange Server is dependent on the DNS and if you have an unhealthy DNS or a change in configuration, it could lead to disconnection or loss of connectivity with the Exchange Server. Follow these steps to add the DNS Suffix to the Network TCP/IP Setting:
- Click on the Internet Protocol Version 4 (TCP/IPv4) and click on Properties.
- Click on the Advanced button and click on the DNS tab.
- In the DNS suffix for this connection, enter the full domain name of the Active Directory and tick Use this connection?s DNS suffix in DNS registration.
This should resolve the issue. After a quick flush of the DNS settings, the server should work fine. To flush the DNS, open the command prompt as Administrator and type the following commands.
ipconfig /flushdns
ipconfig /registerdns
This should clear off the DNS issues which could affect your connectivity to the Exchange Server.
To Wrap Up
There could be an issue with your Exchange Server and the problem persists. This can be caused due to corrupted Exchange installation files or corrupted configuration files or services of the server. Also, there could be an issue with Exchange Update, Windows update, or a new third-party application installed. So, finding out what happened on the Exchange Server or keeping a log might help.
The only solution is to re-install Exchange Server and re-import the mailbox databases back but it isn?t an easy job. The other solution is to restore the server from backup but this would result in data loss. The easiest solution to resolve the issue without restoring from backup or data loss is to use Stellar Converter for EDB. The software can open multiple EDB files from any Exchange Server database version and granularly export them to PST and other file formats. You can also export directly to a live Exchange database of any version. You can use this as a migration tool to migrate to Office 365.
