MySql 5.0 community server remote access stopped working

Hello,
I have a client program that I use to access a MySql 5.0 community server. The client can be on the machine where the MySql server is installed or from a remote machine.

The client has worked fine for 1/2 a year from both the local machine and from remote. I installed the server in january. After returning from vacation in july, I cannot access the server from a remote machine anymore. But the client that is locally on the same machine as the server manage to access it.

Has anybody else encountered this problem? Any ideas what I can do to be able to access again?

best regards
Kurt

What's the error message you get when you try to connect to it?
Can you ping the server?
Perhaps the remote user rights were edited?

Hello, thanks for the reply.

It looks like this is a message from the client program because it crashes with a fatal Run-Time error before it returns message from MySql. Anyhow, the message is: The program has caused a 'General Protection' fault at 001B:685004C9.

Yes, I can ping the server machine from the remote machine.

best regards
Kurt

Hello again,
sorry, I forgot to answer the last question:
The server is installed on one of my personal computers, so unless the IT department has hacked something, I do not think something has been changed. How can I check it?

Could it be a network security problem? If so, how can I come around it?

Best regards

Hello, thanks for the reply.

It looks like this is a message from the client program because it crashes with a fatal Run-Time error before it returns message from MySql. Anyhow, the message is: The program has caused a 'General Protection' fault at 001B:685004C9.

Yes, I can ping the server machine from the remote machine.

best regards
Kurt

So, by "client program" you mean some specially written software, right?
And, by "'General Protection' fault" you mean on Windows, correct?

In the case of specialized software, you want to go back to the basics: Run the simple MySQL Command Line Client and see if you can log in that way.

I'm guessing that a firewall setting or log-in info got changed somewhere. Let us know if you are on Windows or not. Thanks.

Yes, that is a special written sw that has not been changed, and has been working perfectly before, and still does, but now only when running from the server machine, not from the remote machine anymore.

Yes, I am running windows 2000 professional on the server machine, and XP on the remote machine.

I tried the connect command as well as -u x -h y -p but did not manage to get it to work on local nor on remote login. Did not find anything that said very clearly how to logon to a remote machine, so I tried telnet [ipaddr] 3306

Telnet returned some rubbish on localhost (indicating some sort of command conflict which is ok since the MySql server did not recognize the command being sent)
But on remote host, it returned with "Host 'MyRemoteMachin e' is not allowed to connect to this MySql server"

Can that still be firewall? It seems to me that the remote machine got in touch with the server since the return string indicated that the process is a MySql server.

We are running F-Secure, and it has some intrusion preventing popup asking whether we want to allow the client to connect... but that popup was there before it stopped working as well.

best regards
Kurt

<snip>But on remote host, it returned with "Host 'MyRemoteMachin e' is not allowed to connect to this MySql server"

Can that still be firewall? It seems to me that the remote machine got in touch with the server since the return string indicated that the process is a MySql server.

We are running F-Secure, and it has some intrusion preventing popup asking whether we want to allow the client to connect... but that popup was there before it stopped working as well.

best regards
Kurt

That sure sounds like the cause to me.

Hello again,
after disabling the antivirus program the server could still not be accessed. Hence it was not the firewall.

It turned out that (although the user had not been changed) dropping the user and creating it again with grant all did the trick. Don't know why.

best regards
Kurt