Menu

#4 Connection problem

open
nobody
None
5
2004-07-02
2004-07-02
No

Hello,

I am setting up ODBC Socket Server to allow creation of
reports on an Linux/Apache/MySQL/php web
server that access a remote SQL Server database. The
remote site has 2 servers - one that is
accesible externally via a static IP address, and one that
is only accessed internally with the SQL
Server database. The Socket Server has been installed
succesfully on the server that has external
access, and a user DSN set up on the same server to
connect to the database server.

The DNS 'test' function reports success, implying that it
can talk to the database. The results of
running the Socket Server client, both on the server and
remotely, is as follows:

Results (received 123 bytes):
<?xml version="1.0"?>
<result status="failure">
<error>Communication error, connection possibly
denied</error>
</result>

The ODBC connection string used
is "DSN=SWSReporting;UID=sa;PWD=;" along with the
IP of the
externally accessed server and the default port number.

I am assuming that the UID/PWD in the ODBC connection
string should be the same as that in the DSN?

Have you any ideas where we could look to try and
resolve this please?

Regards,

Paul

Paul Bennett
Approach Computing
www.approach-computing.co.uk

Discussion


Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.