Difference between revisions of "Windows Firewall rules"
Steve Cable (Talk | contribs) (→miniSim) |
Steve Cable (Talk | contribs) |
||
Line 1: | Line 1: | ||
− | When using a miniSim on a public network, it is recommended to scope network connections | + | When using a miniSim on a public network, it is recommended to scope network connections for a few different ports in Windows Firewall. To do this, you'll need to itemize the IPs (or ranges of IP addresses) that you want to allow access. |
For tips on how to create a custom Windows Firewall rule, [https://www.howtogeek.com/112564/how-to-create-advanced-firewall-rules-in-the-windows-firewall/ visit this link] and scroll down to the '''Example Rule: Restricting Access''' heading. | For tips on how to create a custom Windows Firewall rule, [https://www.howtogeek.com/112564/how-to-create-advanced-firewall-rules-in-the-windows-firewall/ visit this link] and scroll down to the '''Example Rule: Restricting Access''' heading. |
Revision as of 08:23, 24 July 2019
When using a miniSim on a public network, it is recommended to scope network connections for a few different ports in Windows Firewall. To do this, you'll need to itemize the IPs (or ranges of IP addresses) that you want to allow access.
For tips on how to create a custom Windows Firewall rule, visit this link and scroll down to the Example Rule: Restricting Access heading.
miniSim
Port | Type | Description |
---|---|---|
2554 | TCP | PSManager (all data is received) |
2555 | TCP | PSDict (talking to the dictionary) |
2556 | TCP | PSManager (subscribers talk to PSManager) |
9000 | TCP | SimopServer |
10123 | TCP | FTP from Simop to LocalCoordinator |
- Simop Server
%SystemDrive%\miniSim_install_dir\bin.x64\SimopServer.exe - Visual Server
%SystemDrive%\miniSim_install_dir\bin.x64\NadsMiniSimVisualServer.exe - Publish/Subscribe Dictionary
%SystemDrive%\miniSim_install_dir\bin.x64\PubDict.exe - Publish/Subscribe Manager
%SystemDrive%\miniSim_install_dir\bin.x64\PSManager.exe