Server Installation Troubleshooting
Use this article when Lanview Server has been installed but does not appear to start, accept Studio connections or allow first administrator bootstrap.
Check the Server service
Open Windows Services on the Server machine and check the LanviewServer service.
Confirm that:
- the service exists
- the startup type is automatic
- the service is running
If the service is stopped, start it and check the Server logs if it stops again.
Check the startup configuration
Lanview Server reads its startup configuration when the service starts.
If startup configuration is incomplete or invalid, the service may run without accepting Client or Studio connections.
Use Lanview AdminConsole to check Server status.
Useful commands include:
server.status
server.paths
server.start
admin.listener.status
server.bindcheck
security.statusConfirm the expected ports
By default:
| Purpose | Default port |
|---|---|
| Client connections to Server | TCP 45750 |
| Studio connections to Server | TCP 45751 |
If Studio cannot connect, check the Server service, the Studio connection port, Windows Firewall and the configured administration bind address.
Check firewall rules
The Lanview installer creates the normal Windows Firewall rules. Group Policy or security software may replace, disable or remove them.
Confirm that inbound TCP 45750 is permitted for Client connections and inbound TCP 45751 is permitted for Studio connections, or use the configured replacement ports.
Restrict the Studio connection port to trusted administrator networks where practical.
Use AdminConsole for local checks
Lanview AdminConsole is installed with Lanview Server and is intended for privileged local administration.
Use AdminConsole when Studio cannot connect or when the first administrator account needs to be created.
Typical local checks include:
security.status
server.status
server.paths
admin.pipeinfoFirst administrator bootstrap problems
If no enabled Server administrator exists, Lanview requires bootstrap before normal Studio administration can begin.
Use AdminConsole on the Server machine to check bootstrap status and create the initial administrator account when required.
After bootstrap, sign in with Studio using the new Lanview operator account.
Common causes
Studio is using the wrong port
Studio connects to TCP 45751 by default. Clients connect to TCP 45750 by default.
The Server service is running but connections are not available
Check startup configuration and run server.status or admin.listener.status in AdminConsole.
Windows Firewall is blocking the connection
The installer creates firewall rules, but Group Policy or security software may override them. Restore or recreate the required inbound rules.
The administration bind address is too restrictive
The administration bind address controls which local network interface or address accepts Studio connections.
If it is set to a loopback address, Studio can connect only from the Server itself. If it is set to one specific Server address, Studio must connect through that interface and address.
Use AdminConsole to review the current configuration. Either connect Studio using an address covered by the existing setting or change the administration bind address through a supported Server configuration method. Restart Lanview Server if the setting requires it.
Avoid binding the administration connection to every interface unless that matches the network design and firewall restrictions.
Authentication or two-factor authentication is blocking sign-in
If the connection succeeds but login fails, check the account state, role assignment and two-factor authentication requirement.