Chapter 2: Install and Check APPX ODBC
Check the Client-to-Gateway and Gateway-to-APPX Connections
| Connection | Initiating computer | Destination | Sample TCP port | Configuration |
|---|---|---|---|---|
| ODBC client to gateway | Windows desktop running Excel, Calc, PowerShell or another client | Gateway server | 1990 | DSN Host and Service; local sqlnw mapping |
| Gateway to APPX | Gateway server | APPX server's login manager | 31052 | appx.dbs\appx.env, APPX_DATA_SERVER |
These endpoints may be on one computer, two computers, or three. Pipe is the tested login manager's interface to its Windows APPX engine; it does not remove either network endpoint above. Use the site's configured ports rather than changing them to match this laboratory example.
On the desktop, run this in PowerShell, replacing the hostname:
Test-NetConnection gateway.example.internal -Port 1990
On the gateway server, check its APPX endpoint:
Test-NetConnection appx.example.internal -Port 31052
TcpTestSucceeded : True establishes a TCP connection to that address and port. It does not test the APPX login, SQL dictionary, table definitions or field conversion. Run the COUNTRY query for those checks. A failed first hop directs attention to the gateway listener, DNS, routing and the client-facing firewall; a failed second hop directs attention to the login manager and gateway-to-APPX path.
Configure firewall access for the required clients and backend connection through the site's normal administration process. Do not open a login-manager or gateway port to unrelated networks merely to troubleshoot a local DSN. The services file resolves a name to a port; it does not start a listener or create a firewall rule.