Windows
Q: When I run the PowerShell agent installer script, I get one of the following errors:
-
The underlying connection was closed: An unexpected error occurred on a receive.
-
The client and server cannot communicate, because they do not possess a common algorithm
A: It is most likely because host and the server has mismatched SSL/TLS protocols configured. One can check the SSL/TLS version using the following command:
[Net.ServicePointManager]::SecurityProtocol
To set the SSL/TLS to be matching with server one can use the following command (note, this is not a permanent change, only temporary with the current PowerShell session):
[Net.ServicePointManager]::SecurityProtocol = [System.Net.SecurityProtocolType]’Ssl3,Tls,Tls11,Tls12’
Q: When I run the MSI installer from the downloaded bundle, I get the following error:
This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package.
A: Make sure C:\Windows\Installer path exists. If running the MSI installer from the command line, make sure to not include the relative path when pointing to the msi file. Example of correct syntax:
msiexec /i “TetrationAgentInstaller.msi” /l*v “msi_install.log” /norestart
Q: I have observed that Windows Sensor software fails to upgrade if underlying NIC is Nutanix VirtIO Network Driver.
A: There is an incompatibility issue between Npcap 0.9990 and Nutanix VirtIO Network Driver version earlier than 1.1.3 and Receive Segment Coalescing is enabled.
The resolution for this is to upgrade Nutanix VirtIO Network Driver to version 1.1.3 or later.
Q: I have installed windows sensor. The sensor doesnt seem to register and the sensor_id file contains the following: uuid-invalid-platform
A: You may not have system32 in PATH variable for Windows. Check if system32 is in PATH, if not run the following:
set PATH=%PATH%;C:\Windows\System32\
Q: I am not receiving the network flows from Kubernetes Pods on Windows Nodes.
A: To verify if the required sessions are running to capture the flows from Kubernetes pods on Windows nodes, perform the following:
-
Run cmd.exe with administrative privileges.
-
Run the following command:
logman query -etsEnsure that the following sessions are running:
-
CSW_MonNet: Captures network flows
-
CSW_MonHCS: Monitors creation of pods
-
CSW_MonNat: Monitors NATed flows
-