NCPA connection issue
- snapon_admin
- Posts: 952
- Joined: Mon Jun 10, 2013 10:39 am
- Location: Kenosha, WI
- Contact:
Re: NCPA connection issue
Not a VPN, no. I don't believe it's going through our proxy. We do have one, but it should only be used when traversing the internet, which this doesn't need to do.
Re: NCPA connection issue
What is the Nagios XI and NCPA wizard version that you are currently using?
Enable debugging in the ncpa.cfg file by setting this line:
Save, exit and restart ncpa listener.
Run the following command and show the output:
Also, upload the ncpa_listener.log (and win32service_ncpalistener.log if you have one) to the forum.
Enable debugging in the ncpa.cfg file by setting this line:
Code: Select all
loglevel = debugRun the following command and show the output:
Code: Select all
curl -k 'https://<IP>:5693/testconnect/?token=<TOKEN>' -vBe sure to check out our Knowledgebase for helpful articles and solutions!
- snapon_admin
- Posts: 952
- Joined: Mon Jun 10, 2013 10:39 am
- Location: Kenosha, WI
- Contact:
Re: NCPA connection issue
XI is version 5.6.10, NCPA wizard is version 2.2.3.
We set logging to debug level, but nothing seems to be logging, the file has nothing in it.
Code: Select all
[root@lisl-ngos-02-pv ~]# curl -k 'https://<REDACTED>:5693/testconnect/?token=<REDACTED>' -v
* About to connect() to <REDACTED> port 5693 (#0)
* Trying <REDACTED>...
* Connection refused
* Failed connect to <REDACTED>:5693; Connection refused
* Closing connection 0
curl: (7) Failed connect to <REDACTED>:5693; Connection refused- Box293
- Too Basu
- Posts: 5126
- Joined: Sun Feb 07, 2010 10:55 pm
- Location: Deniliquin, Australia
- Contact:
Re: NCPA connection issue
lmiltchev wrote:What is the output of the command below from the Nagios XI server?Code: Select all
nmap <ip address> -p 5693
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
- snapon_admin
- Posts: 952
- Joined: Mon Jun 10, 2013 10:39 am
- Location: Kenosha, WI
- Contact:
Re: NCPA connection issue
[root@lisl-ngos-02-pv ~]# nmap <IP> -p 5693
Starting Nmap 6.47 ( http://nmap.org ) at 2020-03-10 13:31 CDT
Nmap scan report for <IP>
Host is up (0.00017s latency).
PORT STATE SERVICE
5693/tcp closed unknown
Nmap done: 1 IP address (1 host up) scanned in 0.13 seconds
Starting Nmap 6.47 ( http://nmap.org ) at 2020-03-10 13:31 CDT
Nmap scan report for <IP>
Host is up (0.00017s latency).
PORT STATE SERVICE
5693/tcp closed unknown
Nmap done: 1 IP address (1 host up) scanned in 0.13 seconds
- Box293
- Too Basu
- Posts: 5126
- Joined: Sun Feb 07, 2010 10:55 pm
- Location: Deniliquin, Australia
- Contact:
Re: NCPA connection issue
OK so it's clear from that output that tcp port 5693 to the destination device is closed.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
- snapon_admin
- Posts: 952
- Joined: Mon Jun 10, 2013 10:39 am
- Location: Kenosha, WI
- Contact:
Re: NCPA connection issue
Right, but how would I go about correcting that? As far as I can see we don't have that port blocked over the network as I can browse to the NCPA GUI for that PC in a browser.
Re: NCPA connection issue
Can you try installing the latest version of NCPA (2.2.1) to see if this is going to fix your issue?
If you are still having the same problem, post the ncpa.cfg file on the forum. Please hide/obfuscate sensitive info.
If you are still having the same problem, post the ncpa.cfg file on the forum. Please hide/obfuscate sensitive info.
Be sure to check out our Knowledgebase for helpful articles and solutions!