Bug #10909 Potential 2-15 second delays when connecting due to netbios lookup
Submitted: 27 May 2005 9:16 Modified: 27 Jun 2005 14:35
Reporter: Stephen Irven Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.1.12 OS:Windows (Windows Server 2003)
Assigned to: CPU Architecture:Any

[27 May 2005 9:16] Stephen Irven 
Description:
When connecting to the MySQL server by IP address from a local network machine, the server attempts a name lookup on the client using netbios.

This appears to occur even when netbios is disabled on both machines, and if this is the case, a delay in connection is observed ranging between 2seconds and 15 seconds depending on connecting hardware layout - presumably before windows networking gives up trying to connect.

A workaround seems to be to add the client IP address in the windows/system32/etc/hosts file on the server to prevent it needing to lookup the machine.

Unknown: does the server attempt to lookup the client with netbios even if the client is running on a non-windows machine?

How to repeat:
Start a server running on windows, disable netbios on server and client machines. Connect from a client on the same network.

Netbios lookup, and associated delay can be shown by ethereal or other network monitoring software.

The lookup seems to be independent of client driver (MyODBC / PHP driver / MySQL bundled client software), but may be avoided by using a client on a remote network.

Suggested fix:
Remove netbios lookup from server networking code unless support is known to be in place.
[27 May 2005 14:35] MySQL Verification Team 
Could you please test starting the server with:

--skip-name-resolve

Thanks in advance.
[27 Jun 2005 23:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".