Installation Troubleshooting Guide

1. What to do if you get "We cannot reach the device"?
a. Verify that the target computer is online.
b. Try to ping the machine by running the command in "Command Prompt" - (ping ).
c. Ensure that the IP address specified is correct.
d. In the machine which you want to connect, open the "Windows Defender Firewall with Advanced Security".
e. Check the Inbound Rules for the "File and Printer Sharing (Echo Request - ICMPv4-In)" rule. If it is not enabled, enable it and try to connect the machine again.

2. What to do if you get "Failed to establish WinRM connection"?
a. Ensure that the specified IP address is correct and the machine is reachable (online).
b. Run the ping command to check if the remote computer is reachable-ping <remote_computer_ip>.
c. In the machine that you want to connect, open the "Windows Defender Firewall with Advanced Security".
Check the Inbound Rules "Windows Remote Management (HTTP-In)" rule.
If it is not enabled, enable it and try to connect the machine again.
d. In the machine that you want to connect, press "Win+R" and search for "services.msc".
In the Services window, scroll down or use the alphabetical sort to find the "Windows Remote Management (WS-Management)" service.
e. Check the "Status" column for the "Windows Remote Management (WS-Management)" service.
If it is in "Stopped" state, right-click and start the service.Then try to connect the machine again.

3. What to do if you get "The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests"?
a. Ensure that the specified IP address is correct and the machine is reachable (online).
b. Run the ping command to check if the remote computer is reachable-ping <remote_computer_ip>.
c. In the machine that you want to connect, open the "Windows Defender Firewall with Advanced Security".
Check the Inbound Rules "Windows Remote Management (HTTP-In)" rule.
If it is not enabled, enable it and try to connect the machine again.
d. In the machine that you want to connect, press "Win+R" and search for "services.msc".
In the Services window, scroll down or use the alphabetical sort to find the "Windows Remote Management (WS-Management)" service.
e. Check the "Status" column for the "Windows Remote Management (WS-Management)" service.
If it is in "Stopped" state, right-click and start it and try to connect the machine again.

4. What to do if you get "We couldn't find any Windows or Linux OS devices"?
a. Check if that particular subnet has any Windows or Linux OS devices.
Ceburu needs at least a single Windows or Linux system in that subnet to detect all devices like Printers, Routers, Switches, Cameras, etc.
b. If there are no Windows or Linux OS devices in that subnet, please add a device in the subnet and run the scanner from the "Asset Status" page again.

5. What to do if you get "Unable execute ARP command"?
a. There might be a problem creating the session.
b. In the machine that you want to connect, open the "Windows Defender Firewall with Advanced Security".
Check the Inbound Rules "Windows Remote Management (HTTP-In)" rule.
If it is not enabled, enable it and run the scanner from the "Asset Status" page in the Ceburu application for that specific IP.
c. In the machine that you want to connect, press "Win+R" and search for "services.msc".
In the Services window, scroll down or use the alphabetical sort to find the "Windows Remote Management (WS-Management)" service.
d. Check the "Status" column for the "Windows Remote Management (WS-Management)" service.
If it is "Stopped", right-click and start it and run the scanner from the "Asset Status" page in the Ceburu application for that specific IP.

6. What to do if you get "Ceburu Installation Failed. Permission denied (password)"?
Make sure your Domain Credentials are Correct.

7. What to do if you get "Unable to Create Session" or "Session operation has timed out"?
a. Go to the "Download Files" Page in the Ceburu application.
From the Tools section, download the "Session Creation (Windows)" for Windows Systems and "Session Creation (Linux)" for Linux systems, then run the executable file.
Enter the IP to be checked when you get the prompt.
b. If the session is not created, the issue may be related to WinRM.
c. In the machine that you want to connect, open the "Windows Defender Firewall with Advanced Security".
d. Check the Inbound Rules "Windows Remote Management (HTTP-In)" rule. If it is not enabled, enable it and try to connect the machine again.
e. In the machine that you want to connect, press "Win+R" and search for "services.msc".In the Services window, scroll down or use the alphabetical sort to find the "Windows Remote Management (WS-Management)" service. Check the "Status" column for the "Windows Remote Management (WS-Management)" service. If it is in "Stopped" state, right-click and start it and try to connect the machine again.

8. What to do if you get "Connection failed to establish within 10000 milliseconds" or "No connection could be made because the target machine actively refused it"?
a. Try connecting the machine with "SSH" command - <SSH username@IP>.

9. What to do if you get "The term 'New-SSHSession' is not recognized as the name of a cmdlet"?
a. Install SSHSession by running the PowerShell command:
<Install-Module -Name SSHSessions> and try creating the session again.
b. If the issue persists, check if "Posh-SSH" is available by running the PowerShell command:
<Get-Module -ListAvailable -Name Posh-SSH>.
c. If "Posh-SSH" is not available, install it by running the PowerShell command:
<Install-Module -Name Posh-SSH -Force -AllowClobber> and try again.

10. What to do if you get "The running command has been disconnected but is still running on the remote server. Reconnect to get command operation status and output data"?
a. Attempt to reconnect to the remote session and verify the status of the running command.
b. Verify that the issue is sufficiently resolved before terminating the session.
c. If necessary, re-run the command after reconnecting.

11. What to do if you get "Cannot validate argument on parameter 'Session'. The argument is null or empty"?
a. Verify the system is creating a session to the remote machine (if the remote machine is Windows)
by going to the "Download" Page in the Ceburu application.
From the Tools section, download the "Session Creation (Windows)" for Windows Systems
and "Session Creation (Linux)" for Linux systems, then run the executable file.
Enter the IP to be checked when you get the prompt.
b. If the session is not created, the issue may be related to WinRM.
c. In the machine that you want to connect, open the "Windows Defender Firewall with Advanced Security".
Check the Inbound Rules "Windows Remote Management (HTTP-In)" rule.
If it is not enabled, enable it and try to connect the machine again.
d. In the machine that you want to connect, press "Win+R" and search for "services.msc". In the Services window, scroll down or use the alphabetical sort to find the "Windows Remote Management (WS-Management)" service. Check the "Status" column for the "Windows Remote Management (WS-Management)" service. If it is in "Stopped" state, right-click and start it and try to connect the machine again.

12. What to do if you get "No valid sessions were specified. Ensure you provide valid sessions that are in the Opened state and are available to run commands"?
a. Verify if the system is creating a session to the remote machine (if the remote machine is Windows)
by going to the "Downloader" Page in the Ceburu application.
From the Tools section, download the "Session Creation (Windows)" executable and run it.
Check if it is able to create the session with the IP for which you got the error.
b. If the session is not created, the issue may be related to WinRM.
c. In the machine that you want to connect, open the "Windows Defender Firewall with Advanced Security".
Check the Inbound Rules "Windows Remote Management (HTTP-In)" rule.
If it is not enabled, enable it and try to connect the machine again.
d. In the machine that you want to connect, press "Win+R" and search for "services.msc". In the Services window, scroll down or use the alphabetical sort to find the "Windows Remote Management (WS-Management)" service. Check the "Status" column for the "Windows Remote Management (WS-Management)" service. If it is in "Stopped" state, right-click and start it and try to connect the machine again.

13. What to do if you get "Starting a command on the remote server failed with the following error message: The I/O operation has been aborted because of either a thread exit or an application request"?
a. Check the network connection in the probe as well as in the machine.
b. Make sure the remote server has enough resources (like memory and CPU utilization) and has sufficient disk space.
c. Verify if there are any antivirus or security software on the remote server that might be interfering with the execution.
d. If any AV or EPR tools are running, whitelist ceburu.com and try again.

14. What to do if you get "Connecting to remote server [xxx.xx.xxx] failed with the following error message: Access is denied"?
a. Check if the user in the remote machine has administrative rights.
If not, log in with administrative rights and run the installer again.
b. Make sure your Domain Credentials are Correct.

15. What to do if you get "Cannot invoke the pipeline because the runspace is not in the Opened state. Current state of the runspace is 'Broken'"?
a. The error indicates a problem with the PowerShell Runspace, which is crucial for executing commands during the installation process.
b. Check if the runspace state is opened by running the PowerShell command:
powershell $runspace = [runspacefactory]::CreateRunspace() + $runspace.RunspaceStateInfo.State   

c. If the State is "Closed", first you have to bring it to the "BeforeOpen" state by creating a runspace:
powershell $runspace = [runspacefactory]::CreateRunspace()       
d. Now open the State of Runspace by running:
powershell $runspace.Open()   

16. What to do if you get "The remote server returned an error: (401) Unauthorized"?
a. Ensure that you have the correct credentials to access the remote server.
b. Confirm that the credentials you are using have administrative rights.
c. Clear the browser cache to eliminate any stored authentication information.
d. If you've recently changed credentials (username, password, or authentication token) but the remote machine is still using cached credentials, it could result in authentication failures. In such cases, try clearing any credential caches on the remote machine.

17. What to do if you get "Access denied FATAL ERROR: Configured password was not accepted"?
a. Make sure your Domain Credentials are Correct.
b. Confirm that the credentials you are using have administrative rights.
c. Verify that there are no network issues between your local machine and the remote machine.

18. What to do if you get "ARP Scanning failed: FATAL ERROR: Network error: Connection timed out"?
a. Try connecting the machine with the "SSH" command - <SSH username@IP>.
b. If the connection cannot be made, the SSH service might not be running on the target host.
Check the status of SSH by running the command in the host machine terminal - bash sudo systemctl status SSHd   
c. If the service is not running, you can start it by running - bash sudo systemctl start SSHd       

19. What to do if you get "Keyboard-interactive authentication prompts from server: End of keyboard-interactive prompts from server Access denied -- Keyboard-interactive authentication prompts from server: FATAL ERROR: Configured password was not accepted"?
a. Keyboard-Interactive Authentication is a type of authentication method used in Secure Shell (SSH) protocols for connecting to remote servers.
b. It seems that during an ARP scan, there was an attempt to access a server using keyboard-interactive authentication, but the provided password was not accepted, leading to access being denied.
c. Ensure that you are using the correct username and password for authentication.

20. What to do if you get "FATAL ERROR: Network error: Software caused connection abort"?
a. Ensure that the target system is reachable - bash ping <IP>       
b. Ensure that the firewall settings allow ICMP (Internet Control Message Protocol).
c. Open "Windows Defender Firewall with Advanced Security".
d. Navigate to "Inbound Rules" and check for rules related to ICMP.
e. Ensure that rules allowing ICMP traffic are enabled.

21. What to do if you get "An established connection was aborted by the server"?
a. Ensure that your internet connection is stable.
b. Ensure that the target system is reachable - bash ping <IP>       
c. Make sure your Domain Credentials are Correct.
d. Ensure the machine is connecting with "SSH" command - bash SSH username@IP       
e. Ensure that port 22 is enabled by running the following command on the target machine - bash telnet <IP> 22