Dlltool is a usefull tool but need money 10$ only for 7 days. you can use it fix the netsh problem for free.
Changing TCP/IP settings using the GUI property is very easy and simple. But what about if you want to have more fun doing it, and change the IP and DNS properties using the windows command prompt? If you are a Linux guru or a batch scripting wizard this should not be complicated, if you are new to the command prompt, well, today is a good day to start.
We will change the IP address and DNS servers using the built-in utility in Windows called “Netsh” is a nifty utility to change system networking settings, locally or remotely. To run Netsh click on start then RUN and type CMD press ENTER.
When the command prompt comes up type Netsh, now you should be ready to execute commands. Simple huh. Just to warm up type “interface ip show config” that will show up the TCP/IP network settings.
Now, how you change the IP address and Default Gateway settings? To change the Local Area Connection TCP/IP settings type the following command:
interface ip set address name=”Local Area Connection” static 192.168.10.42 255.255.255.0 192.168.1.1
As you can see, when you use Netsh you need to specify what network properties you need to change, in the example above, we changed the network properties for “Local Area Connection” then we setup a static IP address, Subnet Mask and at the end the default gateway.
Changing the DNS IP address is almost identical as the procedure above, type the following command on the Netsh prompt:
interface ip set dns “Local Area Connection” static 192.168.1.1
To Setup WINS, type the following command:
interface ip set wins “Local Area Connection” static 192.168.1.1
To set the network properties to obtain the IP address from a DHCP server, type the following command:
interface ip set address “Local Area Connection” dhcp
To set DNS to obtain IP address automatically type the following:
netsh interface ip set dns “Local Area Connection” dhcp
There you have it, a useful tool to help you on your network configuration.
The Cipher Suite
Forward Secrecy ensures the integrity of a session key in the event that a long-term key is compromised. PFS accomplishes this by enforcing the derivation of a new key for each and every session.
This means that when the private key gets compromised it cannot be used to decrypt recorded SSL traffic.
The cipher suites that provide Perfect Forward Secrecy are those that use an ephemeral form of the Diffie-Hellman key exchange. Their disadvantage is their overhead, which can be improved by using the elliptic curve variants.
The following two ciphersuites are recommended by me, and the latter by the Mozilla Foundation.
The recommended cipher suite:
The recommended cipher suite for backwards compatibility (IE6/WinXP):
If your version of OpenSSL is old, unavailable ciphers will be discarded automatically. Always use the full ciphersuite above and let OpenSSL pick the ones it supports.
The ordering of a ciphersuite is very important because it decides which algorithms are going to be selected in priority. The recommendation above prioritizes algorithms that provide perfect forward secrecy.
Older versions of OpenSSL may not return the full list of algorithms. AES-GCM and some ECDHE are fairly recent, and not present on most versions of OpenSSL shipped with Ubuntu or RHEL.
Learn how to set the correct timezone and synchronize time with NTP servers on your CentOS box.
Setting the timezone
Setting the timezone on CentOS or Redhat Enterprise Linux (RHEL) is easy.
Login as root either locally or remotely via SSH.
See what the current timezone is:
You should see output like this:
Wed Jun 1 10:33:29 PDT 2017
To change the timezone first look at what timezones are available by running the following command on the command line interface:
You should see a listing like this:
[firstname.lastname@example.org ~]# ls /usr/share/zoneinfo
Africa Australia Cuba Etc GMT0 Iceland Japan MST Poland right Universal Zulu
America Brazil EET Europe GMT-0 Indian Kwajalein MST7MDT Portugal ROC US
Antarctica Canada Egypt Factory GMT+0 Iran Libya Navajo posix ROK UTC
Arctic CET Eire GB Greenwich iso3166.tab MET NZ posixrules Singapore WET
Asia Chile EST GB-Eire Hongkong Israel Mexico NZ-CHAT PRC Turkey W-SU
Atlantic CST6CDT EST5EDT GMT HST Jamaica Mideast Pacific PST8PDT UCT zone.tab
Then simply delete the current timezone:
And replace it with a symbolic link to the new timezone from /usr/share/zoneinfo. For example if your chosen zone is Pacific time:
ln –s /usr/share/zoneinfo/PST8PDT /etc/localtime
Synchronizing time with NTP server
Network Time Protocol (NTP) is a standard way of synchronizing computer clocks across a network. Using NTP you can keep your server’s clock synchronized with super accurate atomic clocks located around the world. Computer clocks tend to “drift” so regularly synchronizing them with NTP servers helps keep them accurate.
The first step is to make sure you have the ntp program installed. Do a:
If its not available type:
yum install ntp
Once ntp is installed synchronize your computer clock with:
To use this pool zone, add the following to your ntp.conf file:
You are not limited to the above server. There are numerous NTP servers around the world. You can find a complete list at ntp.org.
Also keep in mind that ntp only affects the system time. The hardware clock on your server will not reflect that. So you want to set it as well so that the correct time is maintained after reboot:
To keep your server clock automatically synchronized you can run the ntpd daemon which is installed as part of the ntp package.
Edit the /etc/ntp.conf file to comment out the following lines:
#server 127.127.1.0 # local clock
#fudge 127.127.1.0 stratum 10
The above two lines can sometimes prevent ntpd from properly synchronizing your clock. They are already commented out by default on CentOS/RHEL 6. But on 5.x you have to comment them out manually.
Finally type the following two commands to start the daemon and make it run automatically at boot up:
You can also install the following optional GUI packages.
# yum -y groupinstall “Graphical Administration Tools”
# yum -y groupinstall “Internet Browser”
# yum -y groupinstall “General Purpose Desktop”
# yum -y groupinstall “Office Suite and Productivity”
# yum -y groupinstall “Graphics Creation Tools”
Finally, if you wanted to add the K Desktop Environment (KDE).
# yum -y groupinstall kde-desktop
When using yum groupinstall, the groupinstall option only installs default and mandatory packages from the group. There are times when you also want to include optional packages within a group. I have not figured out (yet) how to control which package types to install (group package “policy”) from the command-line using yum. The only method I know of to also include optional packages is to edit the /etc/yum.conf file and add the following to the [main] section:
group_package_types=default mandatory optional
The reason I mention this is because I wanted to install “Terminal emulator for the X Window System” (xterm) which is under the group “Legacy X Window System compatibility”. xterm happens to be an optional package and did not get installed until I added group_package_types=default mandatory optional to /etc/yum.conf.
# yum -y groupinstall “Legacy X Window System compatibility”
I did find a plug-in for yum that allows users to specify which package types within a package group should be installed when using yum groupinstall.
Since the server was previously running on CLI mode, we need to change the initialization process for the machine to boot up in GUI mode.
Open /etc/inittab using a text editor and change following line:
After making the change, reboot the machine.
# init 6
Note that you can switch from GUI to CLI mode manually by using following method:
GUI to CLI: Ctrl + Alt + F6
CLI to GUI: Ctrl + Alt + F1
Installing Additional Applications
After logging in to the GNOME Desktop, you can now go to System > Administration > Add/Remove Software to manage application in CentOS.
After installing gnome packages .Issue the below command to install VNC package along with dependencies
yum -y install tigervnc-server pixman pixman-devel libXfont
Create user name and password.
[email@example.com ~]# adduser user1
[firstname.lastname@example.org ~]# adduser user2
[email@example.com ~]# passwd user1
[firstname.lastname@example.org ~]# passwd user2
Create VNC passwords for the Users created.
[email@example.com ~]# su – user1
[firstname.lastname@example.org ~]$ vncpasswd
[email@example.com ~]$ logout
[firstname.lastname@example.org ~]# su – user2
[email@example.com ~]$ vncpasswd
[firstname.lastname@example.org ~]$ logout
Now open /etc/sysconfig/vncservers file and add the following lines at the end of the file( Edit as per your usernames ).
Here we have configured session 1 with 640×480 resolution for the user “user1” and session 2 with 800×600 resolution for the user “user2”.
Start vnc service
[email@example.com ~]# service vncserver start
and issue this command to start vnc service automatically during startup.
[firstname.lastname@example.org ~]# chkconfig –levels 235 vncsever on
Now in remote machine, start vncviewer type the IP and session as below to view their respective sessions.
192.168.1.10:1 for user1
192.168.1.10:2 for user2
» Check the iptables in the server, if you are not able to connect the sessions.
Issue the below command to stop iptables service.
[email@example.com ~]# service iptables stop
» you might receive the below error while starting the vnc service.
/usr/bin/Xvnc: symbol lookup error: /usr/bin/Xvnc: undefined symbol: pixman_composite_trapezoids
/usr/bin/Xvnc: symbol lookup error: /usr/bin/Xvnc: undefined symbol: pixman_composite_trapezoids
Issue the below command to install pixman,pixman-devel and libXfont packages.
[firstname.lastname@example.org ~]# yum -y pixman pixman-devel libXfont
This command will update everything .
[email@example.com ~]# yum update
If your site can be accessed over HTTPS, then you may need to update older versions of AdSense ad code to avoid the AdSense script being blocked as mixed content. If your AdSense ad code has a script starting with “http://”, then you should update it to “https://” instead:
The HTTPS version of the ad code is also safe for HTTP pages; you don’t need to serve two different versions.
The SSL-compatible ad code also works on HTTP sites and doesn’t change how ads are served on these sites.
yum install php-pear php-devel
yum install ImageMagick ImageMagick-devel
yum install pcre-devel
tar -xvf imagick-3.2.0RC1.tgz
Remember to turn on the extension in the php configuration file.