Windows agent not correctly detecting network interfaces

[Daniel Rich]

On several of our laptops that have both a wired and a wireless interface, we have noticed that both the 2.0 and 2.1RC1 agents are not correctly detecting the interfaces. This all started when one of our help desk engineers noticed that OCS was reporting his primary interface down with no IP when it was up, and his wireless interface up when it was down -- even after forcing an update. We have also seen the agent fail to detect an interface. These are all HP EliteBooks running Windows 7 Professional.

For example, here is what we see on one system -- this is what we would expect for a wired connection:
Description Type Speed MAC address Status IP address Netmask Gateway Network number DHCP IP
Bluetooth Personal Area Network Ethernet 10 Mb/s C0:18:85:B3:1B:15 Down 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0
Intel(R) 82579LM Gigabit Network Connection Ethernet 1 Gb/s 28:92:4A:2A:60:50 Up 192.168.92.213 255.255.254.0 192.168.92.1 192.168.92.0 192.168.4.254
Intel(R) Centrino(R) Advanced-N 6205 Other (see MIB) 300 Mb/s 60:67:20:71:3C:B8 Down 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0

Here is an identically configured machine where we disabled and then re-enabled the wireless interface. Notice that the Advanced-N interface is missing:
Description Type Speed MAC address Status IP address Netmask Gateway Network number DHCP IP
Bluetooth Device (Personal Area Network) Ethernet 0 b/s E0:06:E6:B5:A7:0E Down 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0
Intel(R) 82579LM Gigabit Network Connection Ethernet 100 Mb/s 28:92:4A:2A:61:E7 Up 10.67.4.159 255.255.252.0 10.67.4.1 10.67.4.0 10.110.48.254

However, this is an example of the ones where that started the whole thing. Notice that it is reporting the Gig network connection down even though it has an IP and the Advanced-N up even though it doesn't. If we look at ipconfig /all on this machine it shows the correct data -- Ethernet up, Advanced-N down.
Description Type Speed MAC address Status IP address Netmask Gateway Network number DHCP IP
Bluetooth Personal Area Network Ethernet 10 Mb/s C0:18:85:B3:13:5F Down 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0
Intel(R) 82579LM Gigabit Network Connection Ethernet 1 Gb/s 28:92:4A:2A:60:4F Down 192.168.76.203 255.255.254.0 192.168.76.1 192.168.76.0 192.168.4.254
Intel(R) Centrino(R) Advanced-N 6205 Other (see MIB) 130 Mb/s 60:67:20:71:37:AC Up 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 192.168.0.1

[Didier Liroulet (dliroulet)]

Hi,

Could you try with 2.1rc1 agent to launch OCS systray applet and display network adapter properties ?

Do you see same effects ?

It will help us to diagnose if problem is on server side or client side.

Thanks

Cheers

[Daniel Rich (drich-u)]

I am not going to be back in the office until the 6th, but I'll give it a try as soon as I can after that.

[Didier Liroulet (dliroulet)]

Daniel,

Any news on this ?

[Daniel Rich (drich-u)]

Sorry, I keep meaning to get back to this and forgetting.

I had a couple of interesting things happen when I tried this. The first is that it crashed the agent, I had to manually restart it and the systray. I keep getting the "Failed sending control message to OCS Inventory Service... Error code 1053 = The service did not respond to the start or control request in a timely fashion." when I try and display the properties. It works once, but won't work a second time. When I check the task manager I don't see OCSInventory.exe running.

Because of the crashing, I'm having a hard time reproducing the problem. I do see the correct information in the OCS Inventory server web ui at them moment.

[Didier Liroulet (dliroulet)]

Hi.

Displaying properties with systray applet need OCS service 2.1 installed and running. It do not work with OCS Service 2.0 or 1.X.

I let you do some more testing before closing this bug.

Cheers

[Didier Liroulet (dliroulet)]

Hi,

Any news on this ?

Is the problem still reproducible ?

Cheers

[labiloute (labiloute)]

Hi all !
It happens to us with OCSInventory-NG 2.1.2, agent 2.1.1.1 (latest stable) on Windows.
Only with "HP ProBook 470 G2" and "Realtek RTL8723BE 802.11 b/g/n Wi-Fi Adapter" devices so far.

We first thought that OCS agent was starting prior to the DHCP assignment.
But since it happen only on a specific model, this look more likely to a chipset-specific issue.

Up this thread !