Dynamic IP Issue

I still use a dynamic ip.

Usually, this does not cause a problem.

Occasionally, though, the ip will change while heidisql is just part-way through exporting posts.

Since, my forum is, relatively large, busy, and, so, slow to export, there is usually no way for me to catch onto the problem until after hours have passed and I get tired of waiting for heidisql to finish.

So, to save me from needlessly waiting, how about making heidisql occasionally try re-submitting my ip to the server? If the server rejects the ip, then heidisql can display a warning sign and alert me to the fact that exporting has stopped.

- j

Exporting should not take so long with a newer revision. Unless you are using a 4.0 release?

I don't get the problem exactly - in my understanding, your computer will be offline for some seconds while your provider forces you to get a new IP address. Then, HeidiSQL will of course have killed any running connection, but then reconnect when needed.

No. The ip has changed, on numerous occasions, during export - this why I am raising the issue.

When it happens, heidisql appears to just hang and this creates the false image that it is just waiting for info, from the server.

So, I'm wondering if there is a way to alert the user, during export, that heidisql has stopped.

- j

Which revision/version?

While your IP changes, you will definitely be disconnected from *any* network for a short while, and then, if the software in question has a reconnection logic, won't notice that disconnect. HeidiSQL does a reconnect, so that's why I would say you should not notice any error.

1. I use the latest version.

2. When the ip changes and Heidisql is started up, for the first time, a SQL Error (1130) message appears.

My server will not allow a computer to connect if that computer is without the proper ip.

So, when my ip changes from what the server has on record, then my Heidisql is prevented from accessing the server and exporting further from it; my server does not recognize Heidisql's reconnect attempts if Heidisql is coming from a computer that has a new ip. Yet, unlike the initial start up case, above, there is no error message - just a hanging Heidisql.

Hence, my request for a warning, from Heidisql.

- j

Well, you are right - that hanging should be fixed. However, you should verify that your IPs are always allowed to connect, shouldn't you?

When my ip changes, then, among other things, I have to re-set the recorded ip, at the server.

After all that is done, depending on the time of day, I will usually just re-start Heidisql.

- j

What about accepting "%" (= all ips) as host?

No. That might create a security threat. I don't want to make life easier, for hackers.

- j

Yes, right. Set up DynDns ?

DynDns ?

- j

http://www.dyndns.com/ has a "Free Dynamic DNS" service which you can use to get a fully qualified hostname for a dynamic ip address. A small client tool will ping the server after your ip has changed. In the end you always have the same hostname, with changing ips, e.g. jamsession.dyndns.org or whatever they provide.

On the MySQL server, you will just need to add this hostname instead of the ip.

My host would never go for that and I might be opening myself up to liability.

So, no.

- j

Wait. I didn't read your previous post. So, let me get back to you.

- j

After having looked a little into http://www.dyndns.com/ and considering your post (20:12), I don't think that http://www.dyndns.com/ will work for me.

I wish that http://www.dyndns.com/ would just spell out what you said in a straight-forward manner, though, because I haven't got a lot of time to read all the stuff, at their website.

But, just based on my initial investigation, http://www.dyndns.com/ does not sound like something that would work, for my situation.

Thanks, however, for the suggestion!

- j