Verify Machine Name and Configure Nintex Bot VPN and Nintex RPA Central Firewall IP Addresses
When a Nintex Bot connects to the Nintex RPA Central server, Nintex RPA Central performs a validation to make sure that the Nintex Bot machine is properly registered with DNS to prevent illegal Nintex Bots from connecting to the Nintex RPA Central server. Nintex RPA Central runs that validation using the Nintex Bot machine’s IP address.
If the Nintex Bot machine is connected to a VPN, the Nintex Bot's IP address will be the VPN’s IP address and any connection validation will fail since the DNS lookup using the VPN’s IP address will fail. This failure leads to a verify machine name error and prevents the Nintex Bot from connecting to the Nintex RPA Central server. To bypass the connection validation, follow the steps below to verify the machine name and configure the Nintex Bot VPN and Nintex RPA Central IP addresses:
Note: Nintex RPA Central 2.6.0 and below only supports the use of one VPN IP address. To add additional VPN IP addresses to the configuration and ensure that the connection is successful, upgrade to Nintex RPA Central 2.7.0 or above.
-
In the RPACentral installation folder (C:\Program Files (x86)\Nintex\RPACentral\RPACentral), locate the sharedServiceSettings.xml file and open it using a text editor.
-
In the BotVpnSettings node, type the VPN IP address in the IpAddress node. If you have multiple VPN IP addresses, separate them with a semicolon. If you have a range of VPN IP addresses, separate them with a dash.
<BotVpnSettings>
<IpAddress>10.10.10.1-10.10.10.400;10.10.10.500</IpAddress>
</BotVpnSettings>
Note: Do not include port numbers in VPN IP addresses. For example, 10.10.10.1;10.10.10.2 is valid, but 10.10.10.1:443;10.10.10.2:443 is not valid.
-
Save the sharedServiceSettings.xml file.
-
Open Services and restart the RPA Central Windows service.
The Nintex Bot machine connected to a VPN can now connect to the Nintex RPA Central server.