| Roland,
Maybe it just tweaked a security setting - check the permissions on the ODBC files and compare between what you seen booting from the backup and the current setup. Or just try 'repair permissions' on the new setup first?
Jason
-----
Jason Pamental Director of Web Services North Sails
Office: 401.643.1415 Fax: 401.643.1420 Mobile: 401.743.4406
On Mar 9, 2006, at 11:38 AM, Roland Dumas wrote: actually, not the colo, not the server, not the router....I booted from my latest backup (Sunday) and witango has no problems connecting to the datasource. I'm thinking the latest security update broke something.
On Mar 9, 2006, at 7:55 AM, Dan Stein wrote: Usually the colo will require a VPN connection before you a access. They are not going to leave that port open for everyone.
You should contact you colo and they should give you support on this.
on 3/9/06 10:13, Jason Pamental at [EMAIL PROTECTED] wrote:
Roland,
Can you connect with the MySQL admin program from your machine to the colo dev server? If so, then it's probably a config thing on your machine - otherwise it might be blocked on the other end. See if the colo facility blocks traffic on certain ports, or if maybe it's blocked on the dev server itself for non-local traffic (OS firewall settings maybe?)
Just a few more ideas... can't think of anything else at the moment.
Jason
-----
Jason Pamental
Director of Web Services
North Sails
Office: 401.643.1415
Fax: 401.643.1420
Mobile: 401.743.4406
Email: [EMAIL PROTECTED]
On Mar 9, 2006, at 9:45 AM, Roland Dumas wrote:
I checked to make sure port 3306 is open, changed the server IP from old to new IP address. save. reboot., and still can't connect to database. Very perplexing
On Mar 8, 2006, at 10:44 PM, Customer Support wrote:
Roland,
It will look something like this in your odbc.ini file. Make sure you specify the ones in capitals.
[testdb_MySQL_remote]
DRIVER = /usr/lib/libmyodbc3.dylib
Description = Test DB
SERVER = 10.1.1.1
PORT = 3306
User =
Password =
Database = testdb
OPTION = 0
Socket =
Regards
Witango Support
On 09/03/2006, at 5:20 PM, Roland Dumas wrote:
sorry. didn't give all the details:
MacOS X / mysql 4 /ODBC
port 1433?
On Mar 8, 2006, at 9:33 PM, [EMAIL PROTECTED] wrote:
1433
From: "Roland Dumas" <[EMAIL PROTECTED]>
Date: March 8, 2006 9:30:00 PM PST
To: "WiTango List List" <[email protected]>
Subject: Witango-Talk: what port for odbc?
Reply-To: [email protected]
I moved my dev server from next room to a colo. I mucked with DNS so that domain records that used to point to closet now point to the colo properly.
In the Dev Studio, I can't connect to my dev server any more. It says "unable to connect to the data source ... verify that the data source is properly configured and that the database server is online
could it be that I need to open a port in the router? What else should I look at?
Roland A. Dumas
310 W. Bellevue Ave.
San Mateo, CA 94402
650-347-1373
415-412-9300 (cell)
AIM: radumas
[EMAIL PROTECTED]
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
--
--
Dan Stein
FileMaker 7 Certified Developer
Digital Software Solutions
799 Evergreen Circle
Telford PA 18969
Land: 215-799-0192
Cell: 610-256-2843
Fax 413-410-9682
FMP, WiTango, EDI,SQL 2000, MySQL, CWP
[EMAIL PROTECTED]
www.dss-db.com
"It is perfectly safe to stand nowhere."
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
Roland A. Dumas 310 W. Bellevue Ave. San Mateo, CA 94402 650-347-1373 415-412-9300 (cell) AIM: radumas
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
|
