Symptoms

We have a fully functional K2 Farm with several high profile applications. K2 server internal K2 server is not accessible externally at present. We are now deploying a new application which has K2 Forms on O365 SharePoint Online as well as Internal On-Prem SharePoint. After reviewing your documentation and KBs, we decided to grant external access to K2 server. So our networking team assigned a new DMZ Internal and External IP. I requested networking team to leave the existing internal IP as-is and add a 2nd NIC card to the server so the new DMZ internal and external IPs can be assigned to it as well. But having an internal IP and a 2nd DMZ Internal IP violates the security guidelines as it means the server resides both internally and also in the DMZ. So they suggest deleting IP and replacing it with the DMZ IP. We have several apps running on the server and my concern is that eliminating the old IP might require a 4.6.9 re-configuration/re-install, which might impact existing applications.

Can the existing IP address on K2 server be updated without any impact to existing applications, STS authentication or farm configuration?

 

Diagnoses

K2 uses name resolution. Changing the IP should not affect K2.
 

Resolution


K2 doesn't use IP addresses for the configuration, it uses name resolution, so in the event of an IP change everything will still pointing to the Name only. If you created a Farm then we will be using that farm name and whatever IP is pointing to that one should be the one to use.

Unless the IP is pointing to a different sever than the K2 then you will be getting some issues. there shouldn't be any issue doing that. Only make sure the new IP Address has the access to the SQL, SharePoint or systems that the old IP had. Also check the DNS records so everything gets changed to the new IP.