Lanview DocsSupport and administration
Docs / Troubleshooting

Client Deployment Troubleshooting

Use this article when Lanview Client installs but the device does not appear in Studio, does not connect to Server or does not behave as expected after deployment.

Confirm the Client service

On the managed device, open Windows Services and check the LanviewClient service.

Confirm that:

  • the service exists
  • the service is set to start automatically
  • the service is running

Confirm the Server host and port

On a fresh install, the Client requires a Server host name or Internet Protocol (IP) address.

Silent deployment normally supplies this using MSI properties:

msiexec /i "Lanview Client v5.x.x.msi" SERVERHOST=server01 SERVERPORT=45750 /qn

Ensure these are properties are correct. When using the DNS name, ensure this resolves to the correct server IP address.

If SERVERPORT is omitted, the default Client connection port is used.

If SERVERHOST is omitted on a fresh install, the installer does not create a placeholder Client configuration and does not start the Client service during installer bootstrap.

Confirm network reachability

Lanview Client connects outbound to Lanview Server using Transmission Control Protocol (TCP).

By default, Clients connect to TCP port 45750 on the Server.

Check:

  • DNS name resolution
  • network routing
  • local firewall rules on the Server
  • local firewall or endpoint security rules on the Client
  • whether the Client is pointing to the correct Server name and port

User Datagram Protocol (UDP) is not used for Lanview command traffic. UDP is only relevant to Wake-on-LAN.

Check whether the device is pending approval

A newly connected Client may appear in Studio as pending approval.

In Studio, go to Devices and check pending devices. If the device is pending, approve it using the normal device approval process.

Approval can be affected by permissions, licence limits and Client identity policy.

Check Client identity and trust state

If Client identity requirements are enabled, a device may be refused when required trust checks cannot be completed.

Use Studio device status, audit records and Server diagnostics to identify trust-related refusal. Do not manually delete or replace identity or trust material on the endpoint as a troubleshooting shortcut.

It may be necessary to reset the trust between Server and Client. This can be done by manually running the Reset Server Trust command. 

Lanview.Client.exe --reset-server-trust

Useful checks from Lanview

From Studio or the appropriate console surface, useful commands include:

device.show <deviceId|machineName>
device.ping <deviceId|machineName>
config.clientidentity.mode