Server NIC Missing From List Resources

I have a server deployed in AWS that's giving me some issues. All of my other AWS servers seems to be polling fine, but for some reason, this particular server keeps timing out on the application polling. While trying to troubleshoot, I discovered that the NIC for this server is not listed on the "list resources" page. I did refresh the resource list and got nothing. I also switched the polling method from WMI to Agent. Still nothing. However, the "asset inventory" tab on the node details does show the NIC and the details for it. Does anyone know how I can go about getting the NIC monitored so I can keep an eye on the potential latency issue?

Current deployment:

Find more posts tagged with

network adapter

nic

network interface

interface

server

resources

Accepted answers

All comments

Lewis-H

Windows can automatically detect and install the correct network adapters for you. It will also correct any corrupted registry entries on the network adapter.

To direct Windows to automatically detect and install network adapters for you, follow these steps:
Right-click My Computer, and then click Properties.
Click the Hardware tab, and then click Device Manager.
To see a list of installed network adapters, expand Network adapter(s). Click to locate the network adapter, and then click Uninstall.
Restart the computer, and then let the system automatically detect and install the network adapter drivers.
Check to see whether your networking icons appear. If this method worked for you, you are finished with this article. However, you might want to read the "Prevention tips" section to learn how you can avoid this problem in the future.

christopher.t.jones123

@klevans8907 this may be a problem with WMI on that server. Take a look at this article regarding it

https://support.solarwinds.com/SuccessCenter/s/article/Interfaces-are-not-displayed-in-List-Resources-of-a-WMI-node-with-SAM-installed?language=en_US

klevans8907

The server itself isn't having an issue showing the NIC, it's just missing from Solarwinds. Since this is our main DC, I would prefer to make that a last resort step if nothing else seems to work.

klevans8907

Hey @christopher.t.jones123 , so I did come across this yesterday and I tried it, but the test on the target kept giving an error when I tried to connect. I will send this to the admin for that server and see if he can make sense of what might be causing the error.

christopher.t.jones123

@klevans8907 one other thing you can check is if the polling engine (if you have more than one) its assigned to has SAM installed. If it doesn't have SAM you could move it to a different one and try listing resources again.

shuth

I'm fairly sure Lewis-H is finding random threads and copy/pasting the first Google result. He is a new member from yesterday and his posts are all dubious.

klevans8907

Ah, that makes sense. It seemed to miss the mark slightly.

klevans8907

Fortunately, our infrastructure is fairly small, so I only have the one polling engine lol. It does have SAM installed on it. It's just weird because this is the only server that's doing this which leads me to believe that it's something on the server causing the issue. It's just difficult to track it down since I can't monitor the NIC.

shuth

It's an odd one. I'd follow the instructions and run the Wbemtest app on the server with the WMI account. That will confirm if WMI can see the interfaces (Agent polling still uses WMI locally, WMI polling polls WMI remotely from the SolarWinds server).

If WMI can't see the interfaces - server issue.

If WMI can see the interfaces - SolarWinds issue.

That should at least help determine where the problem lies.

klevans8907

I tried that test yesterday and kept getting an error, so it wouldn't even complete the test. I sent that article over to the admin for that server so we can see what might be causing that error to go from there.