curious anomoly

[expired user #5583]'s profile image [expired user #5583] posted 12 years ago in General Permalink
Just installed heidi on winxp running in virtualbox on a win7 host. Wanted to connect to mysql on another machine but couldn't logon although user,pword,host address,tcp are all correct (double checked). I can connect to the server using heidisql on win7 host. So I exported the registry settings for heidi on win7 and imported them into the winxp client in virtualbox. Heidisql then ran perfectly. So there seems to be a very tiny difference between the procedures which test the connection and the one which makes the connection. It's not a problem, but I found it interesting and thought I should mention it. It would be nice to have the option of displaying the logon passwords in plain text as a quick way of checking that they are correct. However, in this case, the password and username were 1000% correct!
ansgar's profile image ansgar posted 12 years ago Permalink
Which version of Heidi is it? Both machines had the same one?

Which connection error did you get?
[expired user #5583]'s profile image [expired user #5583] posted 12 years ago Permalink
forgot those details, sorry. both are 6004034. error was 10060, unable to connect using bill, password: yes
jfalch's profile image jfalch posted 12 years ago Permalink
10060 does not look like a MySQL error code to me; could be winsock error 10060 WSAETIMEDOUT, connection timed out - ie could not contact partner on tcp/ip level
jfalch's profile image jfalch posted 12 years ago Permalink
..firewall ?
kalvaro's profile image kalvaro posted 12 years ago Permalink
In VirtualBox there're like half a dozen different methods to configure networking for virtual machines. I've never dug into the details (I just leave the default values) but I bet they really matter when you try to connect to other machines inside the LAN. For instance, if your MySQL server is configured to accept remote connections only from 192.168.0.0/24 and VirtualBox happens to create its own subnetwork with host and guest, it's possible that the real LAN is actually unreachable.

I suggest you do the usual TCP/IP troubleshooting: ping, DNS resolution, firewalls...
[expired user #5583]'s profile image [expired user #5583] posted 12 years ago Permalink
Its working fine so its not a problem. I couldnt get it to connect using the correct network type, hostaddress, username and password but it worked fine when I copied the heidisql registry settings from win7 which is hosting virtualbox to the the registry for winxp which is running in virtualbox. But before that, I had proven that access was possible with pings and traces and calling webpages on the same remote server. So it seems to me that heidisql uses a different method in connecting to a server with what it knows is valid data than it does when testing a new connection to see if the data is correct. ie in one case heidisql says bluntly "connect using this data" and is connected whereas in the other case it asks politely "can i connect using this data" and is told NO. However, its not a problem, I just found it curious and thought I'd mention it.

Please login to leave a reply, or register at first.