MySQL Bugs: #25949: 3306 port taken by Symantec & Windows Security Center does not create error

Bug #25949	3306 port taken by Symantec & Windows Security Center does not create error
Submitted:	30 Jan 2007 15:32	Modified:	5 Feb 2007 14:05
Reporter:	Jeannette Browning	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S3 (Non-critical)
Version:	5.0	OS:	Windows (WinXP)
Assigned to:		CPU Architecture:	Any
Tags:	conflict, port

Description:
Symantec Internet Security and Windows XP Security Center conflict over port 3306, making it impossible to use, at least that's the "effect" on a Compaq Presario V6101US notebook. I don't expect an answer to my question, here, but it would be nice if the MySQL 5 Wizard were able to recognize the problem and suggest actual potential solutions, instead of bailing out with a screen full of geekspeek.

Thanks,
Dave Oshel
dcoshel@pobox.com

How to repeat:
Symantec Internet Security and Windows XP Security Center conflict over port 3306, making it impossible to use, at least that's the "effect" on a Compaq Presario V6101US notebook.

Suggested fix:
Minimum - produce error vs. dump.

Hi and thanks for your report.

Looking over and over again I think there's only one scenario possible; *both* Symantec and WinXP firewalls are turned on blocking access to port 3306. Pleasae dissable one of the firewalls and add rule to allow access to port 3306 as moving MySQL server from port 3306 would not solve anything... I fail to see how this is connected to MySQL A.B. 

Symantes search on
http://searchg.symantec.com/search?q=3306&charset=utf-8&proxystylesheet=symc_en_US&client=...
shows nothing similar to this...

If you have any more information to provide regarding this, please reopen the report.