Docs / Troubleshooting

Troubleshooting Device Connectivity

This article helps diagnose why a managed Windows device is not visible, online or manageable in Lanview Studio.

Lanview Client connects outbound to Lanview Server over persistent Transmission Control Protocol (TCP). Lanview Server sends commands over that existing Client connection.

Common causes

Connectivity issues usually fall into one of these areas:

Area	Examples
Network path	Client cannot reach Lanview Server.
Client service	Lanview Client is not installed, not configured or not running.
Approval state	Device is pending, rejected, blocked or deleted.
Client identity	Device identity is missing, failed or not trusted under current policy.
Permissions	The Studio user can see less than expected or cannot run actions.
Status thresholds	Device is timed out or marked lost based on Server status settings.
Target state	Device is powered off, sleeping or disconnected.

Start with the device list

In Lanview Studio, check the Devices list for:

Current status.
Approval state.
Last seen information.
Device name and identity summary.
Whether the device appears pending, rejected, blocked or deleted.

If the device is pending, approve or reassociate it through the correct process before expecting normal management actions to work.

Check the Device Window

If the Device Window can be opened, review:

Summary for device status.
Network for reported network information.
Lanview or identity areas where available.
Audit Log for recent approval, trust, rejection or failure events.
Task List for failed commands or timed-out actions.

Run basic diagnostics

Useful diagnostic commands may include:

device.show <deviceId|machineName>
device.ping <deviceId|machineName>
group.status
server.status
admin.listener.status
network.interfaces

Required permissions

Permission	Allows
`devices.view`	View managed devices and status.
`device.summary.view`	View device summary details.
`device.speed_test.run`	Run Lanview Server-to-Client link speed tests where available.
`Settings.Server.View`	View Server status and diagnostic settings.
`Settings.Server.Manage`	Change Server status and connectivity settings.

Common fixes

Device is pending

Approve the device, reject it, or use reassociation if it represents a rebuild or replacement.

Device is blocked

Review why it was blocked before unblocking. Blocking is a trust and access decision, not just a display state.

Device identity failed

Review Client identity status and use supported reset, rebind or reassociation processes where appropriate.

Client cannot reach Server

Check DNS, routing, firewall rules and the configured Server host and port used by the Client.

Studio user cannot run actions

Check the user’s Lanview roles and permissions. A device can be online while the operator still lacks permission to perform the action.