Remote Installation Trouble Shooting

Top  Previous  Next

Principle of the installation:

1.The browser (Dr.Web Security Control Center Extension module) connects to the ADMIN$ resource at the remote station (\\<remote_station>\ADMIN$\Temp) and copies installer files (drwinst.exe, drwcsd.pub), specified in Dr.Web Security Control Center to the \\<remote_station>\ADMIN$\Temp folder.

2.The extension runs drwinst.exe file at the remote station with the switches according to Dr.Web Security Control Center settings.

Successful installation requires that at the station from which the installation will be performed:

1.The ADMIN$\Temp resource must be available at the remote station.

The availability can be checked in the following way:

In the address line of the Windows Explorer application, enter the following:

\\<remote_station>\ADMIN$\Temp

You will get the prompt for entering login and password for assess to this resource. Enter the account data, which have been specified on the installation page.

The ADMIN$\Temp resource can be unavailable for the following reasons:

a)account does not have administrative rights;

b)the station is powered off or firewall blocks assess to the 455 port;

c)limitations of remote assess to the ADMIN$\Temp resource at the Windows Vista and later OS, if the station is outside a domain;

d)the folder owner is absent or not enough privileges on the folder for the user or the group.

2.The drwinst.exe and drwcsd.pub files are available.

At Dr.Web Security Control Center, the external information (step and error code), which can help to diagnose the error reason, is displayed.

The list of  the most frequently errors

Step

Error Code

Reason

Validating user inputs of the remote stations (1)

No such host is known (11001).

DNS name to address conversion failed. No such DNS name or wrong name server settings.

Checking if NetBIOS on the remote station is available (2)

A socket operation failed because the destination host was down (10064).

445 port is not available at the remote station. Possible reasons:

station is shut down;

firewall blocks specified port;

the OS at the remote station is different from the Windows OS.

Connecting to an administrative resource ADMIN$ on the remote station (1001)

At this step, connection with the ADMIN$ administrative resource at the remote station is performed.

 

The system detected a possible attempt to compromise security. Please ensure that you can contact the server that authenticated you (1265).

Sharing and security model for local accounts is not configured.

Authorization server is not available (domain controller).

Logon failure: unknown user name or bad password (1326).

Unknown user name or bad password.

The filename, directory name, or volume label syntax is incorrect (123).

The ADMIN$ resource does not exist at the remote station.

Checking installer exit code (1009)

At this step, result of installation is checked.

 

Unknown error (2).

Ask for the technical support of the Doctor Web company.

Installation is not required on this computer (4).

The Agent is already installed or has been incorrectly deleted (in this case, use the drwebremover utility) at this station.

Protocol violation (6).

The drwinst.exe installer is not matched with the Server version. Make sure, that the installer is from the Server installation package.

Cannot initialize scripting engine (7).

System error. Ask for the technical support of the Doctor Web company.

Connection to server timed out (8).

Dr.Web Server is not available from the remote station.

System should be rebooted to finish previous deinstallation (9).

Restart the station to complete previously uninstallation.