Nagios Auto Discovery cannot detect Windows 2008 server

[tin.gaur]

We did an Auto Discovery of our server subnet, but at the end we found that Windows 2008 server Operating system is detected as Windows 7 and some of the Windows 2003 server + SP2 is detected as Windows XP operating system.
Is it normal ?

Its not easy to cross verify every scan result with individual server.

[yancy]

Nagios uses NMAP under the hood which is not always 100% accurate when OS linage is so similar. The important details when monitoring is typically that we know if it's Window vs Linux, etc. Any reason you're looking to determine if it's Window08 vs Windows 7?

Thanks,

-Yancy

[tin.gaur]

Hello Yancy,
Thanks for your answer, I was trying to scan what runs in my environment and some servers were not identified properly.
Infact, All the servers running Windows 2008 server are identified as Windows workstation & Windows 7 Operating system. Additionally, what surprises me is that One of the Windows 2003 server + SP2 is identified properly where as another server is identified as Windows Workstation & windows XP Operating system.

I was wondering if there is any configuration mistake or error which is causing this abnormality.

Nitin

[yancy]

tin.gaur,

We can do some testing to make sure it's not the wizard having the issue. However, NMAP can only "guess" at what the architecture is based on how the TCP/IP packets are constructed.

Is there anything particular you're trying to accomplish that you need such granular results? Maybe I can help with a better suggestion than use the Auto Discovery Wizard.

Thanks,

-Yancy

[tin.gaur]

Hello Yancy,

The only propose of the scan was to identify what systems & services are running on network.
Auto discovery wizard did the job to some extent. Please let me know if there is any better way to scan the network for Windows servers OS & Services.

My only worry is to ensure, that wizard does not have any issues or is there any update missing which is causing this improper detection of OS.
if so, please let me know. Otherwise, in worst case, i will identify to remaining machines manually.

Thank you in advance for your answer.

Regards
Nitin

[yancy]

tin.gaur,

Here is the results of running a NMAP scan (which is used by autdiscover) against a Windows 2003 machine:

Code: Select all

OS details: Microsoft Windows XP SP2 or Server 2003 SP1 or SP2

As you can see, the NMAP scan is ambigous because the TCP/IP stack is so similar.

A solution I had in mind was to augement the autodiscovery wizard to also use WMI once a windows host was identified. This would give almost any detail about the Windows box, but would require the WMI service to be running and a valid Windows username and password to be supplied.

Thoughts?

-Yancy

[tin.gaur]

Thanks Yancy. I will try.
Nitin

[yancy]

tin.gaur,

Let us know if you have any other suggestions or comments.

-Yancy