VPN Name Resolution Bug

Applies to. 1

Summary. 1

Solution. 1

Long-term Solution. 2

Applies to

SI5.2 client applications operating over a Virtual Private Network.

Summary

In SI5.2, client applications operating over a Virtual Private Network (VPN) are unable to resolve the server name to get an IP address, resulting in the client being unable to connect to the server.

The solution is to manually edit the client’s host file with the server’s name and IP address.

Solution

1. On the client machine navigate to the %systemroot%\system32\drivers\etc folder (typically C:\Windows\system32\drivers\etc)

2. Right click on the file named hosts and choose Open

3. When prompted choose to open the file with Notepad

4. At the bottom of the file add an entry for your server that follows the example in the host file.

· Example: If the servers IP address is 192.168.0.1 and servers machine name is si5server.domain.com, the entry would look like

192.168.0.1   si5server.domain.com

5. Save the changes and close the host file.

6. Confirm that you are able to resolve the servers name by connecting to the VPN and ping the server using it’s name. If you receive a reply from the correct IP address then the hosts file is set up correctly. If you do not, check the spelling and address in the hosts file.

CAUTION: There are anti-virus and anti-spyware programs that will detect that the host file was changed and change it back. You may need to deactivate this functionality to implement this solution.

Consequences of this solution

If the servers IP address changes in the future, you will need to edit the hosts file to update it with the new address.

Long-term Solution

This is a bug that will be corrected in a future update.