search

OCAAlliance / OcaToolsAndDemos

Source code repository of OCAMicro and AES70 Compliancy Test Tool
Other
39 stars 21 forks source link

Aes70CompliancyTestTool: Failed to setup TCP connection to test device #20

Closed HermansDavy closed 2 years ago

HermansDavy commented 3 years ago

Hello all,

We got since this week an issue with the Aes70CompliancyTestTool:

call: Aes70CompliancyTestTool.exe -d "name" -s tcp -v AES70-2018

Results in ... [Test Suite][Result] - Prepare test (OCP.1 KeepAlive mechanism) result: Passed GetAddrInfo failed, error 11001, errno 0 GetAddrInfo failed, error 11001, errno 0 GetAddrInfo failed, error 11001, errno 0 [OCP.1 KeepAlive mechanism][Result] Test OCP.1 KeepAlive mechanism is now unsuccesfull ...

In each of the 5 tests this "GetAddrInfo failed" error happens.

Any idea what the problem can be? Looks like a Windows Update broke something, because last week, this error did not occur with the same tool, and same test device.

Best regards

Davy

tljdebrouwer commented 3 years ago

Hi,

Are there any special characters in your host name?

Op wo 23 jun. 2021 om 18:51 schreef HermansDavy @.***>

Hello all,

We got since this week an issue with the Aes70CompliancyTestTool:

call: Aes70CompliancyTestTool.exe -d "name" -s tcp -v AES70-2018

Results in ... [Test Suite][Result] - Prepare test (OCP.1 KeepAlive mechanism) result: Passed GetAddrInfo failed, error 11001, errno 0 GetAddrInfo failed, error 11001, errno 0 GetAddrInfo failed, error 11001, errno 0 [OCP.1 KeepAlive mechanism][Result] Test OCP.1 KeepAlive mechanism is now unsuccesfull ...

In each of the 5 tests this "GetAddrInfo failed" error happens.

Any idea what the problem can be? Looks like a Windows Update broke something, because last week, this error did not occur with the same tool, and same test device.

Best regards

Davy

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/OCAAlliance/OcaToolsAndDemos/issues/20, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVHAC3H6QK7MHGVK34SJ4LTUIGKNANCNFSM47GGB6QA .

-- met vriendelijke groet, Tom de Brouwer

HermansDavy commented 3 years ago

Hello Tom,

No, not really: "DESKTOP-AQ8R5UM" I changed it to "PCDavy", but still the same result.

Best regards

Davy

tljdebrouwer commented 3 years ago

I don’t have a windows machine at hand. But you could try to reinstall bonjour for windows (mdnsresponder). Also you can try with the dns-sd command to resolve the ip. From head I believe “dns-sd -G v4 PCDavy.local” and see if that works?

Op 23 jun. 2021 om 19:14 heeft HermansDavy @.***> het volgende geschreven:

 No, not really: "DESKTOP-AQ8R5UM" I changed it to "PCDavy", but still the same result.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

HermansDavy commented 3 years ago

Hello Tom,

Thank you very much for the info: After reinstalling the bonjour service, problem was solved!

Best regards

Davy

tljdebrouwer commented 3 years ago

Cool, so something broke the os name resolver chain towards mdnsresponder.

Probably it’s very difficult to find the exact root cause. Happy it’s resolved now.

Op wo 23 jun. 2021 om 19:39 schreef HermansDavy @.***>

Hello Tom,

Thank you very much for the info: After reinstalling the bonjour service, problem was solved!

Best regards

Davy

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/OCAAlliance/OcaToolsAndDemos/issues/20#issuecomment-867032514, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVHAC4QXUR7Y5KSPA4IAE3TUIL4BANCNFSM47GGB6QA .

-- met vriendelijke groet, Tom de Brouwer

tljdebrouwer commented 2 years ago

Closing since no updates for a while.