Paul, Interesting: I just tested your DSN-Less connection info. (including port 3307) from my web server to another machine running mysql and it connected fine - but only the first time. I used the IP address for my SERVER variable. Then I changed it to the FQDN and it failed with the same message you're getting. I tried setting up an entry in my hosts file to specify the FQDN of the remote machine along with its associated IP address and it still fails. Then I changed the SERVER variable back to the IP address, and now it won't connect at all again.
Restart the MySQL service on the db machine, fails. Restart WWW service on webserver, fails. Restart IIS Admin on webserver, fails! Try from the ODBC administrator on the webserver using both IP and FQDN, connects every time no problem, DSN-less connection refuses to work at all. I'm going to dig into this a bit tomorrow with a few people at work and see what I can come up with and will let you know. This is starting to bug me too... Armando -----Original Message----- From: Paul Stearns [mailto:[EMAIL PROTECTED] Sent: August 15, 2004 11:51 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: ASP Connection to Mysql fails Armando: I tried the fully qualified domain name 'computer.domain.root', I also tried the IP address. Both worked on the odbc test, but not on the connect string. I have already gone the DSN route and it works, but it bugs me that the DSNless method doesn't work. My current hypothesis is that the odbc driver is confusing (or ignoring)either the ip address or port # for the local mysql DB with what I want for the remote. Paul -----Original Message----- From: Armando [EMAIL PROTECTED];] Sent: 8/15/2004 11:35:44 PM To: [EMAIL PROTECTED] Subject: RE: ASP Connection to Mysql fails Paul, when you say SERVER=myserver.com, are you specifying the FQDN name? ie; thatcomputer.thatdomain.com I know you mentioned you use the same settings in your ASP script as you did in the ODBC data source test but if you didn't specify the FQDN, try it and see what happens. Failing that, try setting up a System DSN in your ODBC Data Sources (since you said you could connect that way) and once the DSN is setup, try setting your ASP connection string to connect to the remote server using the DSN name rather than a DSN-less connection string and see what happens there as well. Cheers. Armando -----Original Message----- From: Paul Stearns [mailto:[EMAIL PROTECTED] Sent: August 15, 2004 4:39 PM To: [EMAIL PROTECTED] Subject: ASP Connection to Mysql fails I have an ASP application running on a server with a mysql DB, everything works great. I connect using localhost, no problems. I have a second mysql DB on another server. I connect to it via the odbc Data Source Administrator from the web server with no problems. When I try to connect from an ASP script from the web server using the following; ========= Set connMailServer = Server.CreateObject("ADODB.Connection") ConnectString = "DRIVER={MySQL ODBC 3.51 Driver}; SERVER=myserver.com; USER=root; PASSWORD=rootPW; DATABASE=myDB; PORT:3307; OPTION=35;" IntDebug=connMailServer.Open(ConnectString) ========= The server, user, password, database and port are what I used in the odbc Data Source Administrator. Remember I can connect to my local DB from ASP. I receive the following error; ========== Microsoft OLE DB Provider for ODBC Drivers error '80004005' [MySQL][ODBC 3.51 Driver]Can't connect to MySQL server on 'myserver.com' (10061) ========= The environment is w2k server on both computers. The MYSql version on remote server is 4.0.17. I'm so confused... Paul -- MySQL Windows Mailing List For list archives: http://lists.mysql.com/win32 To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL Windows Mailing List For list archives: http://lists.mysql.com/win32 To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
