This post shows how to query and set the time zone in the command line on RHEL 8, CentOS 8 and Fedora 30. The command line tool timedatectl use to check and modify time zone setting.
Run the query using timedatectl without additional arguments:
1
2
3
4
5
6
7
8
9
$timedatectl
Local time:Wed2021-02-1717:04:29GMT
Universal time:Wed2021-02-1717:04:29UTC
RTC time:Wed2021-02-1716:57:58
Time zone:Europe/London(GMT,+0000)
System clock synchronized:yes
NTP service:active
RTC inlocal TZ:no
Now set the time zone to another zone:
1
2
$sudo timedatectl set-timezone Europe/Zurich
To query the changed time zone setting:
1
2
3
4
5
6
7
8
9
$timedatectl
Local time:Wed2021-02-1718:05:58GMT
Universal time:Wed2021-02-1717:05:58UTC
RTC time:Wed2021-02-1716:59:27
Time zone:Europe/Zurich(CET,+0100)
System clock synchronized:yes
NTP service:active
RTC inlocal TZ:no
The available time zones showing with the following command:
1
2
$timedatectl list-timezones
Since there are many time zones, the query becomes very long; the query can be narrowed down with grep:
Setting Up and customize OpenVPN on Windows, macOS and Linux
VPN (Virtual Private Network) is becoming more and more widely used. OpenVPN is a free application for building a virtual private network over an encrypted TLS connection. The increasingly popular OpenVPN client enables VPN connections to access its data from anywhere, for example, when working in the home office, or with a private cloud. This article shows the client deployment and use of OpenVPN. OpenVPN is available for free for many operating systems, in addition to Windows there is a client for macOS, for iOS, Linux and Android devices.
OpenVPN for Windows can be downloaded from the community website here, on Windows 10 with double-clicking OpenVPN-2.5.0-I601-amd64.msi start the setup.
Choose Customize to goes through the setup wizard, because here only the client components are needed, we choose the selection.
Continuous Installing OpenVPN..
OpenVPN Installing Completed.
Start OpenVPN
A glance at the taskbar shows now the OpenVPN icon
OVPN configuration import at the client
The OpenVPN Access Server is available for Windows, Linux and FreeBSD, and there are an increasing number of devices that can be used as OpenVPN servers, such as pfSense and OPNsense or OpenWrt, from commercial manufacturer like Sophos formerly Astaro or Synology NAS and many more.
The file with the configuration for the client, such as openvpn.zip, which was previously exported on the VPN server or router need to unpacked, the files ca.crt, README.txt and VPNConfig.ovpn are usually extracted.
The configuration file here in this example VPNConfig.ovpn may have a different file name. Hint! if you change the file name to i.e. office-davos.ovpn, then this name appears in the context menu at connection.
The file VPNConfig.ovpn usually has to be open in an editor, for this I use Notepad and change YOUR_SERVER_IP to the public IP address of the VPN gateway, or the firewall on which is the NAT mapping to the VPN termination device.
After saving VPNConfig.ovpn, the configuration is imported.
Right-clicking above the icon in the Systemtry opens the context menu from which you choose to import file.
Figure: Importing OpenVPN Connection
Tip! If you rename the file VPNConfig.ovpn eg. Home-Office.ovpn, the corresponding name appears as the target in the Connect context menu.
Connecting from the context menu prompts to enter the user and password, which is the user on the VPN Router or with use LDAP authentication the user on the server.
Figure: OpenVPN Connection
If the connection is successful, the OpenVPN icon will appear green.
OpenVPN client setup on macOS
OpenVPN Connect v3 Client for macOS is a complete installation program for macOS, after the installation the ovpn file can be imported for an OpenVPN connection to an access server. If the downloaded OpenVPN Connect v3 for macOS is installed on a Mac on which OpenVPN Connect v3 is already installed and configured, it will be updated to the new version with all settings retained.
OpenVPN Installer on macOS Catalina
OVPN file import on macOS catalina.
Deploy OpenVPN client on Linux
With the standard installation, OpenVPN is usually already installed together with the network management tools, in this case you can go directly to Import OVPN configuration file below. The easiest way to deploy the OpenVPN client using the package management system is to run the following commands as root on a Red Hat based Linux distribution such as Fedora or CentOS:
Fedora Terminal
1
2
3
4
5
[sam@fedora~]$sudo su-
[sudo]password forsam
[root@fedora~]# dnf install openvpn
Install the OpenVPN on Debian and Ubuntu based distributions as follows:
Debian Terminal
1
2
3
4
5
[sam@debian~]$sudo su-
[sudo]password forsam
[root@debian~]# apt-get install openvpn
Running the OpenVPN client with the downloaded configuration file, using the -config argument to pass the configuration file:
1
2
openvpn-config VPNConfig.ovpn
The configuration file here in this example VPNConfig.ovpn may have a different file name. Hint! if you change the file name to i.e. office-davos.ovpn, then this name appears in the context menu at connection
The connection can also be established via a GUI client, to install the OpenVPN GUI from the shell:
Now you can call the Connection Manager by clicking on the network icon – VPN Connections – Configuring VPN.
Illustration: OpenVPN GUI Ubuntu
By clicking on Add – Import Saved VPN Configuration – Create a new VPN connection. The next step is to import the previously downloaded VPNConfig.ovpn file. The connection can now be started from the taskbar.
For Linux Mint with Cinnamon desktop, you click on the network icon in the taskbar and go to network settings.
Click + to create a new network connection.
Import saved VPN configuration from the VPNConfig.ovpn file. After entering the user and password, the saved connection can be started in the taskbar.
Import the OVPN file via the Network Manager of Linux Mint and Cinnamon Desktop.
OVPN file import by Network Manager at Linux Mint Cinnamon desktop.
Connect to Printer: Windows cannot connect to the printer. Operation failed with error 0x00004005
If the error occurs when adding a network printer; Printer connection cannot be established, then the printer driver must be added directly without using the printer setup wizard.
Click on the Start button, and choose settings.
then select Devices and Printers & scanners.
In the Printers window, click on the right to Print server properties, see below Related settings.
choose the tap Drivers.
Alternatively open the old windows 7 control panel. Right click on the Start button und choose Run, or press Win + R.
Go through the steps 1 to 3, but first select any printer so that the option Print server properties becomes active.
Now drivers for the appropriate printer can be added with click to the Add button, in the wizard with choose the path to the previously downloaded and decompressed driver package, it must point to the directory in which the printer description INF file is located, or select your printer from the device list for which Microsoft provides certified printer drivers.
How to Adding Network Printer
When using Windows printer shares on a server, errors may occur when adding a network printer on client site, because the printer setup wizard are unable to find the printer driver. The wizard looks for a driver in the InfPath registry key, in which the directory path to the printer driver should be saved.
Now that the path to the printer driver is no longer valid, the path must be find in the registry of the server, here in this example it is the printer Sharp MX-C401 PCL6, which includes the path to the printer driver with the INF file in the InfPath registry key, the path shown as follows:
The path is inserted as a value in the InfPath key which is presumably empty, require admin rights to change, run regedit.exe as administrator or temporarily grant admin rights to the user.
If there is another printer on the client with the same driver, InfPath can copy this value and insert it by double-clicking InfPath on the printer with an invalid value or where the value is empty.
Adding Network Printer manually
Now open the windows administrative share print$ to the print server on the client, where the printer drivers of the server are located.
i.e. \\SERVER02\print$
Under the print share the printer drivers of the installed printers are located on the print server. In our example \\SERVER02\x64\PCC printer drivers are for the Windows 64 Bit system architecture.
Find the appropriate CAB archive file which has the same driver that is file name as the file in RegistryKey InfPath, so here sn0emdeu.inf.
Unzip the compressed CAB archive file that matches the printer from the print- share with 7-Zip, and copy the files to the path taken from InfPath.
Connecting and adding network printers is now possible as usual.
Another simple solution is to add a new printer where by selecting LPT1 as the port, even if LPT1 does not exist, it is re-entered correctly when the path is installed in the InfPath registry key, so that the printer connection to network printers works again, the previously installed printer on LPT1 can be deleted with Device Removal.
UNBLOG verwendet Cookies, um Dein Online-Erlebnis zu verbessern. Mit "ACCEPT" gibst Du Deine Zustimmung zur Nutzung dieser Website und unseren Datenschutzbestimmungen, oder wähle Cookie settings.
Diese Website verwendet Cookies, um Ihre Erfahrung zu verbessern, während Sie durch die Website navigieren. Von diesen werden die Cookies, die nach Bedarf kategorisiert werden, in Ihrem Browser gespeichert, da sie für das Funktionieren der grundlegenden Funktionen der Website wesentlich sind. Wir verwenden auch Cookies von Drittanbietern, mit denen wir analysieren und verstehen können, wie Sie diese Website nutzen. Diese Cookies werden nur mit Ihrer Zustimmung in Ihrem Browser gespeichert. Sie haben auch die Möglichkeit, diese Cookies zu deaktivieren. Das Deaktivieren einiger dieser Cookies kann sich jedoch auf Ihre Browser-Erfahrung auswirken.
Notwendige Cookies sind unbedingt erforderlich, damit die Website ordnungsgemäß funktioniert. Diese Kategorie enthält nur Cookies, die grundlegende Funktionen und Sicherheitsmerkmale der Website gewährleisten. Diese Cookies speichern keine persönlichen Informationen.
Alle Cookies, die für die Funktion der Website möglicherweise nicht besonders erforderlich sind und speziell zur Erfassung personenbezogener Daten des Benutzers über Analysen, Anzeigen und andere eingebettete Inhalte verwendet werden, werden als nicht erforderliche Cookies bezeichnet. Es ist obligatorisch, die Zustimmung des Benutzers einzuholen, bevor diese Cookies auf Ihrer Website ausgeführt werden.
