How to configure Windows Firewall for Sage 100 Advanced and Premium (with video)

CAUTION: This solution requires an advanced understanding of Windows or third-party add-ons. Mistakes in the Windows registry, security, and network settings can cause serious problems. Sage isn't responsible for the Windows environment, third-party add-ons, or customization issues. Create a system and database backup before making changes. Get help from your system admin, consultant, or vendor.

• Create Inbound Rule for Sage 100 Advanced C\S ODBC Driver Service (if applicable)
  1. Open Windows Firewall with Advanced Options.
  2. Right-click Inbound Rules and select New Rule.
  3. Select Program on the Rule Type screen, and click Next.
  4. In the Program dialog box, select This program path.
  5. Click the Browse button and browse to the C:\Sage\Sage 100 Advanced\Mas90\Home\ folder.
  6. Double-click pvxiosvr.exe.
  7. Click Next twice.
  8. On the Profile screen, select the desired Network Profiles to apply the settings to (Domain, Private, Public), and click Next.
  9. Enter Name and Description for Rule (i.e., Sage 100 C\S ODBC Driver).
  10. Click Finish.

• Create Inbound rule for SQL Server Instance and SQL Browser Service (Premium only)
   NOTE: Apply the following Firewall settings on SQL Server

1. Open Windows Firewall with Advanced Options.
2. Right-click Inbound Rules and select New Rule.
3. Select Program on the Rule Type screen.
4. Click Next.
5. In the Program dialog box, select This program path.
6. Select Browse and go to SQL Server instance you want access to via the firewall, then click Open. (Example: C:\Program Files\Microsoft SQL Server\MSSQL11\Instance_Name\MSSQL\Binn\Sqlserv.exe).
7. Click Next twice.
8. On the Profile screen, select the desired Network Profiles to apply the settings to (Domain, Private, Public), and click Next.
9. Enter the Name and Description for Inbound Rule (i.e., Sage 100 SQL).
10. Select Finish.
11. Right-click Inbound Rules and select New Rule.
12. Select Port on the Rule Type screen, and click Next.
13. In the Protocol and Ports dialog box, select UDP.
14. Select Specific Port Numbers and then enter the 1434.
15. Click Next twice.
16. On the Profile screen, select the desired Network Profiles to apply the settings to (Domain, Private, Public), and click Next.
17. Enter the Name and Description for the Rule (i.e., SQL Server Browser).
18. Click Finish.

How to use the PowerShell cmdlet 'Test-NetConnection' to test access to Port on Server?
Error: "Connection failure to host: [TCP]::NODELAY;STREAM"
Error: “The database login failed. Failed to open the connection. Details: [Database Vendor Code: 17]”