Hello,
I'm trying to setup a tunnel between agent and the NetXMS-server. Unfortunately without success.
Both, server and agent, are latest version at the time of writing and are running on Window. Server's IP is 192.168.10.6, the agent is at .10.70
Server is running on Win Server 2016, I have tried agent side on Win7x64 (physical machine) and server 2019 (VWware virtual machine)
Here's what I did:
- created a key (rsa 2048) and a CSR (including SAN) on a linux machine using standard open-ssl
- created a server cert using the CSR (on our windows domain ca)
- copied the root cert, the server cert and the server key to the netxms server
- edited the server's .conf to add the file pathes for key, cert and ca
after starting the test agent's log reports:
*D* [tunnel ] Tunnel manager started
*D* [tunnel ] 192.168.10.6: Cannot open file "C:\Windows\system32\config\systemprofile\AppData\Local\nxagentd\certificates\897A0B2402C28AD5A07199D8CDD5A37FD445FF87.crt" (No such file or directory)
*D* [tunnel ] 192.168.10.6: Cannot open file "C:\Windows\system32\config\systemprofile\AppData\Local\nxagentd\certificates\0602060AA8C0000000000000000000000000.crt" (No such file or directory)
*D* [tunnel ] 192.168.10.6: Server certificate subject is /C=DE/ST=NW/.....
*D* [tunnel ] 192.168.10.6: Server certificate issuer is /DC=de/DC=.....
...
*I* [ ] Tunnel with 192.168.10.6 established
The two "cannot open file" lines should be ok as there are no certs yet. The server's certificate subject and issuer are ok.
Checking the tunnel using the management console I see the tunnel as unbound.
I think that everything is fine until here.
Now I tried to create a node and bind the tunnel using the management console.
A key and a cert are created and copied to the agent computer, the files appear in c:\windows\system32\config....
the agent's log:
*D* [tunnel ] 192.168.10.6: Resetting tunnel
*D* [tunnel ] 192.168.10.6: Certificate and private key loaded
*D* [tunnel ] 192.168.10.6: Server certificate subject is /C=DE/ST=NW/.....
*D* [tunnel ] 192.168.10.6: Server certificate issuer is /DC=de/DC=.....
...
*D* [tunnel ] 192.168.10.6: Receiver thread stopped (MSGRECV_COMM_FAILURE)
...
*W* [ ] Tunnel with 192.168.10.6 closed
...
*D* [tunnel ] 192.168.10.6: Cannot configure tunnel (request timeout)
The unbound tunnel disappears from the mangement console, but there's no bound one now.
The server's log reports:
*D* [ ] SocketListener/AgentTunnels: Incoming connection from 192.168.10.70
*D* [ ] SocketListener/AgentTunnels: Connection from 192.168.10.70 accepted
*D* [agent.tunnel ] SetupTunnel(192.168.10.70): TLS handshake failed (error:00000001:lib(0):func(0):reason(1))
Whatever I have tried - same results.
Anyone out here, who have an idea what I'm missing or doing wrong?
Thanks in advance for any help!
Regards
Detlev
I'm trying to setup a tunnel between agent and the NetXMS-server. Unfortunately without success.
Both, server and agent, are latest version at the time of writing and are running on Window. Server's IP is 192.168.10.6, the agent is at .10.70
Server is running on Win Server 2016, I have tried agent side on Win7x64 (physical machine) and server 2019 (VWware virtual machine)
Here's what I did:
- created a key (rsa 2048) and a CSR (including SAN) on a linux machine using standard open-ssl
- created a server cert using the CSR (on our windows domain ca)
- copied the root cert, the server cert and the server key to the netxms server
- edited the server's .conf to add the file pathes for key, cert and ca
after starting the test agent's log reports:
*D* [tunnel ] Tunnel manager started
*D* [tunnel ] 192.168.10.6: Cannot open file "C:\Windows\system32\config\systemprofile\AppData\Local\nxagentd\certificates\897A0B2402C28AD5A07199D8CDD5A37FD445FF87.crt" (No such file or directory)
*D* [tunnel ] 192.168.10.6: Cannot open file "C:\Windows\system32\config\systemprofile\AppData\Local\nxagentd\certificates\0602060AA8C0000000000000000000000000.crt" (No such file or directory)
*D* [tunnel ] 192.168.10.6: Server certificate subject is /C=DE/ST=NW/.....
*D* [tunnel ] 192.168.10.6: Server certificate issuer is /DC=de/DC=.....
...
*I* [ ] Tunnel with 192.168.10.6 established
The two "cannot open file" lines should be ok as there are no certs yet. The server's certificate subject and issuer are ok.
Checking the tunnel using the management console I see the tunnel as unbound.
I think that everything is fine until here.
Now I tried to create a node and bind the tunnel using the management console.
A key and a cert are created and copied to the agent computer, the files appear in c:\windows\system32\config....
the agent's log:
*D* [tunnel ] 192.168.10.6: Resetting tunnel
*D* [tunnel ] 192.168.10.6: Certificate and private key loaded
*D* [tunnel ] 192.168.10.6: Server certificate subject is /C=DE/ST=NW/.....
*D* [tunnel ] 192.168.10.6: Server certificate issuer is /DC=de/DC=.....
...
*D* [tunnel ] 192.168.10.6: Receiver thread stopped (MSGRECV_COMM_FAILURE)
...
*W* [ ] Tunnel with 192.168.10.6 closed
...
*D* [tunnel ] 192.168.10.6: Cannot configure tunnel (request timeout)
The unbound tunnel disappears from the mangement console, but there's no bound one now.
The server's log reports:
*D* [ ] SocketListener/AgentTunnels: Incoming connection from 192.168.10.70
*D* [ ] SocketListener/AgentTunnels: Connection from 192.168.10.70 accepted
*D* [agent.tunnel ] SetupTunnel(192.168.10.70): TLS handshake failed (error:00000001:lib(0):func(0):reason(1))
Whatever I have tried - same results.
Anyone out here, who have an idea what I'm missing or doing wrong?
Thanks in advance for any help!
Regards
Detlev
