The LanSchool Connection Service (LCS) is a client-server communication model used by LanSchool Classic to manage communication between teacher and student computers.
LCS helps simplify network communication in environments that use multiple VLANs, wired and wireless networks, or network configurations where peer-to-peer communication is restricted.
Instead of relying on teacher computers to discover student computers directly through network broadcasts, teacher and student computers connect through the LanSchool Connection Service.
The LCS should be installed on a dedicated Windows server or workstation that remains powered on and available to teacher and student computers.
For recommended server specifications, supported operating systems, and network requirements, see LanSchool Classic System Requirements.
Before installing the LanSchool Connection Service, verify the following:
You have access to a dedicated Windows server or workstation that will host the LCS.
The server meets the recommended LanSchool Connection Service system requirements.
You have administrator privileges to install software and modify Windows registry settings.
Teacher and student computers can communicate with the LCS server through the required network ports.
You have downloaded the LanSchool Classic installation files.
On the server or workstation where you want to install LCS, locate the LanSchool Classic installation files.
Open the Windows\ConnectionServer folder.
Double-click LCS.msi to start the installation.
Review the license agreement, select I accept the terms in the license agreement, and select Next.
Configure the security options, if needed:
Password Secure Mode: Requires teachers and students to enter the configured security password when subscribing to a channel.
Active Directory Secure Mode: Requires the LCS server to be joined to the domain and able to access the LanSchool Teachers Group.
Select Enable a security mode to enable one or both security options.
If desired, select Allow problem reports to be sent to Stoneware, Inc. to permit anonymous and confidential problem reports.
Select Next.
When the installation finishes, select Finish.
After installation, a LanSchool Connection Server shortcut is added to the Windows Start menu and desktop.
To verify that the service is running:
Open the LanSchool Connection Server shortcut.
Alternatively, open a web browser on the server and navigate to http://localhost:8085/.
Review the server status displayed in the browser.
If the server status page does not load, verify that the LanSchool Connection Server service is running in Windows Services.
The LanSchool Connection Service can automatically deliver software updates to Windows and macOS computers that already have LanSchool Teacher or LanSchool Student installed and configured.
For instructions, see Updating LanSchool Remotely.
If the computer hosting the LanSchool Connection Service has multiple network adapters (NICs), you can specify the IP address and subnet mask that the server should use for communication.
To configure the network adapter:
On the LCS server, open Windows Registry Editor (regedit.exe).
Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\LanSchool
Create the following two String (REG_SZ) values:
IPSubnet – Specifies the IP address of the network interface.
IPSubnetMask – Specifies the subnet mask of the network interface.
Restart the LanSchool Connection Server service through Windows Services.
By default, the LanSchool Connection Service uses TCP port 8080 for teacher and student communication.
If another application is already using TCP port 8080, you can configure LCS to use a different port.
Open Windows Registry Editor (regedit.exe).
Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\LanSchool
Create a new String (REG_SZ) value named:
ConnectionServerPort
Set the value to the new port number.
Restart the LanSchool Connection Server service through Windows Services.
The student computers must use the same port configured on the LCS server.
Create or update the following String (REG_SZ) registry value with the same port number:
32-bit Windows:
HKEY_LOCAL_MACHINE\SOFTWARE\LanSchool
64-bit Windows:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\LanSchool
Registry value:
ConnectionServerPort
Set the value to the new port number.
You can also configure the student connection server and port during a silent student installation using the following command:
msiexec /i student.msi /qn ADVANCED_OPTIONS=1 LCS=192.168.1.149:<NewPortNumber>
Replace 192.168.1.149 with the IP address of your LCS server and <NewPortNumber> with the configured port.
The LanSchool Connection Service can automatically assign unique teacher channels from a configured channel range.
This is useful for schools that want to reduce the need for teachers to manually manage channel assignments.
All teachers must be running LanSchool Teacher version 9.0.1 or later.
Teacher installations must initially use a channel number within the configured dynamic channel range.
The configured range must contain enough available channels for all teachers using LCS.
On the LCS server, open Windows Registry Editor (regedit.exe).
Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\LanSchool
Create the following registry values:
DynamicChannelStart – REG_DWORD (Decimal). Specifies the beginning of the channel range.
DynamicChannelStop – REG_DWORD (Decimal). Specifies the end of the channel range.
Restart the LanSchool Connection Server service through Windows Services.
To configure a dynamic channel range from 1000 to 5000:
DynamicChannelStart = 1000
DynamicChannelStop = 5000
The first teacher connecting to LCS keeps the initially assigned channel if that channel is within the configured range and is not already in use.
When another teacher connects using the same channel, LCS assigns that teacher an available channel within the configured range.
This process continues as additional teachers connect.
After a teacher receives a new channel, the channel is saved in the teacher computer's registry and used for future connections.
Important: If a teacher manually changes their channel to another number within the configured dynamic range, LCS will not automatically reassign that teacher. This allows schools to intentionally have multiple teachers share a channel but can also result in channel conflicts.No. LanSchool Classic can use either a peer-to-peer connection model or a client-server connection model with LCS. The connection model you choose depends on your network configuration and deployment requirements.
The LanSchool Connection Service manages communication between teacher and student computers. It is especially useful in environments with multiple VLANs, wired and wireless networks, or network configurations that restrict peer-to-peer communication.
Install LCS on a dedicated Windows server, workstation, or virtual machine that remains powered on and available to teacher and student computers.
Open the LanSchool Connection Server shortcut or navigate to http://localhost:8085/ in a web browser on the LCS server to view its status.
You can also check the LanSchool Connection Server service in Windows Services.
Yes. You can change the default TCP communication port by creating the ConnectionServerPort registry value on the LCS server and configuring the same port on the Windows student computers.
Yes. LCS supports automatic teacher channel assignment when configured with the DynamicChannelStart and DynamicChannelStop registry values. This feature requires LanSchool Teacher version 9.0.1 or later.
Yes. LCS can deliver software updates to supported Windows and macOS teacher and student computers that already have LanSchool installed and configured. See Updating LanSchool Remotely for instructions.
No. Migrating the LanSchool Connection Service (LCS) virtual machine from VMware to Hyper-V should not affect communication between teacher and student computers, provided the server retains the same static IP address.
Changing the virtual machine's MAC address during the migration should not prevent teacher and student computers from communicating with LCS. The existing LCS installation does not need to be reinstalled solely because of the hypervisor migration.
Important: Verify that the static IP address remains unchanged after the migration and that the required network connectivity and firewall rules are maintained.