Create Inbound Rule for Sage 100 Service

1. Go to Start, Windows Administrative Tools, Windows Firewall with Advanced Options.
2. Right-click Inbound Rules and select New Rule.
3. Select Program on the Rule Type screen, then click Next.
4. In the Program dialog, select This program path.
5. Click Browse and go to C:\Sage\Sage 100 Advanced\Mas90\Home\.
6. Double-click exe (use pvxwin64.exe for 64-bit installations).
7. Click Next.
8. On the Profile screen, select the desired Network Profiles (Domain, Private, Public), then click Next.
9. Enter the Name and Description (for example, Sage 100 (10000)).
10. Click Finish.

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 and click Next.
4. In the Program dialog, select This program path.
5. Click Browse and go to C:\Sage\Sage 100 Advanced\Mas90\Home\.
6. Double-click exe.
7. Click Next.
8. On the Profile screen, select the desired Network Profiles, then click Next.
9. Enter Name and Description (for example, Sage 100 C\S ODBC Driver).
10. Click Finish.

Create Inbound Rule for SQL Server Instance and SQL Browser Service (Premium only)

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

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