SQL or Watcom servers, ODBC, and TCPIP 
Author Message
 SQL or Watcom servers, ODBC, and TCPIP

Hi all,
I'm at my wit's end with this and need some help. I have NT workstation
SQL server 4.21 on one machine, and Watcom SQL server on a Win 3.1
machine. NT is running its TCPIP, Windows is running Trumpet. From
another Windows machine, I can't get MSQuery to connect to either using
ODBC. I've tried every form of address, etc, and it still can't see a
server. I also haven't found any good books on ODBC (experience kinds of
things) either. Watcom 4.0 server sees the TCPIP network, but after
applying their A patch, it doesn't. And of course Watcom doesn't do much
for support....

Does anyone have any ideas? What do (would) you run to test network
access? How do you have it set up? I'm out of ideas.

BTW, everything works fine locally on each, and all network apps work
fine too (I'm sending this with one ;-).

thanks,
skip




Mon, 12 Jan 1998 03:00:00 GMT
 SQL or Watcom servers, ODBC, and TCPIP



Quote:
>Does anyone have any ideas? What do (would) you run to test network
>access? How do you have it set up? I'm out of ideas.

>BTW, everything works fine locally on each, and all network apps work
>fine too (I'm sending this with one ;-).

Skip:

I know that MS-SQL Server has a client configuration utility which helps you
set up transport DLLs and network addresses. DOes Watcom use a similar
concept? For MS you need to specify DBMSSOC3.DLL and the IP address for each
server in the WIN.INI file under [SQL SERVER]. If any of this sounds familiar
or if you have the DLL file on your client, you might try this. The INI looks
like:

[SQLSERVER]
DSQUERY=DBNMP3
AutoAnsiToOem=off
pipestream=dbmssoc3,xxx.xxx.xxx.xxx

where pipestream is the server name the client programs will use.

Hope this helps.

Craig

***************************************************************

* Software Engineer
* IPC/Pipestream Technologies, Inc.
* ContactBuilder Web Page: http://www.ipctech.com/cbhome.htm
***************************************************************



Tue, 13 Jan 1998 03:00:00 GMT
 SQL or Watcom servers, ODBC, and TCPIP

Quote:

>Hi all,
>I'm at my wit's end with this and need some help. I have NT workstation
>SQL server 4.21 on one machine, and Watcom SQL server on a Win 3.1
>machine. NT is running its TCPIP, Windows is running Trumpet. From
>another Windows machine, I can't get MSQuery to connect to either using
>ODBC. I've tried every form of address, etc, and it still can't see a

Skip--

Can't help you with the Watcom.  But for the SQL Server 4.21a,
have you:

--configured sql server to use tcp/ip (not default behavior)?
--run the client config utility so that the win3.1 client has
the appropriate .dll loaded (dbmssoc3.dll, I *think*)?
--pinged sql server from the win3.1 client?
--connected to the sql server from the win3.1 station using
the "native" sql server utils (e.g., sqladmin.exe) thus taking
odbc out of the loop?

HTH
--Kylo

--Kylo Ginsberg       | Proof is always a relative thing.

(919) 962-9074        | probabilities.
                                --Raymond Chandler



Sat, 17 Jan 1998 03:00:00 GMT
 
 [ 3 post ] 

 Relevant Pages 

1. ODBC to SQL Server Slow after Switch from TCPIP to Named Pipes

2. ODBC to SQL Server Slow after Switch from TCPIP to Named Pipes

3. HELP: ODBC SQL Server programming using Watcom C 10.6

4. Problems making an ODBC connection on a TCPIP server address

5. Help: How to translate Watcom SQL database into SQL Server

6. Help: How to translate Watcom SQL database into SQL Server

7. SQL server 6.0 to Watcom/Sybase SQL Anywhere porting tool

8. Cannot read Watcom SQL Data tables using Microsoft Query/odbc Only System tables

9. Unix->ODBC->WatCom SQL

10. Watcom SQL with ODBC (On network) = Out of memory

11. ODBC 2.0 required by Delphi and Watcom SQL?

12. Watcom SQL 4.0 and Delphi 2.0 & ODBC


 
Powered by phpBB® Forum Software