boed
asked on
Exchange 2013 server can't send or receive email
Hello,
We are migrating our server from Exchange 2010 to 2013. Both servers are in a single AD server environment.
The databases are mounted on both exchange servers and I am able to open my mailbox on the new exchange server using owa
We just set up a new server running 2012 R2 with all the latest patches
We've disabled the firewall on it for now and the one on the 2010 server for now.
Both servers are now set for internal DNS resolution
Each server only has 1 nic with 1 ip per new server 10.10.150.16 old server 10.10.150.15 - nothing on the network had those IPs.
There are no vlans - this is just one subnet - dumb switch.
2010 can telnet to 2013
2013 can telnet to 2010
2010 can ping 2013 by name - gets the correct internal IP address
2013 can ping 2010 by name - gets the correct internal IP address
I can telnet out from 2013 to any other exchange server outside the network
I can telnet in from any other exchange server in the outside world to the 2013 server
I migrated one test mailbox from the old server to the new server.
When I send an email from the 2010 server to the 2013 server with the test mailbox I get the message stuck in the queue -
Queue - Hub version 15 451 4.4.0 Primary target IP address responded with 421 4.2.1 unable to connect.
There are no other messages in the queue but that 1 that I just sent - no other outstanding queues
When I do a test-mailflow from 2010server to 2013server I get
MapiExceptionNetworkError:
Diagnostic context:
......
Lid: 15000 dwParam: 0x6BA Msg: EEInfo: prm[1]: Pointer val: 0x0000000000000000
Lid: 15000 dwParam: 0x6BA Msg: EEInfo: prm[2]: Pointer val: 0x65960A0A00000000
Lid: 16280 dwParam: 0x6BA Msg: EEInfo: ComputerName: n/a
Lid: 8600 dwParam: 0x6BA Msg: EEInfo: ProcessID: 7016
Lid: 12696 dwParam: 0x6BA Msg: EEInfo: Generation Time: 2018-10-13 03:59:38:822
Lid: 10648 dwParam: 0x6BA Msg: EEInfo: Generating component: 18
Lid: 14744 dwParam: 0x6BA Msg: EEInfo: Status: 10060
Lid: 9624 dwParam: 0x6BA Msg: EEInfo: Detection location: 318
Lid: 13720 dwParam: 0x6BA Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x6BA Msg: EEInfo: NumberOfParameters: 0
Lid: 24060 StoreEc: 0x80040115
Lid: 23746
Lid: 31938 StoreEc: 0x80040115
Lid: 19650
Lid: 27842 StoreEc: 0x80040115
Lid: 20866
Lid: 29058 StoreEc: 0x80040115
+ CategoryInfo : NotSpecified: (0:Int32) [Test-Mailflow], MapiExceptionNetworkError
+ FullyQualifiedErrorId : B82CA4E1,Microsoft.Exchang
When I send an email from OWA on the 2013 server from the test mailbox it doesn't seem to go anwwhere.
I look at the queue on the 2010 and 2013 server and neither has any message queues for that message.
I'm pretty sure the issue is the new 2013 server because it can't even email to itself. I definitely have the internal windows firewall disabled. There are no add on products to this as it is a brand new set up - not even any antispam other than the native exchange antispam which is currently left with the default settings.
When I do mailflow from the new server to the new server it fails
RunspaceId : f497ade5-7df1-4ba0-ae99-f6
TestMailflowResult : *FAILURE*
MessageLatencyTime : 00:00:00
IsRemoteTest : True
Identity :
IsValid : True
ObjectState : New
A test from the old server to the new server
MapiExceptionNetworkError:
Diagnostic context:
......
Lid: 15000 dwParam: 0x6BA Msg: EEInfo: prm[1]: Pointer val: 0x0000000000000000
Lid: 15000 dwParam: 0x6BA Msg: EEInfo: prm[2]: Pointer val: 0x65960A0A00000000
Lid: 16280 dwParam: 0x6BA Msg: EEInfo: ComputerName: n/a
Lid: 8600 dwParam: 0x6BA Msg: EEInfo: ProcessID: 6700
Lid: 12696 dwParam: 0x6BA Msg: EEInfo: Generation Time: 2018-10-13 13:40:16:314
Lid: 10648 dwParam: 0x6BA Msg: EEInfo: Generating component: 18
Lid: 14744 dwParam: 0x6BA Msg: EEInfo: Status: 10060
Lid: 9624 dwParam: 0x6BA Msg: EEInfo: Detection location: 318
Lid: 13720 dwParam: 0x6BA Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x6BA Msg: EEInfo: NumberOfParameters: 0
Lid: 24060 StoreEc: 0x80040115
Lid: 23746
Lid: 31938 StoreEc: 0x80040115
Lid: 19650
Lid: 27842 StoreEc: 0x80040115
Lid: 20866
Lid: 29058 StoreEc: 0x80040115
+ CategoryInfo : NotSpecified: (0:Int32) [Test-Mailflow], MapiExceptionNetworkError
+ FullyQualifiedErrorId : 89E097A3,Microsoft.Exchang
All the correct exchange services are running. Tried restarting frontend transport and transport services, system attendant on old server etc, no luck. I have rebooted both servers.
Not sure if it matters but this is a 2012 R2 VM running on a 2016 host.
We are migrating our server from Exchange 2010 to 2013. Both servers are in a single AD server environment.
The databases are mounted on both exchange servers and I am able to open my mailbox on the new exchange server using owa
We just set up a new server running 2012 R2 with all the latest patches
We've disabled the firewall on it for now and the one on the 2010 server for now.
Both servers are now set for internal DNS resolution
Each server only has 1 nic with 1 ip per new server 10.10.150.16 old server 10.10.150.15 - nothing on the network had those IPs.
There are no vlans - this is just one subnet - dumb switch.
2010 can telnet to 2013
2013 can telnet to 2010
2010 can ping 2013 by name - gets the correct internal IP address
2013 can ping 2010 by name - gets the correct internal IP address
I can telnet out from 2013 to any other exchange server outside the network
I can telnet in from any other exchange server in the outside world to the 2013 server
I migrated one test mailbox from the old server to the new server.
When I send an email from the 2010 server to the 2013 server with the test mailbox I get the message stuck in the queue -
Queue - Hub version 15 451 4.4.0 Primary target IP address responded with 421 4.2.1 unable to connect.
There are no other messages in the queue but that 1 that I just sent - no other outstanding queues
When I do a test-mailflow from 2010server to 2013server I get
MapiExceptionNetworkError:
Diagnostic context:
......
Lid: 15000 dwParam: 0x6BA Msg: EEInfo: prm[1]: Pointer val: 0x0000000000000000
Lid: 15000 dwParam: 0x6BA Msg: EEInfo: prm[2]: Pointer val: 0x65960A0A00000000
Lid: 16280 dwParam: 0x6BA Msg: EEInfo: ComputerName: n/a
Lid: 8600 dwParam: 0x6BA Msg: EEInfo: ProcessID: 7016
Lid: 12696 dwParam: 0x6BA Msg: EEInfo: Generation Time: 2018-10-13 03:59:38:822
Lid: 10648 dwParam: 0x6BA Msg: EEInfo: Generating component: 18
Lid: 14744 dwParam: 0x6BA Msg: EEInfo: Status: 10060
Lid: 9624 dwParam: 0x6BA Msg: EEInfo: Detection location: 318
Lid: 13720 dwParam: 0x6BA Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x6BA Msg: EEInfo: NumberOfParameters: 0
Lid: 24060 StoreEc: 0x80040115
Lid: 23746
Lid: 31938 StoreEc: 0x80040115
Lid: 19650
Lid: 27842 StoreEc: 0x80040115
Lid: 20866
Lid: 29058 StoreEc: 0x80040115
+ CategoryInfo : NotSpecified: (0:Int32) [Test-Mailflow], MapiExceptionNetworkError
+ FullyQualifiedErrorId : B82CA4E1,Microsoft.Exchang
When I send an email from OWA on the 2013 server from the test mailbox it doesn't seem to go anwwhere.
I look at the queue on the 2010 and 2013 server and neither has any message queues for that message.
I'm pretty sure the issue is the new 2013 server because it can't even email to itself. I definitely have the internal windows firewall disabled. There are no add on products to this as it is a brand new set up - not even any antispam other than the native exchange antispam which is currently left with the default settings.
When I do mailflow from the new server to the new server it fails
RunspaceId : f497ade5-7df1-4ba0-ae99-f6
TestMailflowResult : *FAILURE*
MessageLatencyTime : 00:00:00
IsRemoteTest : True
Identity :
IsValid : True
ObjectState : New
A test from the old server to the new server
MapiExceptionNetworkError:
Diagnostic context:
......
Lid: 15000 dwParam: 0x6BA Msg: EEInfo: prm[1]: Pointer val: 0x0000000000000000
Lid: 15000 dwParam: 0x6BA Msg: EEInfo: prm[2]: Pointer val: 0x65960A0A00000000
Lid: 16280 dwParam: 0x6BA Msg: EEInfo: ComputerName: n/a
Lid: 8600 dwParam: 0x6BA Msg: EEInfo: ProcessID: 6700
Lid: 12696 dwParam: 0x6BA Msg: EEInfo: Generation Time: 2018-10-13 13:40:16:314
Lid: 10648 dwParam: 0x6BA Msg: EEInfo: Generating component: 18
Lid: 14744 dwParam: 0x6BA Msg: EEInfo: Status: 10060
Lid: 9624 dwParam: 0x6BA Msg: EEInfo: Detection location: 318
Lid: 13720 dwParam: 0x6BA Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x6BA Msg: EEInfo: NumberOfParameters: 0
Lid: 24060 StoreEc: 0x80040115
Lid: 23746
Lid: 31938 StoreEc: 0x80040115
Lid: 19650
Lid: 27842 StoreEc: 0x80040115
Lid: 20866
Lid: 29058 StoreEc: 0x80040115
+ CategoryInfo : NotSpecified: (0:Int32) [Test-Mailflow], MapiExceptionNetworkError
+ FullyQualifiedErrorId : 89E097A3,Microsoft.Exchang
All the correct exchange services are running. Tried restarting frontend transport and transport services, system attendant on old server etc, no luck. I have rebooted both servers.
Not sure if it matters but this is a 2012 R2 VM running on a 2016 host.
Amit
Try to send a test mail using telnet. Review the result. It seems you have permission issue.
ASKER
Hello,
Thanks for your help - I don't know if these results help you
I ran the test from our 2010 server which is on the same subnet and switch.
220 EXCH2013.intdomain.lan Microsoft ESMTP MAIL Service ready at Sat, 13 Oct 2018
41:47 -0700
EHLO ourdomain.com250-exch2013.
250-SIZE 36700160
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-X-ANONYMOUSTLS
250-AUTH NTLM
250-X-EXPS GSSAPI NTLM
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 XRDST
MAIL FROM:me@ourdomain.com250 2.1.0 Sender OK
RCPT TO:me@ourdomain.com NOTIFY=success,failure250 2.1.5 Recipient OK
DATA354 Start mail input; end with <CRLF>.<CRLF>
Subject: Test from me
This is a test message
.
451 4.7.0 Temporary server error. Please try again later. PRX5
I ran these commands to point to our internal dns server and it did not help.
Set-FrontendTransportServi
Set-FrontendTransportServi
Set-FrontendTransportServi
Set-FrontendTransportServi
Get-FrontEndTransportServi
[PS] C:\Windows\system32>Get-Fr
ExternalDNSAdapterEnabled : True
ExternalDNSAdapterGuid : 9ed76c4e-8bbf-46a6-9b46-e9
ExternalDNSProtocolOption : Any
ExternalDNSServers : {10.10.150.10}
InternalDNSAdapterEnabled : True
InternalDNSAdapterGuid : 9ed76c4e-8bbf-46a6-9b46-e9
InternalDNSProtocolOption : Any
InternalDNSServers : {10.10.150.10}
DnsLogMaxAge : 7.00:00:00
DnsLogMaxDirectorySize : 100 MB (104,857,600 bytes)
DnsLogMaxFileSize : 10 MB (10,485,760 bytes)
DnsLogPath :
DnsLogEnabled : False
Thanks for your help - I don't know if these results help you
I ran the test from our 2010 server which is on the same subnet and switch.
220 EXCH2013.intdomain.lan Microsoft ESMTP MAIL Service ready at Sat, 13 Oct 2018
41:47 -0700
EHLO ourdomain.com250-exch2013.
250-SIZE 36700160
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-X-ANONYMOUSTLS
250-AUTH NTLM
250-X-EXPS GSSAPI NTLM
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 XRDST
MAIL FROM:me@ourdomain.com250 2.1.0 Sender OK
RCPT TO:me@ourdomain.com NOTIFY=success,failure250 2.1.5 Recipient OK
DATA354 Start mail input; end with <CRLF>.<CRLF>
Subject: Test from me
This is a test message
.
451 4.7.0 Temporary server error. Please try again later. PRX5
I ran these commands to point to our internal dns server and it did not help.
Set-FrontendTransportServi
Set-FrontendTransportServi
Set-FrontendTransportServi
Set-FrontendTransportServi
Get-FrontEndTransportServi
[PS] C:\Windows\system32>Get-Fr
ExternalDNSAdapterEnabled : True
ExternalDNSAdapterGuid : 9ed76c4e-8bbf-46a6-9b46-e9
ExternalDNSProtocolOption : Any
ExternalDNSServers : {10.10.150.10}
InternalDNSAdapterEnabled : True
InternalDNSAdapterGuid : 9ed76c4e-8bbf-46a6-9b46-e9
InternalDNSProtocolOption : Any
InternalDNSServers : {10.10.150.10}
DnsLogMaxAge : 7.00:00:00
DnsLogMaxDirectorySize : 100 MB (104,857,600 bytes)
DnsLogMaxFileSize : 10 MB (10,485,760 bytes)
DnsLogPath :
DnsLogEnabled : False
ASKER
FYI - I haven't had a chance to really go to town but I did create a new hub receive connector and I could now telnet to it. from the exchange 2010 server. Still no mail in my mailbox on 2013 and stil can't send. I'll possibly remove all the default connectors and create new send and receive and see if that works - going to bed now.
What roles did you install on your Exchange 2013 server? You need at least Client Access, Hub Transport and Mailbox roles for 2013.
Mailboxes on 2013 will use 2013 Hub transports first (not earlier ones before sending it out). Also, you need to update or create new Send Connectors for mail going out.
Mailboxes on 2013 will use 2013 Hub transports first (not earlier ones before sending it out). Also, you need to update or create new Send Connectors for mail going out.
ASKER
Thanks - for some reason it had a DNS entry on the dns with the original IP before I changed it. I removed it and rebooted the server and it didn't create one. Even tried ipconfig /registerdns - no joy - for whatever reason I had to manually create the internal dns A record. .
Thanks for your help.
Thanks for your help.
Make sure that you configure the domain suffix in the System Control Panel, System, Computer Name. As this needs to match the DNS zone name to ensure IP registration works with dns.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.
I have recommended this question be closed as follows:
Accept: 'boed' (https:#a42707082)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
seth2740
Experts-Exchange Cleanup Volunteer
I have recommended this question be closed as follows:
Accept: 'boed' (https:#a42707082)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
seth2740
Experts-Exchange Cleanup Volunteer