Lanview DocsSupport and administration
Docs / Troubleshooting

Studio Connection Troubleshooting

Use this article when Lanview Studio cannot connect to Lanview Server or when the connection succeeds but sign-in fails.

Check the Studio connection port

Lanview Studio connects to the Server's administration connection port.

The default Studio port is Transmission Control Protocol (TCP) 45751. This is separate from the Client connection port, which is TCP 45750 by default.

If Studio is configured to use the Client port, the connection will fail.

Check Server status locally

When Studio cannot connect, use AdminConsole on the Server machine.

Useful commands include:

server.status
admin.listener.status
server.sessions
security.status
admin.pipeinfo

These checks help distinguish between a stopped Server, an unavailable connection port, a firewall problem and an authentication problem.

Check firewall and network path

Verify that the Server allows inbound TCP traffic to the Studio connection port from the administrator workstation.

Also check:

  • Domain Name System (DNS) resolution
  • routing between the workstation and Server
  • Windows Firewall rules
  • Group Policy firewall rules
  • endpoint security products that may block the connection

Check the administration bind address

The administration bind address controls which Server network interface or address accepts Studio connections.

If it is restricted to another interface or to the local Server only, Studio may be unable to connect from a different computer even though the Server service is running.

Review the current setting with AdminConsole and use a Server address covered by that setting.

Check authentication state

If Studio reaches the Server but sign-in fails, check:

  • the username and password
  • whether the account is enabled
  • whether the account has permission to sign in to Studio
  • whether two-factor authentication is required
  • whether the user needs to complete two-factor setup
  • whether the account has the required module permissions after sign-in

Authentication failures and rejected logins are audited.

Check session limits

The Server can limit total administration connections and unauthenticated sessions.

If too many sessions are open, or repeated failed sign-in attempts are consuming unauthenticated session capacity, a new Studio connection may be refused.

Use AdminConsole diagnostics to review the current session state.

Common causes

Studio is using TCP 45750 instead of TCP 45751

TCP 45750 is the default Client connection port. Studio uses TCP 45751 by default.

The Server service is running but the Studio connection is unavailable

Use admin.listener.status in AdminConsole to check the administration connection.

Two-factor authentication setup is required

A user may need to complete two-factor authentication setup before normal access is allowed.

The user can sign in but cannot see expected modules

Check the user's assigned roles and effective permissions.