Highlighted
Absent Member.
Absent Member.
1511 views

Error trying to access secondary post office via SOAP

Hello -

Unfortunately, a client of mine has been purchased and are moving to Outlook 365. They are trying to migrate two post offices. The main works OK, as it's server is accessible from a public IP. The second currently is not.

The app gets an error when trying to migrate a user on secondary PO. "Your migration failed. GroupWise Login Failed. Error: Redirect user to different post office. Code: 59923 - redirected to: http://192.168.3.240:7191/."

Their resolution states:

1. Check that the specified user name is on the target POA (it is).

2. If the user is on a linked POA, make sure the link references a publicly accessible name / IP (they're linked via private IP)

3. If necessary, update POA links to use publicly accessible names / IPs (not sure how to do this).


Any ideas?
Labels (2)
0 Likes
4 Replies
Highlighted
Absent Member.
Absent Member.

Re: Error trying to access secondary post office via SOAP

bertschj wrote:

> 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 123.123.123.123 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?

--
Danita
Novell Knowledge Partner
Are you a GroupWise Power Administrator? Join our site.
http://www.caledonia.net/register

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Error trying to access secondary post office via SOAP

dzanre;2315650 wrote:
bertschj wrote:

> 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 123.123.123.123 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?


Sort of... : )

Let me add some other info and then get to your info.

Primary PO IP = 192.168.1.240 (SOAP int/ext ports in GW set to 7191/7191)
Secondary PO IP = 192.168.3.240 (SOAP int/ext ports in GW set to 7191/7192) - also tried 7192/7192
Firewall has port forward for public IP/port 7191 to 192.168.1.240 (7191 for both External and Internal port)
Firewall has port forward for public IP/port 7192 (ext) to 192.168.3.240 port 7191 (int) - also tried 7192 for int
To test from outside, we enter http://<publicIP>:7191/soap (we get odd message but that's normal)
If I test http://<publicIP>:7192/soap, I just get browser timeout error.

So based on your suggestions, where am I making mistake?

Thanks for your help
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Error trying to access secondary post office via SOAP

bertschj wrote:

> If I test http://<publicIP>:7192/soap, I just get browser timeout error.
>
> So based on your suggestions, where am I making mistake?


It really sounds like there is still a firewall issue that is not properly
routing this through to the POA.

--
Danita
Novell Knowledge Partner
Are you a GroupWise Power Administrator? Join our site.
http://www.caledonia.net/register

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Highlighted
Visitor.

Re: Error trying to access secondary post office via SOAP

Hi bertschj!

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"

Any idea??

Thanks you!! 

Fernando

 

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.