Sorry for spamming. I found out that something else listen on port 8405. It is possible to change port in nsc.ini
On Tue, Aug 25, 2009 at 2:49 PM, Arlen Drina<arly...@gmail.com> wrote: > Hi all, > > I have to set up nagios monitorig in maze of firewalls, and due to that > I am facing some strange requirements :) > For windows monitoring I am using NSClient++ and in NSC.ini is specified port > > port=12489 or port=5666 > > in section modules I have uncommented, > > FileLogger.dll > CheckSystem.dll > CheckDisk.dll > NSClientListener.dll > SysTray.dll > CheckEventLog.dll > CheckHelpers.dll > > I realized in NSClientListener.dll is uncommented, it works no mater > does port 12489 or > port 5666 is specfied in port line > port= > it alway bind it to port 12489 and I understant it. > > When I try to change port to let say 8344 and when restart NSCservice > it does not start and I am getting error > > 2009-08-25 14:38:32: error:include\Socket.h:683: bind failed: 10048: > Only one usage of each socket > address (protocol/network address/port) is normally permitted. > 2009-08-25 14:38:32: error:include\Socket.h:714: Socket did not start > properly, we will now do nothing... > > > my question is possible to change NSClient port in NSC.ini in some > other value different that 12489 or 5666 and avoid > above error. > I think it is easier for me to change port than to change port on > firewall for which I am not responsible. > > Thank you in advance for sharing your experiences > > Arlen > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
