Question : ODBC DSN parameters- how conect to SQL Anywhere v10 server over network?

Hi,  we've just upgraded to Sybase SQL Anywhere v10 from v5.5 (long story, we had a 16 bit app that could not be ported past v5.5 and it kept us on v5.5 but we're finally now moving to v10)

We are setting our first system up for one of our customers. They want a mirrored database system so we have three machines (two servers and one arbiter) and the high availability option set up. We are running two windows 2003 servers - one for the primary database, one for the mirror database, and the arbiter on a windows XP system.

We have a C++ application that connects to the database using a DSN. This app was written to, once connected, keep its connection open and only use the one connection for all its queries and inserts and deletes.

We also have a C#/.NET application that uses connection strings, connects to the database, runs its query, and then immediately disconnects from the database.

My C# app works fine. It collects data from sensors in cleanrooms, and if I log into ISQL on the server, I can see that it is successfully inserting all the data it gathers. It is reporting no connection errors either in its own application logs.

My C++ app (run on the Arbiter machine) lets me view the data the C# app inserted. Some times it connects to the database, sometimes immediately gets disconnected. Sometimes it will connect and stay connected successfully for a bit, then suddenly (not at any set time or duration), it will get disconnected.

I see the same behavior if I try to connnect to the database using a DSN with ISQL and SybaseCentral. They will connect then get disconnected, sometimes immedately. They won't stay connected for longer than maybe 10 minutes or so (at most).

In my DSN on the Arbiter machine I list-
DSN Name=LMS
Server Name =LMS
Database name=LMS10
check TCPIP
      have tried  entering the port numbers in the TCPIP field (2637,2638,2639),
      and another time the hosts  (Host=lms-dataserver1;Host=lms-dataserver2)
     neither has seemed to make a difference...
Check Shared Memory
Set Liveliness timeout to 7200
Set Idle timeout to 0

I see the same disconnect issues if I try running ISQL or Sybase Central and connect using a DSN instead of entering the specific database name and server name.

ISQL Will stay up though if I connect by entering the server and database names (not using a DSN).

What am I missing?
If I run my C++ app directly on the server, even with a DSN, it runs ok.
But if I try to run it (or ISQL using a DSN) on the Arbiter machine, it disconnects randomly. And sometimes won't even connect.

These three machines, my server1, server2 and arbiter machine each have two network cards. One is for the customer's network, the other is a private network between the three machines.

My IT guys keep telling me the hardware is ok - we can see each machine from the other, and can access each other machine's files. Also a clustered web server is running over the three successfully, so hence, my IT guys think the hardware is OK.

what do I need in my DSN???  Or what is messed up?

Thanks!
HC

Answer : ODBC DSN parameters- how conect to SQL Anywhere v10 server over network?

PAQed with points refunded (500)

Computer101
EE Admin