I work for DataDirect-Technologies. My customer is using our Connect for ODBC
5.00.0059 driver on Solaris 8 to connect to SQL Server 7 on Win 2000. When he
tries to connect using a simple C application he gets the error
"[DataDirect][ODBC SQL Server Driver][SQL Server]Cannot open database
requested in login 'northwind'. Login fails." The customer has tried using
the IP Address and the machine name. He has tried connecting to Northwind and
Master. He is using the sa login with a password. He is able to connect with
the same information from a Windows machine either using Windows
Authentication or SQL Server authentication.
There must be some setting within his SQL Server database that does not
allow remote connections, is anyone aware of something like this?
Actually, to update the issue: the customer can connect from a remote Windows
client to his SQL Server 7 database using the MS ODBC driver. However, if he
takes that same data source on his remote Windows client and changes the
connection info to point to the machine name and port number of the Solaris
box where a TCP/IP packet sniffer
(ftp://ftp.datadirect.com/download/da...ools/snoop.jar) is running and
the packet sniffer re-routes the connection to the SQL Server database, he
sees the same error that he gets with the DataDirect ODBC driver on Solaris.
So it appears that SQL Server must be configured only to disallow connections
coming from that Solaris machine, not necessarily all remote connections.
Does anyone know what setting is controlling this?
"Pat Frost" wrote:
> I work for DataDirect-Technologies. My customer is using our Connect for ODBC
> 5.00.0059 driver on Solaris 8 to connect to SQL Server 7 on Win 2000. When he
> tries to connect using a simple C application he gets the error
> "[DataDirect][ODBC SQL Server Driver][SQL Server]Cannot open database
> requested in login 'northwind'. Login fails." The customer has tried using
> the IP Address and the machine name. He has tried connecting to Northwind and
> Master. He is using the sa login with a password. He is able to connect with
> the same information from a Windows machine either using Windows
> Authentication or SQL Server authentication.
> There must be some setting within his SQL Server database that does not
> allow remote connections, is anyone aware of something like this?
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment