2
Failover to another IP
Question asked by Terry Reynolds - 5/20/2021 at 5:34 AM
Unanswered
Hi,
I have 5 IP's on my server that I transferred from one host to a VM on another.  I can send and receive email from the server.  The mail server is mail.domain.com on IP xxx.xxx.xxx.188 and resolves externally to this as does the PTR record, yet there are loads of bounce-backs.  When I look at a received email header I see it has used xxx.xxx.xxx.186.  No protocols are actually bound to this IP and it is used (or meant to be) by HTTP(S) traffic.
When I look in the Smartermail logs I see the following;

  • Initiating connection to 104.47.8.36
  • Connecting to 104.47.8.36:25 (Id: 1)
  • Exception connecting to 104.47.8.36 (Id: 1)
  • System.Net.Sockets.SocketException (0x80004005): The requested address is not valid in its context
  • Binding to local ip 'xxx.xxx.xxx.188' failed.  Switched binding to primary local ip.
Being on a VM I think it's failing over to the server IP (192.168.1.2) which does have protocol bindings and is then simply sending out on xxx.xxx.xxx.186.

I think my first question is, why does it fail to bind to 188?
Second question, if I can't stop the error, how do I then force the internal IP to use 188?

I hope the above makes sense and would dearly like to know how to resolve this.

Thanks.

4 Replies

Reply to Thread
0
Terry Reynolds Replied
Does anyone have any ideas please?
Thanks.
1
You need to open a ticket and probabily the tecnicians need to look at you VM network configurations.

I think there's something wrong with  your SmarterMail config AND with the network config of your VM, but without accessing it directly and see it I cannot help you...

Sorry
0
Terry Reynolds Replied
Thanks for the response Gabriele.  

As an interim measure I have asked the host to add an additional PTR for the second IP address and once the bounce backs cease will open it then.

0
Ron Raley Replied
I believe that your IP address MUST be binded with the SMTP SmarterMail protocol.  Also, you likely need to change your PRIMARY IP for the Network Adapter using ipconfig.

This is my best guess.  Good luck!

Reply to Thread