pederl asked a question.
Hi, Im having problem with agent at a customer environment that cant do a handshake with Inventory server. If you browse to server it answers. I think ithis is about rights but would appreciate if anyone has another suggestion we can try. BR PEder
Can you post the content of the log file from the failing client?
Also, you could check the settings according to this chart that Adam just posted:
https://community.flexera.com/s/question/0D51r00008qw0i8CAA/map-of-snow-infrastructure-and-ports
Are all clients failing?
Also, can you post the (filtered/obfuscated as you need) content of the config file on this client?
There are a few settings there that could prevent the client from reporting properly: The address, the site name, etc. ...
Its not all of them. Its a few servers. Reporting and not reporting servers are on same network segment. Ports are checked and are open and the same with FW.
BR Peder
This is from agent loggfile.
2020-08-24T11:24:12+02:00; ERROR; snowagent; message_loop\messageloop.cpp; Client::MessageLoop::Handshake; Handshake failed. Cannot connect to server. No endpoint can establish a connection to the server.
BR Peder
Hi Peder,
Please let me know the Operating System name where you getting the handshake issue.
Thanks,
Kishan Pant
this might help - https://community.flexera.com/s/article/AbletobrowsetoSItestpagebutcannotsendthesnowpackErrorinlogsstatehandshakefailed-v2
it could also be an issue with TLS versions
Hi Peder,
As Adam mentioned it could be TLS version issues and for the same below are the steps to handle the same:
I suspect this might be due to TLS1.2. TLS 1.2 is not enabled for WinHTTP by default and depends upon the policy enabled in environment.
Please follow the steps below and try –
64 bit path - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp
32 bit path - HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp
Once this has been done, please try to scan and send the data using agent command line.
NOTE: I observed the above issue in the Windows 7 machines and after following the above steps issue resolved.
I hope above helpful for you as well if the issue is same.
Kind regards,
Kishan Pant