Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ipaddr in hardware table diferent from ipaddr in networks table #102

Open
pchamo opened this issue Sep 13, 2018 · 3 comments
Open

Ipaddr in hardware table diferent from ipaddr in networks table #102

pchamo opened this issue Sep 13, 2018 · 3 comments
Milestone

Comments

@pchamo
Copy link

pchamo commented Sep 13, 2018

General information

Operating system : Windows 7/10

OCS Inventory information

Windows agent version : 2.4.0.0 and 2.1.0.3

Problem's description

  • Inconsistent info registered in networks and hardware ocsinventory tables.
  • IP addresses registered in hardware table is different from the ones registered in networks table.

Please, look: http://prntscr.com/ku4bnh

Thank you

@pchamo
Copy link
Author

pchamo commented Sep 17, 2018

What I see is that the issue is not exclusive of the Windows agent version. And as far as I can see, the ocs agent doesn't clean the networks table before updating the network address info, and doesn't update the network info in the hardware table, I mean, it doesn't check that the network info of the main network adapter is syncronized. It's a shame.

@charleneauger charleneauger added this to the 2.6.0.0 milestone Jan 8, 2019
@alexandreChichmanian
Copy link

alexandreChichmanian commented Jul 8, 2020

Hello @charleneauger @gillesdubois , is there any news regarding this issue? I'm facing the same problem and I found a pseudo work arround by deleting the laststate file. It forces the resynch of the table which works once, but the problem is still here and the laststate file needs to be deleted again to force the synch again which is not optimal.

Thanks

@alexandreChichmanian
Copy link

Hello @gillesdubois @charleneauger, is there any news regarding the issue?

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants