tony

Summary for clarification Problem: Using the default c-ares resolver on Windows does not resolve names that are netbios names and not in DNS. E.g. the local machine name is not...

I've created a PR to update the documentation for the resolvers https://github.com/grpc/grpc/pull/31385

@jtattermusch I suggest we close this with no fix planned as the documentation has now been updated for NetBIOS support: https://github.com/grpc/grpc/blob/master/doc/environment_variables.md

As a workaround - once https://github.com/grpc/grpc/issues/27099 is released (it has been merged) you will be able to use the GRPC_PROTOC_PLUGIN environment variable to point to your own plugin that is...

Nothing obvious from the provided logs. Theory which I need to test, and for which I might not have enough information to confirm: - c-ares does not do NetBIOS lookups...

@roitenen1981 I can confirm the theory in my comment above with the same tests I did for https://github.com/grpc/grpc/issues/25252 However I do not know if this is what you are seeing....

@roitenen1981 NetBIOS support is now documented: https://github.com/grpc/grpc/blob/master/doc/environment_variables.md @jtattermusch shall we close this or wait for more feedback?

@qifzhou Is this still a problem? Are you able to give more details - e.g. version of IIS, version of .NET

I've created a new PR to fix the hanging in a different way: https://github.com/grpc/grpc/pull/31450 This does not address why the status is corrupt when reading it. I cannot reproduce that....

Your client continuously creates new threads to send requests to the server, without waiting for the results of previous threads. Your server responds to each request with a 2 second...