Vlado, did you run a re-install of your GMS? In most cases it will help because GMS will reread GW configuration.

I assume that you have already refreshed your GW admin certs to fit the new ip address and dns information.

Thank you for your response, Diethmar. Yes, I created a new certificate to include the new IP address.

Since we need to change the IPs for several other MTAs/POAs, I need to be certain of the steps required to ensure GMS works with the new IPs. I've also reached out to support for further guidance.

Hey, I had couple weeks ago same problem and ended with GMS reinstall. 

Thank you, David. I've just reinstalled GMS, but it didn't resolve the problem. As soon as I add a user from PO with a changed IP address, errors appear in the groupwise-agent.log.

2024-09-04 00:49:39.817 ERROR [CP Server Thread-20] [gwsoap:424] [userID:ac] [eventID:] [objectID:] [SOAPRequest] Timeout error when talking to a POA. Response string: None; Exception: HTTPSConnectionPool(host='172.29.250.152', port=7191): Max retries exceeded with url: /soap (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7fa463b9c3d0>, 'Connection to 172.29.250.152 timed out. (connect timeout=40)'))

172.29.125.152 is old IP address.

I received the following troubleshooting steps from support, which resolved the issue:

1. Stop GMS and connect to the database:
   psql -U datasync_user datasync;

2. Check if the incorrect IP address is present:
   select poasettings from targets;

3. Remove all records:
   update targets set poasettings=NULL;

4. Restart GMS. The records will be regenerated with the correct new IP address.

I have published that as a TID: https://portal.microfocus.com/s/article/KM000033841

Note, that editing databases to reflect changes in POA settings is so far only a temporary workaround. I hope that devs will come up with a "regular" solution for that.