Building an Ubuntu Workstation for development and general use, one that can be accessed remotely with central authentication.  Most of the commands below will be ran as the root user, hence # sudo su – to root will be needed.  Let’s get going: ALIAS SETUP Personally, the following alias just makes it a tad easier […]

Quick configuration to proxy AD requests through another server. Set the following on the proxy server. Note the frontend server is on port 443 whereas the backend server is on port 389: # vi /etc/haproxy18/haproxy.cfg global log 127.0.0.1 local0 debug stats socket /var/run/haproxy.sock mode 0600 level admin # stats socket /var/lib/haproxy/stats maxconn 4000 user haproxy […]

There were extra spaces or space with a different font, in front of “” that got copied over from an editor.  Once replaced, everything worked fine: root@g73sw01:/etc# klist -kte klist: Improper format of Kerberos configuration file while initializing krb5 root@g73sw01:/etc# vi /etc/krb5.conf root@g73sw01:/etc# klist -kte Keytab name: FILE:/etc/krb5.keytab KVNO Timestamp Principal —- ——————- —————————————————— 6 […]

When joining a new client to the FreeIPA servers: # ipa-client-install –uninstall; ipa-client-install –force-join -p USER -w “SECRET” –fixed-primarver=idmipa01.nix.mds.xyz –server=idmipa02.nix.mds.xyz –domain=nix.mds.xyz –realm=NIX.MDS.XYZ -U the following  message is visible: Connection to https://idmipa01.nix.mds.xyz/ipa/json failed with [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failename mismatch, certificate is not valid for ‘idmipa01.nix.mds.xyz’. (_ssl.c:1007) Connection to https://idmipa02.nix.mds.xyz/ipa/json failed with [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify […]

Ping resolves internal DNS entries with external IP’s: C:\Windows\system32>ping atlas-c01 Pinging atlas-c01.nix.mds.xyz [3.64.163.50] with 32 bytes of data: Control-C ^C C:\Windows\system32>ping atlas-c01 Pinging atlas-c01.nix.mds.xyz [3.64.163.50] with 32 bytes of data: Control-C ^C C:\Windows\system32> Nslookup works great: C:\Windows\system32>nslookup atlas-c01.nix.mds.xyz Server: dns.mds.xyz Address: 192.168.0.224 Non-authoritative answer: Name: atlas-c01.nix.mds.xyz Address: 10.0.0.77 C:\Windows\system32> Even from a locally installed Ubuntu […]

Via the CLI: root@tom-G73Sw:~# cd /etc/netplan/ root@tom-G73Sw:/etc/netplan# cat 01-network-manager-all.yaml # Let NetworkManager manage all devices on this system network: version: 2 renderer: NetworkManager ethernets: enp5s0: dhcp4: no addresses: [192.168.0.15/24] gateway4: 192.168.0.1 nameservers: addresses: [192.168.0.224,192.168.0.46,192.168.0.51] root@tom-G73Sw:/etc/netplan# Then issue: netplan try so changes take effect.  Via UI, go to Activities then Settings, select Network or WiFi, based […]

BitDefender updates resulted in this message being printed: “we could not verify the certificate: reason = wrongHost” “we could not verify the certificate: reason = untrusted” And on further inspection, it is revealed the BitDefender is indeed the culprit via it’s Parental Controls: To fix this, I uninstalled BitDefender Parental Control in Windows, as it […]

Follow the following steps to add specific user and group access to a single ESXi host: Configure a single group, be it AD (remote) or Local. Add user to the above group. Login to the VCSA (vSphere Client). Select the ESXi host.  Click on the Permissions tab. Click on the + icon.  You will be […]

Getting a rather cryptic ESXi error message when trying to set a new IPv4 IP: Enable Management Network: Error Setting ip/ipv6 configuration failed: For example, when trying to set 10.3.0.12, this is what is seen: It doesn't really, really say what the real reason behind the error is.  Taking a dive into the network configuration […]

In case the below error is seen: C:\Users\tom>nslookup josh-vm01.nix.mds.xyz 10.5.0.1 Server:  UnKnown Address:  10.5.0.1 *** No internal type for both IPv4 and IPv6 Addresses (A+AAAA) records available for josh-vm01.nix.mds.xyz The fix for this is to enable Setup -> Networking -> Optional DNS Target then fill in the target DNS server, in this case 192.168.0.100 for our […]