GM's machine barriers
Last updated
Was this helpful?
Last updated
Was this helpful?
Was this helpful?
These first 3 points relate to the configuration of the GM's machine/OS.
Breaking these barriers should be enough to successfully host a game for players located in your own home network, even if you are in a no-go situation for remote player access.
If you have a third-party protection software installed, it may "take over" some settings from Windows 10 itself : you may then find them in the third-party software settings.
Windows 10 has a setting to classify each network it is connected to as :
either "pubic" (read : "not safe")
or "private" (read : "safe")
Windows 10 will prevent incoming connections from "public" networks, including Fantasy Grounds, so be sure to 👍 tag your current W10 network connection as "private", or else... 👎
How to change your Windows network connections between "Public" and "Private"
TODO : W10 screenshots needed here
Be sure to 👍 allow incoming communications to your TCP 1802, or better yet 👍👍 to your Fantasy Grounds executable program in the operating system firewall, or else... 👎
Here is an example of Windows 7 firewall rules authorizing any kind of incoming connection to the Fantasy Grounds program, with TCP+UDP protocols and the "ALL" value for networks, adresses and ports parameters (W7 Firewall "advanced" view) :
TODO : W10 screenshots needed here
If you are using any kind of third-party anti- malware/virus/threat protection software, chances are that you also need to 👍 enable incoming communications for FG in these, or else... 👎
TODO : Other screenshots needed here ??
