• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 220
  • Last Modified:

Timeout Period for WSAAsynGetHostByName

Using the asynchronous name resolution for the Winsock library "WSAAsyncGetHostByName" is there a maximum timeout for when the callback will happen if the name has not been successfully resolved and the resolver fails? Is this determined by the implementation of the local resolver/stack?
0
xen15
Asked:
xen15
  • 2
  • 2
1 Solution
 
vinniewCommented:
I want to say that with all Async... calls, the timeout is the same and is kept in the registry( in NT 3.51 for sure, 4.0 server, too).

Since these values are kept in the MSTCP portion of the registry and not in a system key, a different stack would control them locally as well.

Hope this helps,

V

0
 
xen15Author Commented:
Do you know how to decode the values in the MSTCP registry key to see what the timings are: I imagine you refer to the HKEY_LOCAL_MACHINE...\Bindings\ConfigFlags key?
0
 
vinniewCommented:
On which platform?

NTWS 4.0, WIN94 don't have the settings.  NT 3.51, NT Server 4.0 do.

0
 
xen15Author Commented:
I found the above key on Win95. I couldn't find it in NTWS4.0
I'm also interested in Win 3.11, obviously this wouldn't be a registry key though, is there an ini file setting?
0

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now