Follow

KID How to test for network connectivity from a "Disk boot"

Symptom

You maybe unable to perform imaging tasks from a "Disk Boot"

 

Diagnostics 

It's possible that you're unable to connect to the repository and therefore aren't unable to image your machines.

For a machine to be imaged successfully it needs to be able to contact the repository and Kaseya server on their ip address (no DNS) 

Assuming that the servers will reply to "Pings" then you can use the following tests to determine if the machine is able to connect to the servers.

 

1) Perform a disk boot.

2) When the machine seemingly stops performing additional tasks or  the same task is constantly displayed on the screen without proceeding to the boot menu. Hit ALT+F2

Here is an example of a stuck machine. 

 

 kid3.jpg

 

3) You will then be asked for a username. Please enter “kiduser” following this enter “kid11” as the password.

4) Now type ifconfig (NOT ipconfig)

Doing so will return a screen like this . Please ensure the machine has received a valid Ip address.

 

kid2.jpg

 

5) Now please try to ping your repository and Kservers  address by typing PING “address” 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.