I'm trying to get MSSQL Query analyzer to work it loads up i can enter the sql server name and user name and password. in the sql client utility it is setup for tcpip with an alias for the server name and the ip address. it tries to connect then comes back with an error: [Microsoft][ODBC SQL SERVER DRIVER][TCP?IP SOCKET]General network error odbc32 is native wsock32 is native winsock is native any ideas Ibrahim Hamouda
On Sun, 19 Aug 2001, Ibrahim Hamouda wrote:> I'm trying to get MSSQL Query analyzer to work > it loads up i can enter the sql server name and user name and password. > in the sql client utility it is setup for tcpip with an alias for the > server name and the ip address. > it tries to connect then comes back with an error: > [Microsoft][ODBC SQL SERVER DRIVER][TCP?IP SOCKET]General network error > > odbc32 is native > wsock32 is native > winsock is nativeSorry, I have been a bit busy lately, and I'm not too sure about this, but you left out the bit about native winsock/wsock32 from your complaint to wine-devel. I wouldn't use native anything wine has a builtin of, unless the app refuses to run with the wine builtin. AFAIK Wine's winsock and wsock32 are fairly functional - but all wine sockets are implemented using linux sockets. IOW, your linux box has to be connected to the windows box as itself, not expecting to use some windows functionality to connect. I sort of doubt that native winsock and wsock32 will work. builtin odbc32 might be worth a try. If your app uses msvcrt, native msvcrt might very well help. My app needs that and riched32 and mfc42.> > any ideas > > Ibrahim HamoudaLawson ---oof--- ________________________________________________________________ GET INTERNET ACCESS FROM JUNO! Juno offers FREE or PREMIUM Internet access for less! Join Juno today! For your FREE software, visit: dl.www.juno.com/get/tagj.
On Sun, 19 Aug 2001 22:03:26 GMT, Ibrahim Hamouda <admin@internode.net> wrote:>I'm trying to get MSSQL Query analyzer to work >it loads up i can enter the sql server name and user name and password. >in the sql client utility it is setup for tcpip with an alias for the >server name and the ip address. >it tries to connect then comes back with an error: >[Microsoft][ODBC SQL SERVER DRIVER][TCP?IP SOCKET]General network error > >odbc32 is native >wsock32 is native >winsock is nativeIt's not sure at all that it's possible to use the native version of these dlls. I don't remember having ever seen a success story involving this setup. OTOH people are using the builtin winsock everyday and the builtin odbc control was used by Corel when they were using Wine. So I'd try all builtin instead. Gerard
On Tue, 21 Aug 2001 01:44:56 GMT, g.patel@wanadoo.fr.invalid (gerard patel) wrote:>and the builtin odbc control was used by Corel when >they were using Wine.On second thought I think more dubious the possibility of the builtin control actually working. So the native odbc32 is probably the only possibility - that means using the native driver for MSSQL - it could work *if* this driver uses only winsock calls. Gerard