TechRookie
ISP
Web Server:
OS: WinNT 4 SP6a
MyODBC: 2.50.36
SQL Server:
OS: WinNT 4 SP6a
MySQL: 3.23.27
A System DSN setup as:
Windows DSN name: DBTEST
MySql Database: dbtest
Server: xxx.xxx.xxx.xxx
User: my_dbtest_user
Password: my_dbtest_password
When I access the windows DSN with an .asp page I get:
"Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[TCX][MyODBC]Can't connect to MySQL server on 'localhost' (10061)"
I can access the database via a MySQL client so I know it isn't a
permission problem. What stumps me is why it keeps referring to the
MySQL database on localhost and not on the remote machine where MySQL
is actually running.
I have tried:
1) Re-installing MyODBC
2) Creating new DSN with users that have more permissions.
3) Creating new DSN using a NetBIOS name in the server field.
4) Creating new DNS using a DNS name in the server field.
All have had the same results.
Any help would be greatly appreciated.
OS: WinNT 4 SP6a
MyODBC: 2.50.36
SQL Server:
OS: WinNT 4 SP6a
MySQL: 3.23.27
A System DSN setup as:
Windows DSN name: DBTEST
MySql Database: dbtest
Server: xxx.xxx.xxx.xxx
User: my_dbtest_user
Password: my_dbtest_password
When I access the windows DSN with an .asp page I get:
"Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[TCX][MyODBC]Can't connect to MySQL server on 'localhost' (10061)"
I can access the database via a MySQL client so I know it isn't a
permission problem. What stumps me is why it keeps referring to the
MySQL database on localhost and not on the remote machine where MySQL
is actually running.
I have tried:
1) Re-installing MyODBC
2) Creating new DSN with users that have more permissions.
3) Creating new DSN using a NetBIOS name in the server field.
4) Creating new DNS using a DNS name in the server field.
All have had the same results.
Any help would be greatly appreciated.