OpenEdge 11.7.x and prior: firewall rule exceptions based on process image name are needed for _sqlsrv2, _mprosrv
- Both ABL and SQL remote client need to first connect to the Login Broker process: _mprosrv (inbound)
- SQL remote clients, connect to the Remote Server process: _sqlsv2 (outbound/inbound)
- ABL remote clients, connect to the Remote Server process: _mprosrv (outbound/inbound)
In OpenEdge 12: firewall rule exceptions based on process image name are needed for _sqlsrv2, _mprosrv and _mtprosrv
- Both ABL and SQL remote client need to first connect to the Login Broker process: _mprosrv (inbound)
- SQL remote clients, connect to the Remote Server process: _sqlsv2 (outbound/inbound)
- ABL remote clients connecting to a single-threaded database Server process is: _mprosrv (outbound/inbound)
- ABL remote clients connecting to a multithreaded database Server process is: _mtprosrv (outbound/inbound)
For further information refer to Article
Starting the multithreaded database server To accept all incoming TCP connections to OpenEdge databases based on Broker / Server process image names:netsh advfirewall firewall add rule name="OE BRK and ABLSRV" dir=in action=allow protocol=TCP program="<dlc>\bin\_mprosrv.exe" enable=yes
netsh advfirewall firewall add rule name="OE ABL TSRV" dir=in action=allow protocol=TCP program="<dlc>\bin\_mtprosrv.exe" enable=yes
netsh advfirewall firewall add rule name="OE ABL TSRV" dir=out action=allow protocol=TCP program="<dlc>\bin\_mtprosrv.exe" enable=yes
netsh advfirewall firewall add rule name="OE SQLSRV" dir=in action=allow protocol=TCP program="<dlc>\bin\_sqlsrv2.exe" enable=yes
netsh advfirewall firewall add rule name="OE SQLSRV" dir=out action=allow protocol=TCP program="<dlc>\bin\_sqlsrv2.exe" enable=yes
Once the Firewall rules have been added based on the respective OpenEdge executables, navigate to:
'Start -> Administrative Tools -> Windows Firewall with Advanced Security'
