MySQL Bugs: #24853: Default port not added to Vista firewall exceptions list

Bug #24853	Default port not added to Vista firewall exceptions list
Submitted:	6 Dec 2006 14:26	Modified:	17 Mar 2008 19:57
Reporter:	Horst Hunger	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S3 (Non-critical)
Version:	5.0.27, 5.0.34, 5.0.37	OS:	Windows (Vista)
Assigned to:	Iggy Galarza	CPU Architecture:	Any
Tags:	vista

Description:
After the installation of Mysql on Vista remote access was rejected
(Firewall was active with mysqld as program within exception).
I switch off the firewall completely and remote login (and telnet) was successful!!!!
Then I switched on firewall, but add port 3309 to exceptions (allow a program through Windows firewall) and remote access was successful.

How to repeat:
see above.

Suggested fix:
Not only mysqld as program but also the default port should be added to the exceptions by the installation process.

Thank you for the report.

It will be verified and fixed in nearest feature when we start support Windows Vista.

Thank you for the report.

Verified as described even if "allow remote connections" has checked.

- Verified the 'add firewall exception' function works for whatever port is selected
- Verified firewall exceptions are not added unless the GUI checkbox is selected

- NOTE - Firewall exception will not be created if Windows Firewall has 'Do Not Allow Exceptions' set.  Should probably document this behavior

- NOTE - Reconfiguring the instance w/o selecting the 'add exception' box will not remove an existing firewall exception -- might want to document this.

Ok to push

Noted in 5.0.51a, 5.1.23 changelogs.

For Vista installs, MySQLInstanceConfig.exe did not add the default
MySQL port to the firewall exceptions. It now provides a checkbox 
that enables the user a choice of whether to do this.