Problem: unable to connect from Sybase Central to my SQL Anywhere 11
Web Edition server.

OK when server is running on local network but fails to connect to
server running on Internet.

I can ping the Internet server from command line but cannot succeed
using Sybase Central ping button.

My client OS is CentOS 5.2. My server OS is also CentOS 5.2.

Results from Test Connection in Sybase Central

Fri Jan 16 2009 07:42:08
07:42:08 Attempting to connect using:
UID=DBA;PWD=********;ENG=webbox_demo;CON=SQL_DBC_8 ea4940;LOG=/tmp/
testcon57745.tmp;LINKS='TCPIP(IP=syskitchen.com;PO RT=8080)'
07:42:08 Attempting to connect to a running server...
07:42:08 Trying to start TCPIP link ...
07:42:08 My IP address is 127.0.0.1
07:42:08 My IP address is 192.168.1.111
07:42:08 My IP address is ::1%1
07:42:08 My IP address is fe80::209:6bff:fe61:7b5f%2
07:42:08 TCPIP link started successfully
07:42:08 Attempting TCPIP connection (no sasrv.ini cached address)
07:42:08 Looking for server with name webbox_demo
07:42:08 Trying to find server at address syskitchen.com
07:42:08 Found server, verifying server name
07:42:13 Verification of server name failed
....

I believe that is part of the Web Edition
(agreed to) conditions. Sybase Central is not
a web application.

As seen at http://www.sybase.com/detail?id=1057272
SQL Anywhere Web Edition
Free database development and deployment of ***web applications*** using
PHP, Java, ASP.NET and more.

Click here to read the SQL Anywhere Web Edition FAQ.
http://www.sybase.com/detail?id=1057560






<wytcom (AT) gmail (DOT) com> wrote

Maybe so... But the Web Edition FAQ statement below seems to imply
that Sybase Central should work with the web edition. Also the fact
that Sybase Central and Interactive SQL are both included with the web
edition download leads me to believe that they can work with it.

From the web edition FAQ:
What about administration and maintenance tasks?

The SQL Anywhere Web Edition includes a comprehensive set of powerful
tools and utilities for administration and maintenance. The SQL
Anywhere Web Edition is not limited to web browser applications for
administration tasks, maintenance tasks, or data import/export tasks.
However, the primary purpose for SQL Anywhere must be to support
interactive web browser applications.

And it does! You've already seen that in action.

This section

means Sybase Central and the other admin. utility will work
with it. I.E. they are not locked as as other non-web tools
would be; not that they are web-based tools. In fact the
phrase "not limited to web browser applications for" is
a pretty good indication that the admin. tools are not.

"wytcom" <wytcom (AT) gmail (DOT) com> wrote

The error that you are getting implies that the name of the server
that is running on "syskitchen.com" is not named "webbox_demo".
How did you start your server on syskitchen.com?
Is there more than one server running on syskitchen.com?
--
Mark Culp
SQLAnywhere Research and Development
Sybase iAnywhere Engineering
-------------------------------------------------------------------------
-- SQL Anywhere Blog Center - http://www.sybase.com/sqlanyblogs
-- SQL Anywhere Developer Community:
-- http://www.sybase.com/developer/libr...ere-techcorner
-------------------------------------------------------------------------
wytcom (AT) gmail (DOT) com wrote:

You are attempting to have Sybase Central connect to port 8080. I would
guess that you have started your server with "-xs http(port=8080)",
which means that the server is listening for *http* connections on port
8080, not standard connections like those used by Sybase Central. You
want to remove the port= option altogether. If the server is started on
a different port (using "-x tcpip(port=xxx)"), replace the 8080 with
that port number (xxx).

It works over the LAN because the client will send out a UDP broadcast
on both port 8080 and the default port (2638) looking for the server. In
that case, the server hears the broadcast on 2638 and responds,
including its port number in the broadcast response. In the Internet
case, the broadcast never reaches the server so it simply makes a TCP
connection to the address you've given.

Graeme Perrow
Senior Software Developer
gperrow _at_ ianywhere _dot_ com
Sybase iAnywhere Engineering

SQL Anywhere Developer Community
http://www.sybase.com/developer/libr...ere-techcorner
SQL Anywhere Blog Center
http://www.sybase.com/sqlanyblogs


wytcom (AT) gmail (DOT) com wrote:

Thank you Graeme Perrow. I understand now and my connection works. I
can now start the SQL Anywhere Web Edition server either to handle web
requests or to connect with Sybase Central and Interactive SQL. I
don't know yet if I can launch the server once in such a way that it
will handle both types of connection though.

I am now able to run the SQL Anywhere Web Edition server so that it
will respond to web requests and also connect to Sybase Central and
Interactive SQL. Command is dbsrv11 -xs http{port=8080} ... This
handles the web requests on port 8080 and by default the standard
connection from Sybase tools on port 2638. In addition to
understanding that the Sybase tools do not connect via HTTP, part of
my problem was making sure these ports were not blocked by the
firewall on the serving computer.