172.16.98.114
What is the issue here ?
CRITICAL - Socket timeout after 20 seconds
-
lafargeuser
- Posts: 341
- Joined: Thu Sep 27, 2012 12:23 am
-
sreinhardt
- -fno-stack-protector
- Posts: 4366
- Joined: Mon Nov 19, 2012 12:10 pm
Re: CRITICAL - Socket timeout after 20 seconds
So to get this straight, the windows machine you are having issues with is 172.16.98.114, but you scanned 172.17.85.69? I need you to scan the windows machine with issues, from the nagios machine.
Code: Select all
nmap -p 5666,12489 172.16.98.114Nagios-Plugins maintainer exclusively, unless you have other C language bugs with open-source nagios projects, then I am happy to help! Please pm or use other communication to alert me to issues as I no longer track the forum.
-
lafargeuser
- Posts: 341
- Joined: Thu Sep 27, 2012 12:23 am
Re: CRITICAL - Socket timeout after 20 seconds
[root@BGLRLXNAGIOS01 ~]# nmap -p 5666,12489 172.16.98.114
Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2014-01-31 18:34 IST
Interesting ports on bglrmsbsmdshb.bglrgoc.com (172.16.98.114):
PORT STATE SERVICE
5666/tcp closed unknown
12489/tcp filtered unknown
MAC Address: 00:50:56:AB:00:76 (VMWare)
Nmap finished: 1 IP address (1 host up) scanned in 1.484 seconds
Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2014-01-31 18:34 IST
Interesting ports on bglrmsbsmdshb.bglrgoc.com (172.16.98.114):
PORT STATE SERVICE
5666/tcp closed unknown
12489/tcp filtered unknown
MAC Address: 00:50:56:AB:00:76 (VMWare)
Nmap finished: 1 IP address (1 host up) scanned in 1.484 seconds
Re: CRITICAL - Socket timeout after 20 seconds
port 12489 is filtered. This is most likely due to a firewall.
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.