Error encountered while communicating with primary IP-address

Question

Hi
I have recently deployed my first Exchange Server. This is an Exchange Server 2013 Standard and I set up everything using this document on Technet for installation: http://technet.microsoft.com/en-us/library/bb124778(v=exchg.150).aspx
For post-installation I used this document on Technet: http://technet.microsoft.com/en-us/library/bb124397(v=exchg.150).aspx
I have setup access to port 25, 587, 143, 993, 110, 995, 80, 443 in my routers SPI-firewall and created DNAT rules for each of these ports as well. I can send mail without any issues, but I cannot receive. Reverse DNS is working both internally and externally.
I can telnet to port 25 on my external IP and external domain which is exchange.mydomain.tld
My Exchange-server is running inside a Gen1 Hyper-V virtual machine on a Windows Server 2012 R2.
My Exchange Server has the following resources:
OS: Windows Server 2012 R2
CPU: 2 cores of AMD FX-6120 3.30GHz
RAM: 3584MB
HDD1: IDE 80GB VHDX - is currently used for all system files and for Exchange.
HDD2: SCSI 127GB VHDX - will be used for Exchange DB and logs when everything is working.
When sending mail from any internal or external e-mail address to an internal e-mail address I get the following error in Exchange Queue Viewer:
"451 4.4.0 Error encountered while communicating with primary target IP address:"421 4.2.1 Unable to connect." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate
hosts. The Last"
How can I solve this issue? If you need any more information please let me know and I will see if I can find it.

Answer 1

Hi I have now tried to send mail to an internal address using telnet. This returned the following value:
250 2.6.0 <[email protected]> [InternalId=1971389988866] Queued mail for delivery
Next I tried to send to an external mail by using telnet and it returned this result when adding the reciepient:
550 5.7.1 Unable to relay
This is the output of the Test-Servicehealth cmdlet:
Role                    : Mailbox Server Role
RequiredServicesRunning : True
ServicesRunning         : {IISAdmin, MSExchangeADTopology, MSExchangeDelivery, MSExchangeIS, MSExchangeMailboxAssistant
                          s, MSExchangeRepl, MSExchangeRPC, MSExchangeServiceHost, MSExchangeSubmission, MSExchangeThro
                          ttling, MSExchangeTransportLogSearch, W3Svc, WinRM}
ServicesNotRunning      : {}
Role                    : Client Access Server Role
RequiredServicesRunning : True
ServicesRunning         : {IISAdmin, MSExchangeADTopology, MSExchangeMailboxReplication, MSExchangeRPC, MSExchangeServi
                          ceHost, W3Svc, WinRM}
ServicesNotRunning      : {}
Role                    : Unified Messaging Server Role
RequiredServicesRunning : True
ServicesRunning         : {IISAdmin, MSExchangeADTopology, MSExchangeServiceHost, MSExchangeUM, W3Svc, WinRM}
ServicesNotRunning      : {}
Role                    : Hub Transport Server Role
RequiredServicesRunning : True
ServicesRunning         : {IISAdmin, MSExchangeADTopology, MSExchangeEdgeSync, MSExchangeServiceHost, MSExchangeTranspo
                          rt, MSExchangeTransportLogSearch, W3Svc, WinRM}
ServicesNotRunning      : {}
Can we use this information to find a possible source for my issues?