Network ports
See listening services and inspect port conflicts on a remote host.
Before you start
- Use ShellMate 3.3.0 and select the intended account or workspace.
- Confirm the host/provider access and permissions required by this guide.
Let’s walk through it.
- 01
Open Network Ports
Select the remote session and open its Network Ports tool.
- 02
Inspect listeners
Review available port, address and owning-process information.
- 03
Locate conflicts
Match the listening process to the application you are investigating. Refresh to confirm its current state.
- 04
Act only on the intended process
If termination is available and appropriate, inspect the confirmation and selected PID. Otherwise use the application’s service manager.
What success looks like
Complete the walkthrough, then verify the result in the selected host or account view. Read any failure or partial-result message before repeating an action.
Good to know.
Visibility is permission-dependent
The remote user may not be able to see every process owner. A listener is not proof that a port is publicly reachable; firewalls and routing still apply.
Forwarding is separate
Port inspection does not create a tunnel. Use the Port Forwarding tool to configure a supported tunnel.
A few common questions.
The process name is missing
The server may restrict process visibility. Check remote permissions rather than assuming the port has no owner.