GComm guide

Set up your GComm service

The installer creates and starts the Windows service. Your first job in Server Manager is to create channels, check access, and invite devices.

For Server 8.1.0 / Server Manager 2.1.0 and Desktop 10.1.0. English control names are shown; your app may use your Windows language.

1. Create channels for your group

  1. Open GComm Server Manager on the host computer.Use its Start menu shortcut. If the window reports standard access, choose Run as administrator to make changes. The manager normally detects the installed service.
  2. Find the Channels panel.It loads the server’s channels automatically. A new server includes General. If you do not see the list, choose Refresh channels. Save or reload unsaved settings first if refresh is disabled.
  3. Create your first named channel.Enter Office in Channel name. Enter a six-digit color such as #6495ED in Channel color, then choose Create channel. Repeat for Family, or use names suited to your group.
  4. Decide who belongs together.Devices that share at least one channel can see and contact one another. Give a person’s device Office, Family, or both. Review all checked channels before creating each invitation.
  5. Decide what to do with General.Keep it for a shared group if you want one. If Office and Family should remain separate, clear General when assigning devices. It is a normal channel and can reconnect groups you intended to separate.
Example: Alex and Morgan belong to Office; Sam belongs to Office and Family; Casey and Taylor belong to Family. Sam sees both groups; the groups do not see each other without a shared channel.
Illustrative membership plan. Each name represents one registered device.

2. Confirm the service is ready

  1. Check the selected server and service state.Confirm Server Manager points to the installation you intend to manage. If auto-detection did not select it, use Browse to select the server executable. Service controls apply to the installed server.
  2. Check that the service is running.The installer normally leaves it running. If it is stopped, use Start. If you changed its port or passphrase, choose Save settings, then Restart.
  3. Choose Test local connection.In Connection diagnostics, wait for a successful local HTTPS check. This confirms the local service; it does not prove another computer can reach it.
  4. Note the connection details.Under Connect your clients, review the host addresses and port. The usual port is 8443; use the value actually shown. Copy connection details includes addresses and the certificate fingerprint, but omits the shared passphrase.

3. Let the right computers reach it

For computers on the same private LAN

  1. Choose Allow private LAN.This creates an inbound rule for this server’s TCP port and installed executable, from the local subnet on Windows Private networks. It does not enable access from every network.
  2. Use the server’s reachable LAN address.From another computer, use the host name or LAN IP shown in Manager. localhost and 127.0.0.1 point to the client’s own computer; use them only when Desktop runs on the server computer.
  3. Test from a second computer.Follow the Desktop guide with a fresh invitation. If it cannot connect, confirm both computers can reach one another and the host network is classified appropriately. A guest or isolated Wi-Fi network may block local devices.

For VPN or internet clients

  1. Choose Set up remote access.Enter the Client server address as a hostname or IP, without https://, a port, or a path. Enter the Port clients use.
  2. Choose who may connect.Use VPN or specific IP addresses and enter the intended IP addresses or CIDR ranges, or deliberately choose Internet access for clients anywhere. The latter allows any source address on this GComm port; enrollment and channel checks still apply.
  3. Choose Apply remote access.Manager saves the address for new invitations and adds a separate Windows Firewall rule limited to GComm’s installed executable and listening port. Your private-LAN rule stays in place.
  4. Configure the network outside Windows.Set up VPN routing, or the router’s TCP port mapping and any cloud firewall/security-group rules needed for your server. Manager does not change your router, DNS, or cloud account. If a router maps a different public port to the server port, put that public port in Port clients use.
  5. Verify from outside the server’s network.Use a remote client and a fresh invitation. A successful Test local connection cannot verify public routing or VPN access. To undo Manager’s changes, use Remove remote access setup; router and cloud settings must be changed separately.

4. Invite the first device

Once channels and the connection address are ready, select the intended channel checkboxes and create one invitation per device. The invitation carries the server information and enrolls the device; the recipient also needs the shared passphrase.

Create an invitation & copyable email →

If something is unavailable

What you seeWhat to check
A disabled controlRest the pointer on it for its specific explanation. Common causes are standard access, no installed server selected, unsaved settings, a stopped service, or no device/channel selected.
Channels are missingCheck the selected installation. Save or reload settings, then choose Refresh channels. Read the message beside the channel list.
Local connection check failsVerify the service is running and review the status message. Use Event Viewer → Windows Logs → Application for GComm server events.
Local check passes; another PC cannot connectCheck the client’s destination, the Private LAN rule and network profile, routing, and guest/client isolation. Local success does not test the LAN path.
An upgrade reports a certificate changeVerify the intended server and fingerprint with the administrator. Preserve the existing data/certificate folder when upgrading; do not bypass a mismatch just to connect.