It’s hard to say exactly what is required without knowing your exact setup.
Hopefully, if you have the CMS installed correctly, you now can access it on your local network at http://ip.address where ip.address is the IP address of your Windows machine. So for example something like http://192.168.0.10
If the URL you’re using includes the word web, then the CMS isn’t installed correctly, and you should correct that before proceeding.
If that’s working as expected, then you’ll need to do the following:
- In your router, set a static reservation for that computer so that it always gets the same IP address
- Open inbound port 80 to that IP address from the public internet in your router’s port forwarding
- Configure a dynamic DNS service such that you have a publicly resolvable DNS name that resolves to your current public IP address - so for example, something like DynDNS offer this and might give you a name like sprinkles.dyndns-remote.com
- Your players would then be configured to connect to http://sprinkles.dyndns-remote.com. Keep in mind you need to run their update client to keep the public IP in sync as it changes over time.
- If you’re running a 1.8 series CMS, and have XMR running, you’ll also need to open inbound port 9505 and that should map to your server IP too.
As it’s available on the public internet, you should really secure that with HTTPS too, in which case you’ll need to close port 80 and open port 443 instead, and configure the players to talk to the https:// variant of your URL.
I’m not sure what the second part of your question relates to. What settings you set depends on how you want the CMS to function. The CMS post-installation guide stickied on the front page of the Community site is a good place to start.