Thứ Bảy, 26 tháng 7, 2014

Đổi IP từ xa

Nguồn : http://fakatosh.blogspot.com/2009/10/how-to-change-ip-settings-remotely.html


In order to edit or change the IP settings of a remote client in your enterprise, you would need some tools and a set of command line knowledge. To get there in no time, simply follow these steps:


* Download the PsExec tool. This tool helps you run software on remote machines over command line.


*Unpack the zip file under your c:\ . Open up a command line, navigate thru the pstools to find PsExec.exe .


* The command goes like this;


c:\psexec \\remotemachineip -u username -p password cmd.exe



\\remotemachineip : Here you can enter the IP of the remote client OR the computer name of the client. i recommend going for the IP to avoid DNS problems.

-u : user name that has administrative rights on the remote client. In an enterprise, please DO include the domain and the user name as domain\username.

Example : contoso\administrator01 .

-p : password of the user name that has administrative rights on the client machine.

cmd.exe : this is the tool we will need to edit ip settings.

* After entering the command , you will see some lines passing through and finally you will get c:\windows \system32 . This means that you have successfully logged in the client machine and its cmd.

* type netsh and press enter. Netsh is a tool that allows you to mess with your network settings.

*type int and press enter. int stands for Interface.

* Under netsh interface , enter this command that will change the IP settings.


ip set address local static theipnumber thesubnetmask thegateway metric




theipnumber : this is the desired ip address.

thesubnetmask : this is the subnet mask suitable for the desired IP

thegateway : gateway IP that will let the client machine to Internet

metric : the metric of the gateway that will prioritise the entries of different gateways respectfully.

Thứ Tư, 9 tháng 7, 2014

Why the Administration console cannot connect to the Administration server 8.0

The process of connecting to the Administration server includes several stages:
  • Definition of Server address and connection settings
  • Verification of the Administration server authenticity
  • Verification of user account permissions
In case an error occurs at the moment of connecting to the Administration server, the troubleshooting effort should begin with the first stage. If the first stage completes successfully, you should carry on to the second one.

Definition of Server address and connection settings

This stage establishes the connection with the Administration server.


Possible errors at this stage:
  • Incorrect DNS name, NETBIOS name or IP address in the Server Address field. Incorrect DNS service configuration in the network.
  • Kaspersky Lab Administration Server service is not started (the server is down, service start error);
  • SQL Server service (database unit name) is not started (the server is down, service start error);
  • TCP 14000 port closed on the Administration server when connecting with the Use SSL connection option disabled;
  • TCP 13000 port closed on the Administration server when connecting with the Use SSL connection option enabled;
  • The Administration server is using non-standard ports for Console connection. In this case, you should enter <server_name:port> in the Server Address field;
  • The Administration server connects via a proxy server, yet there are no authorization credentials specified. Click the button Advanced to specify the required data.

Verification of the Administration server authenticity
If the Use SSL connection option has been enabled on the previous stage, you should then select the Administration server authentication settings used by the Console. The authentication check is based on the certificate that has been created during the Administration server installation. You should select Connect to Administration server at the first connection attempt and receive that certificat

 

If this window appears again, you should indicate the certificate path via the button Select. The klserver.cer certificate file can be found in the Cert subfolder inside the Kaspersky Administration Kit installation folder.

Verification of user account permissions

Once the Administration server has been authenticated, user account permissions to access the Administration server database are verified. If the user account running the Administration console lacks the permissions required for connecting to the Administration server, a User registration box will open.



By default, the following accounts have the permissions for connecting to the Administration server:
  • Domain Administrators group, if the Administration server is installed in a domain (full access);
  • Local Administrators group on the host with the Administration server installed (full access);
  • Domain group KLAdmins, if the Administration server is installed on a domain controller (full access);
  • Domain group KLOperators, if the Administration server is installed on a domain controller (reading);
  • Local group KLAdmins, if the Administration server is installed on an ordinary host in a domain/workgroup (full access);
  • Local group KLOperators, if the Administration server is installed on an ordinary host in a domain/workgroup (reading);
  • Users and groups listed on the Security tab in the Administration server properties (access as configured).