Jeff it's kind of a loaded question because it introduces more questions which might even be more important, but here are my comments. They are my own opinion.
* Unless it has changed on current versions, the App Server does not use UDP ports.
* For performance, on the SPM, read all the points on bandwidth, VPN, recommendation of point-to-point connection over shared internet connection, ping times. This again begs question about RDS / Terminal Server / Citrix as using that mitigates latency.
* Absolutely enable the CS ODBC driver which runs on TCP 20222.
* Instead of VPN, some setup their Sage servers, typically in a data center, with both a static IP, and with IP based client restrictions where only whitelisted remote clients can connect. In most cases this runs much faster because there is no VPN overhead.
* Check box for
Low Speed Connection. Normally when Launcher task is run, the screen (Nomads library) loads 1st before underlying code does. Usually you can't see that with naked eye. But on slow WAN connection with no RDP/Citrix, you may see it, where screen loads and looks like it's ready to use. The box prevents any user input on screen until all the code behind the screen is loaded. (remote users were clicking the Next SO Number button too soon)
* Unlikely: If NAT support is required, you must check the
Spawn Task box in User Maintenance for all the remote users. If the Windows Firewall is also used on Sage server, then box is required for all users.
------------------------------
Alnoor Cassim
Email:
alnoor@asifocus.comPh: 949-689-9887
Orange County, CA
------------------------------
Original Message:
Sent: 07-19-2021 11:40
From: Kevin Moyes
Subject: Sage 100 Advanced TCP-IP Details - Network level
The SPM has some details with a few comments on minimums / VPN considerations / ping times...
------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------