L P
asked on
Exchange Server 2013 - changed ip - now queues in retry state
I changed the ip address of my Exchange server. I had issues seeing the queues but now can after changing my firewall. Now the queues are "stuck" in retry state.
ASKER
Still the same after restart of msexchangetransport.
Please make sure Exchange server can reach DC and vice versa
ASKER
The servers appear to communicate fine, each can ping the other.
Please make sure there is no antispam holding this in your server.
I interpet, that the mails which are stuck in the queue are from the time around changing the IP Address?
But no new ones?.
What is about to just resend them?
But no new ones?.
What is about to just resend them?
ASKER
I have for now reverted to the old ip. Yes, they were stuck from the change point. However, any new emails that would be sent from my outlook with the new up wouldnot flow through the system.
As soon as I revert back to the old ip everything again works. I assume it is obviously a flow issue but I do not understand enough of exchange to know how the flow all works between receiving the email (I assume receive connector), it getting into a queue, and it getting to a mailbox. I wonder if I remove all receive connector and recreate would that likely solve the issue?
As soon as I revert back to the old ip everything again works. I assume it is obviously a flow issue but I do not understand enough of exchange to know how the flow all works between receiving the email (I assume receive connector), it getting into a queue, and it getting to a mailbox. I wonder if I remove all receive connector and recreate would that likely solve the issue?
In exchabge you have listener IPs as well a IP targets configured on the send and receive connectors.
If you change the IP you have to take care, that all connectors reflect the new IP address.
So as exchange gets the mail from somewhere, there is something infront of echange which directs the mail to your connector. The minimum would be your MX record, but also a router, spam protection device etc. may in scope.
For outgoing mails, exchange has to know, how to distribute the mails. You can uses DNS MX resolution, where exchange justs ask for the MX record for the target mail server. Also here, other devices may be involved, like routers and spam protection devices.
If such devices are involved, you have to tell them, that they get mails nows from a different ip.
In the queue, you see usually if outgoing or incoming mails are affected. But no seeing incoming doesn't mean, that you get them.
Also you have usually an error code there, which may point to the reason. The queue usually has to do with the communication with other systems, as internal queues are normaly not so affected by the changed IP.
If you change the IP you have to take care, that all connectors reflect the new IP address.
So as exchange gets the mail from somewhere, there is something infront of echange which directs the mail to your connector. The minimum would be your MX record, but also a router, spam protection device etc. may in scope.
For outgoing mails, exchange has to know, how to distribute the mails. You can uses DNS MX resolution, where exchange justs ask for the MX record for the target mail server. Also here, other devices may be involved, like routers and spam protection devices.
If such devices are involved, you have to tell them, that they get mails nows from a different ip.
In the queue, you see usually if outgoing or incoming mails are affected. But no seeing incoming doesn't mean, that you get them.
Also you have usually an error code there, which may point to the reason. The queue usually has to do with the communication with other systems, as internal queues are normaly not so affected by the changed IP.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Open in new window