> redirected to: ">http://192.168.3.240:7191/."
I would try setting a public IP address on the External IP Address field for the
POA. You can also have a different port at the External SOAP port, if
necessary, and redirect through NAT Port Forwarding.
So, for example, if the processes is going to 188.8.131.52 port 7191 and that
is then being forwarded through to one PO, you would need to make the external
port for the second PO something like 7192. The first PO would then redirect to
123.123.123123 port 7192 rather than the internal address when the user is found
to be on the second post office.
Does that make sense?
I've the same issue! Can you solve it? How? I'm migrating from GroupWise 18 to Office 365 with BitTitan tool and I've the same error. In my environment, we have linked POAs:
Primary PO = IP1 | SOAP int/ext ports in GW set to 7191/7191
Secondary PO = IP2 | SOAP int/ext ports in GW set to 7191/7191
Firewall has port forward for public IP/port 7191 to Primary PO (IP1)
If user is located in Primary PO, it work fine. But if the user is located in Secondary PO, I have the following error: "Your migration failed checking source credentials. GroupWise login failed. Error: Redirect user to different post office. Code: 59923"