Exchange 2010 and Mailbox Export

Unfortunately I am not the network person, I am the Exchange Admin, and I was just trying to do some homework on my own. I can share with you the details though.

 

 

If you look at the syntax of the new-mailboxrestorerequst, when troubleshooting, you have the option of adding the -mrsserver switch. When I run this command without that switch, this is how it looks-

 

 

COMMAND: new-mailboxrestorerequest -mailbox user@domain.com -filepath \\servername\share$

 

ERROR: Couldn't connect to the source mailbox.

 

 

Not a very descriptive error. Now I add in the mrsserver switch.

 

 

COMMAND: new-mailboxrestorerequest -mailbox user@domain.com -filepath \\servername\share$ -mrsserver CASNAME

 

ERROR: The call to 'net.tcp://casname/microsoft.exchange.mailboxreplicationservice' failed because no service was listening on the specified endpoint. Error details: Could not connect to net.tcp://casname/microsoft.exchange.mailboxreplicationservice. The connection attempt lasted for a time span of 00:00:21.0162157. TCP error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 129.220.1.1:808. --> A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 129.220.1.1:808.

 

 

NOW.....the support article I mentioned initially tells you that enabling SNAT will correct this. They have not done it yet. I was able to follow the workaround and manually update the RPC Client Access Server name on the users database FROM the CASNAME to the actual name of a CAS server.

 

 

For your lab testing, remember, this failure is specific to hardware load balancers and CAS Arrays. So maybe check that all of your CAS servers are in your CAS Array. Hope this helps. Also hoping my network team will add the SNAT config so I can report back. But per Microsoft, this is somewhat of a known issue and that article is pretty specific. Thanks.