---
title: "How Do I Set Up a Remote Connection to Lasernet 10 Server from a Local Machine?"
slug: "set-up-remote-connection-to-lasernet-10-server-from-local"
description: "This article describes the setup required to remotely connect to a Lasernet server from a local machine. Read for more information."
updated: 2026-03-04T08:57:41Z
published: 2026-03-04T08:57:41Z
canonical: "kb.lasernetgroup.com/set-up-remote-connection-to-lasernet-10-server-from-local"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.lasernetgroup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How Do I Set Up a Remote Connection to Lasernet 10 Server from a Local Machine?

**Applies to:** Lasernet Core 10

This article describes the setup required to remotely connect to a Lasernet server from a local machine. This lets you make development changes on your local machine and deploy them to your remote Lasernet server.

> [!WARNING]
> Warning
> 
> Ensure the Lasernet Server has a public IP address associated with it and a Fully Qualified Domain Name (FDQN). The Lasernet Server and Lasernet Web Client must be installed on your Lasernet Server.

## Lasernet Server Setup

1. Stop the following Lasernet Services in **services.msc**.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-CMIA9D3P.png)

1. Navigate to `C:\ProgramData\Formpipe Software\Lasernet 10\Config\Default`.
2. Open **ServerSettings.json** with Notepad or Notepad++.
3. Under the **Server Name**, add the FQDN and save the changes.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-AGERASZX.jpg)

1. Start the Lasernet Services within **services.msc**.
2. Open the **config.lnlog** within `C:\ProgramData\Formpipe Software\Lasernet 10\Config\Default`. This is the log for the configuration server.
3. Ensure the **Listening on** `https://servername.local.cloudapp.azure.com:33443/` with your FQDN is visible.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-SNINR810.png)

## Ports

To reach your Lasernet server remotely, you must enable the connection to the Lasernet port. The default Lasernet 10 port is **33443**.

> [!NOTE]
> Note
> 
> Reach out to your IT department regarding the following steps as your security settings may need adjusting.

The following example is the newly opened inbound port in Windows Defender Firewall:

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-8W8P42TF.png)

## Hosted on Azure

If your server is hosted on Azure, you will need to add an NSG inbound port rule.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-SZPOBBPL.png)

Ensure you open port **33443** and pick **TCP**.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-4WAKO3RA.png)

## Access Lasernet Web Portal with FQDN

You can access the Web Portal by browsing `https://FQDN:33443/lasernet/`. In our example, the FQDN is `servername.location.cloudapp.azure.com`, but yours may vary.

> [!NOTE]
> Info
> 
> If the "Your connection isn't private" error shows up, select advanced, and click **continue to FQDN.com (unsafe)**.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/1666776675825.png)

## Connect to the Lasernet Server from Lasernet Developer on a Local Machine

1. Install Lasernet Developer on your local machine and load a valid license into the Developer License Manager.
2. Launch Lasernet Developer on your local machine.
3. Set the server to the FQDN of the server that you created previously and click **Connect**.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-FPFP8A8B.png)

1. Enter your login credentials.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-HI4S2FI7.png)

The Lasernet Developer on your local machine is now connected to your Lasernet Server. You can make developments on Lasernet Developer locally. Any objects that you create will be saved and deployed on the Lasernet Server.

## Verify Successful Connection

1. From Lasernet Developer, if you can successfully click **Connect** with your provided **FQDN** to retrieve the **Sign** **In** dialog, you have successfully verified access from your application to the Lasernet Config Server.
2. If you accessed the provided URL from a web browser and received the **Sign** **In** dialog or the message "**Y****our connection isn't private**”, you have successfully verified access to the Lasernet Config Server.