Error Message | Resolution |
| Make sure your Domain Credentials are Correct. |
| Step 1 Navigate to Downloader in the Ceburu application. Navigate to the Tools section. Download the Session Creation(Windows).exe. Once it is downloaded, run the exe file to check if it can create the session with the IP for which you got the error.
Step 2 If it does not create the session, the issue might be related to Winrm. In the client machine to which 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.
Step 3 In the client machine to which you want to connect, press Win+R and search for Services.msc. In the services window, scroll down or use the alphabetical order to find the Windows Remote Management (WS-Management) service. Check the Status column for the Windows Remote Management (WS-Management) service. If it is Stopped, right-click and start it. Try to connect the machine again.
|
| Verify that the target computer is online. Try to ping the machine by running the below command in Command Prompt (ping<IP>) Ensure that the IP address specific is correct. In the client machine to which you want to connect, open the Windows Defender Firewall with Advanced Security. Check the Inbound rules for the File and Printer Sharing(Echo Request ICMPc4-In) rule. If it is not enabled, enable it and try to connect the machine again.
|
| |
| Step 1 Navigate to Downloader in the Ceburu application. Navigate to the Tools section. Download the Session Creation(Windows).exe. Once it is downloaded, run the exe file to check if it can create the session with the IP for which you got the error.
Step 2 If it does not create the session, the issue might be related to Winrm. In the client machine to which 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.
Step 3 In the client machine to which you want to connect, press Win+R and search for Services.msc. In the services window, scroll down or use the alphabetical order to find the Windows Remote Management (WS-Management) service. Check the Status column for the Windows Remote Management (WS-Management) service. If it is Stopped, right-click and start it. Try to connect the machine again.
|
| Ensure that your internet connection is stable. Ensure that the target system is reachable. Ensure that the machine is connecting with ssh command, <ssh username@IP> Ensure the port 22 is enabled by telnet the target machine. (telnet <IP> 22)
|
| |
|
|
Failed to install Ceburu in [xxx.xx.xxx] Connecting to remote server [xxx.xx.xxx] failed with the following error message: The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management Service running on the destination, most commonly IIS or WinRM service: winrm quickconfig. For more information, see the about_Remote_Troubleshooting Help topic.(lab)
| Ensure that the specified IP address is correct and the machine is reachable(online). Run the ping command to check if the remote computer is reachable, ping<remote_computer_ip> In the client machine which 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. In the client machine which you want to connect, press Win + R and search for services.msc. In the Services window, scroll down or use the alphabetical order to find the Windows Remote Management (WS- Management) service. Check the Status column for the Windows Remote Management service. If it is Stopped, right click and start it and try to connect the machine again.
|
| Attempt to reconnect to the remote machine and check the status of the running command. Verify that there is sufficient disk space on the machine server for the installation. Verify that there are no network issues between your local machine and the remorse machine.
|
[xxx.xx.xxx] - Ceburu Installation Failed. The term ‘New-SSHSession’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
| <Install-Module-Name SSHSessions> and try creating the session again. <Get-Module- ListAvailable-Name Posh-SSH> <Install-Module- Name Posh-SSH- Force-AllowClobber> |
| Step 1 Navigate to Downloader in the Ceburu application. Navigate to the Tools section. Download the Session Creation(Windows).exe. Once it is downloaded, run the exe file to check if it can create the session with the IP for which you got the error.
Step 2 If it does not create the session, the issue might be related to Winrm. In the client machine to which 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.
Step 3 In the client machine to which you want to connect, press Win+R and search for Services.msc. In the services window, scroll down or use the alphabetical order to find the Windows Remote Management (WS-Management) service. Check the Status column for the Windows Remote Management (WS-Management) service. If it is Stopped, right-click and start it. Try to connect the machine again.
|
| Verify if the user in the problem machine has Administrative rights. If not, provide the Administrative rights to the user and run the installer. Make sure your Domain Credentials are Correct.
|
| The error indicates a problem with the PowerShell Runspace, which is crucial for executing commands during the installation process. Check if the runspace state is opened by running the powershell command.
$runcpace=[runspacefactory]::CreateRunspace() $runspace.RunspaceStateInfo.State $runspace = [runspacefactory]::CreateRunspace() |
Failed to install Ceburu in [xxx.xx.xxx] Connecting to remote server [xxx.xx.xxx] failed with the following error message : WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is the WinRM service is enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet. For more information, see the about_Remote_Troubleshooting Help topic.
| Ensure that the specified IP address is correct and the machine is reachable(online). Run the ping command to check if the remote computer is reachable. ping<remote_computer_ip> In the client machine which you want to connect, press Win + R and search for services.msc. In the Services window, scroll down or use the alphabetical order to find the Windows Remote Management (WS-Management) service. Check the Status column for the Windows Remote MAnagement (WS- Management) service. If it is Stopped, right-click and start it and try to connect the machine again.
|
Failed to install Ceburu in [xxx.xx.xxx] - Ceburu Installation Failed. 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. For more information, see the about_Remote_Troubleshooting Help topic.
| Check the network connection in the probe as well as in the client machine. Make sure the remote server has enough resources (like memory and CPU utilization) and sufficient disk space. Verify if there is any antivirus or security software on the remote server that might be interfering with execution.
|
| Step 1 Navigate to Downloader in the Ceburu application. Navigate to the Tools section. Download the Session Creation(Windows).exe. Once it is downloaded, run the exe file to check if it can create the session with the IP for which you got the error.
Step 2 If it does not create the session, the issue might be related to Winrm. In the client machine to which 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.
Step 3 In the client machine to which you want to connect, press Win+R and search for Services.msc. In the services window, scroll down or use the alphabetical order to find the Windows Remote Management (WS-Management) service. Check the Status column for the Windows Remote Management (WS-Management) service. If it is Stopped, right-click and start it. Try to connect the machine again.
|
| Ensure that you have the correct credentials to access the remote server. Confirm that the credentials you are using have Administrative rights. Clear the browser cache to eliminate any stored authentication information. 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.
|
|
|
| Check if that particular subnet has any Windows or Linux OS devices as it is needed to run arp command to detect devices such as Printers, Routers, Switches, and Cameras. If there are no Windows or Linux OS devices in the subnet please add a device in the subnet and run the scanner from the Asset Status page in the Ceburu application for that specific subnet.
|
| Make sure your Domain Credentials are Correct. Confirm that the credentials you are using have Administrative rights. Verify that there are no network issues between your local machine and the remote machine.
|
| There might be a problem creating the session. In the client machine to which you want to connect, open the Windows Defender Firewall with Advanced Security . check the Inbounds 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. In the client machine which you want to connect, press Win + R and search for services.msc. In the Services window, scroll down or use the alphabetical order to find the Windows Remote Management (WS-Management) service. 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.
|
| Try connecting the machine with ssh command, ssh username@IP> If the connection cannot be made, SSH service might not be running on the target host. Check the status of SSH by running the command in the host machine terminal <sudo systemctl status sshd> If the service is not running, you can start it by the command <sudo systemctl start sshd>
|
| Keyboard-Interactive Authentication is a type of authentication method used in secure shell (SSH) protocols for connecting to remote servers. 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. Ensure that you are using the correct username and password for authentication.
|
| Ensure that the target system is reachable. (ping <IP>) Ensure that the firewall settings allows ICMP (Internet Control Message Protocol). Open Windows Defender Firewall with Advanced Security. Navigate to Inbound Rules and check for rules related to ICMP. Ensure that rules allowing ICMP traffic are enabled.
|