Windows Firewall Security interferring with MySQL?

[Richard]

Hi All,

I'm running WinXP-Pro/SP2, MySQL 5.0.15-nt and Windows
Firewall/Internet Connection Sharing. I run on an account that's a
member of Administrator accounts.

Control Panel | Administrative Tools | Services indicates that both
MySQL and Windows Firewall run as services that start automatically and
log on as a Local System account.

From time to time MySQL refuses to allow me to log on as root. Also,

when I check communication with the MySQL server using "telnet
localhost 3306", I get a trash response ... sort of an amalgamation of
Arabic, Farsi and Hebrew ... none of which I recognize nor speak

Incidentally, MySql.ini is configured to have MySQL listen to port
3303 on localhost.

Questions:

1. How can I determine what program image MySQL runs to provide this
service?

Start | Run "firewall.cpl" provides a "Windows Firewall" dialog
with an "Exceptions" tab that lists "mysqld-max". I want to
confirm that this is the image the MySQL service starts up with.

2. How can I determine if I'm inadvertently running any other
firewalls?

3. Is there anything else I should check for?

Thanks in Advance,
Richard

 

[Guest]

Hi All,

I'm running WinXP-Pro/SP2, MySQL 5.0.15-nt and Windows
Firewall/Internet Connection Sharing. I run on an account that's a
member of Administrator accounts.

Control Panel | Administrative Tools | Services indicates that both
MySQL and Windows Firewall run as services that start automatically and
log on as a Local System account.

when I check communication with the MySQL server using "telnet
localhost 3306", I get a trash response ... sort of an amalgamation of
Arabic, Farsi and Hebrew ... none of which I recognize nor speak

Incidentally, MySql.ini is configured to have MySQL listen to port
3303 on localhost.

Questions:

1. How can I determine what program image MySQL runs to provide this
service?

Start | Run "firewall.cpl" provides a "Windows Firewall" dialog
with an "Exceptions" tab that lists "mysqld-max". I want to
confirm that this is the image the MySQL service starts up with.

2. How can I determine if I'm inadvertently running any other
firewalls?

3. Is there anything else I should check for?

Thanks in Advance,
Richard

Ok, first ensure that mysql daemon is running, in a command prompt type
netstat -an and see if port 3303 is listening, second thing is, when
you get an error, open up event viewer.. start/programs/admin/ and have
a looka nd see what the errors say about it, that will give you a
better idea of what the problem is.

Flamer.

 

[Haggis]

Ok, first ensure that mysql daemon is running, in a command prompt type
netstat -an and see if port 3303 is listening, second thing is, when
you get an error, open up event viewer.. start/programs/admin/ and have
a looka nd see what the errors say about it, that will give you a
better idea of what the problem is.

Flamer.

what does the MySql Administrator say is running?

 

[Richard]

Hi Flamer,

Thanks for responding. Prior to receiving your post, I got a solution
from Gordon Burditt on the thread
http://groups.google.com/group/mailing.database.mysql/browse_frm/thread/6cc5cccab3c92fc7/#.

netstat -an and see if port 3303 is listening

I very much appreciate this advice. I'm set up to have MySQL listen to
port 3306. When I checked this out, I got some interesting results
just after I started up MySQL with "net start mysql":

Windows Task Manager shows that a process with Image Name
"mysql-nt.exe" is started.
Administrative Tools | Services shows that the status of a service
named "MySQL" is "Started". A few iterations of netstat -an filtered
for "330" shows:

K:\>netstat -an | find "330" [Does this have anything to do with MySQL
server?]
TCP 0.0.0.0:3306 0.0.0.0:0 LISTENING

K:\>netstat -an | find "330"
TCP 0.0.0.0:3306 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1239 127.0.0.1:3306 TIME_WAIT
[I've got localhost set to "127.0.0.1" in the hosts file, so the
TIME_WAIT entry suggests to me that the MySQL server is listening to
localhost:3306 after some delay. Do you agree?]

K:\>netstat -an | find "330" [After starting "mysql" client in
another Command Window]
TCP 0.0.0.0:3306 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1239 127.0.0.1:3306 ESTABLISHED
TCP 127.0.0.1:3306 127.0.0.1:1239 ESTABLISHED
[The EST. entry suggests to me that the MySQL server is "established"
as a listener on localhost:3306, now that it has a client connected.
Do you agree?]

The EST. status remains as I execute statements in the client. When I
shut down the one-and-ony client, the status reverts to:

K:\>netstat -an | find "330"
TCP 0.0.0.0:3306 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1239 127.0.0.1:3306 TIME_WAIT

After I issue "mysqladmin shutdown" (I've got root's name and pswd set
in mysql.ini), I get:

K:\>netstat -an | find "330"
[Empty list]

So it looks like the first netstat above was indicating a MySQL server
was "listening" to a port on a non-existing site; next netstat
indicated that the server was now listening to 3306 on local host. Do
you agree?

Best wishes,
Richard