Bug #57962 mysqld does not bind to any IP on Dual Port Server Adapter
Submitted: 3 Nov 2010 22:19 Modified: 30 Jan 2012 18:33
Reporter: Holger Mueller Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Windows Severity:S2 (Serious)
Version:5.5.13 OS:Microsoft Windows (2003 x64)
Assigned to: CPU Architecture:Any
Tags: mysqld tcp port bind bind-address dual-port-nic, regression

[3 Nov 2010 22:19] Holger Mueller
Description:
I tried to update from 5.1.x to 5.5.6-rc on a windows-server-box (x64) which uses 4 network cards combined to one IP (Intel Team / Intel PRO/1000 PT Dual Port Server Adapter and Broadcom BCM5708C).
After starting the service I could not connect to the server - only from command-line-client directly on the same host. 
I used MS process explorer (sysinternals) to see if the port 3306 is open: it was not tho mysqld writes to the event log that it is listening to that port. I also checked system variables 'port' and 'skip-networking'.
After further investigation I found out that putting 'bind-address=192.168.0.1' in my.cnf fixes the problem.

How to repeat:
Do a clean installation of 5.5.6-rc on windows-machine with Intel PRO/1000 PT Dual Port Server Adapter or Broadcom BCM5708C and try to connect to the service via TCP (not socket) or check NETSTAT to see that there is no port open..

Suggested fix:
compare algorithm with 5.1 series which works fine with these NIC's
[22 May 2011 14:47] Valeriy Kravchuk
Please, check if the same problem still happens with a recent version, 5.5.12.
[22 Jun 2011 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".
[24 Jun 2011 14:26] Holger Mueller
sorry for letting you wait, but the server is located at a customers office where i don't have regular access to.
yesterday i updated to 5.5.13 and still same problem.
i figured out that it also works when setting bind-address to 0.0.0.0.
only leaving this parameter out (which i guess should do the same) does not work.
[30 Dec 2011 18:33] Valeriy Kravchuk
Please, check if recent version, 5.5.19, is still affected.
[31 Jan 2012 1: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".